payone
Sign up

Testszenarios

    Introduction

    Before you go live, you want to be sure about how our platform works and how to process feedback received for processed transactions.

    As this is pivotal part in your journey to finally process live transactions, we have designed PAYONE E-Payment in a way allowing you to perform test transactions in manifold ways with any of our payment methods:

    • Successful, declined and uncertain transaction results.
    • Various 3-D Secure scenarios.
    • Fraud-related cases.
    • Outcomes when using one of our specific services.

    Without any costs involved, PAYONE E-Payment offers you a great way to simulate any business case you might encounter in your activities!

    Make sure to switch to the LIVE endpoint as soon as you have finalised your tests.

    Get started

    Before you start testing, make sure you:

    • Set up an active test account on our platform, with all the payment methods active you would like to test.
    • Understand the properties presented in the tables below.

      Input properties (values you need to send in your transaction request)
      Property Description
      amount Refers to property order.amountOfMoney.amount (CreateHostedCheckout/CreatePayment)
      currency Refers to property order.amountOfMoney.currencyCode (CreateHostedCheckout/CreatePayment)
      authorizationMode

      requiresApproval

      Refers to property
      cardPaymentMethodSpecificInput.authorizationMode 
      mobilePaymentMethodSpecificInput.authorizationMode 
      redirectPaymentMethodSpecificInput.requiresApproval
      in CreateHostedCheckout/CreatePayment) requests.

      Read our dedicated guide to learn more about these properties and available authorisation modes.

    If not specified, any value for properties are valid for any given scenario:

    amount

    currency

    authorizationMode

    • Output properties (values you receive from our platform after submitting a request)

      Properties Description
      eci

      Refers to property paymentOutput.cardPaymentMethodSpecificOutput.threeDSecureResults.eci (GetPayment/GetPaymentDetails/GetPaymentDetails)

      Learn more about ECI values and their meaning in our dedicated guide.
      statusCode

      Refers to properties
      statusOutput.statusCode
      payment.statusOutput.statusCode
      createdPaymentOutput.payment.statusOutput.statusCode

      Learn more about these properties and which of our API calls return them in our dedicated guide.

    Credit Cards

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)

    371449635311004 (3-D Secure frictionless flow eci=5)
    375418081197346 (3-D Secure frictionless flow eci=5)

    376691390182618 (3-D Secure frictionless flow eci=6)

    379764422997381 (3-D Secure challenge flow eci=5)
    379943305931143 (3-D Secure challenge flow eci=6)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)
    • Use any of the card numbers mentioned above.
    • Send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)

    36179157859125 (3-D Secure challenge flow eci=5)
    36488479185378 (3-D Secure frictionless flow eci=5)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)

    36155897388518 (3-D Secure challenge flow eci=91)
    36259600000079 (3-D Secure frictionless flow eci=91)
    Alternatively:

    • Use any of the card numbers mentioned above.
    • Send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)

    3528798062014879 (3-D Secure challenge flow eci=5)
    3569990010096831 (3-D Secure frictionless flow eci=5)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)

    3569990010083821 (3-D Secure challenge flow eci=91)
    3569990010014859 (3-D Secure frictionless flow eci=91)
    Alternatively:

    • Use any of the card numbers mentioned above
    • Send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)

    5020802352808673 (3-D Secure challenge flow eci=5)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)
    • Use any of the card numbers mentioned above.
    • Send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)

    5137009801943438 (3-D Secure frictionless flow eci=5)
    5156400512420624 (3-D Secure frictionless flow eci=6)

    5130257474533310 (3-D Secure challenge flow eci=5)
    5168693992589936 (3-D Secure challenge flow eci=6)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)

    5168645305790452 (3-D Secure frictionless flow eci=91)
    5144144373781246 (3-D Secure challenge flow eci=91)

    Alternatively:

    • Use any of the card numbers mentioned above.
    • Send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)

    4330264936344675 (3-D Secure frictionless flow eci=5)

    4450213273993630 (3-D Secure frictionless flow eci=6)

    4874970686672022 (3-D Secure challenge flow eci=5)
    4839645466321180 (3-D Secure challenge flow eci=6)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)

    4450022237973103 (3-D Secure challenge flow eci=91)
    Alternatively:

    • Use any of the card numbers mentioned above.
    • Send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    See the Integration tab for a JSON example.

    • To simulate the following pending statuses, we need to configure your account and make sure transactions are processed online (or offline when the online acquiring system is unavailable). Contact us to make this happen.
    • Read in our dedicated transaction status guide to learn more about these exceptional scenarios and how to deal with them.
    Use case Test data
    Pending authorisations (statusCode=51)
    • Use any of the card numbers from any card scheme mentioned in chapter 3
    • Send a request with the following properties:
      amount=1404
      currencyCode=EUR
      authorizationMode=FINAL_AUTHORIZATION
    Pending direct sales (statusCode=51)
    • Use any of the card numbers from any card scheme mentioned in chapter 3
    • Send a request with the following properties:
      amount=1402
      currencyCode=EUR
      authorizationMode=SALE
    Successful refunds (statusCode=8)
    • Make a RefundRequest request for any credit card transaction in statusCode=9
    • Send the request with any amount
      • not exceeding the originally captured amount
      • different than amount=1303/1203

    Right after processing the RefundPayment request, you will receive statusCode=81 in the feedback. Our platform will update the transaction to statusCode=8 after a few minutes. Make sure to retrieve this final status either via a GetPayment/GetPaymentDetails request or webhooks
    Uncertain refunds (statusCode=82)
    • Make a RefundRequest request for any credit card transaction in statusCode=9
    • Send the request with amount=1203
    Unsuccessful refunds (statusCode=83)
    • Make a RefundRequest request for any credit card transaction in statusCode=9
    • Send the request with amount=1303
    Uncertain captures (statusCode=92)
    • Make a CapturePayment request for any credit card transaction in statusCode=5
    • Send the request with amount=1209
    Unsuccessful captures (statusCode=93)
    • Make a CapturePayment request for any credit card transaction instatusCode=5
    • Send the request with amount=1309
    • Every capture request with any other amount not exceeding the orginally authorised amount will succeed (statusCode=9)
    • Right after processing the CapturePayment request, you will receive statusCode=91 in the feedback. Our platform will update the transaction to statusCode=93 after a few minutes. Make sure to retrieve this final status either via a GetPayment/GetPaymentDetails request or webhooks

    CVV for test cards

    Use any 3- or 4-digit number for the CVV on the Hosted Checkout Page / Hosted Tokenization Page or for cardPaymentMethodSpecificInput.card.cvv in Server-to-server requests.

    Alternative payment methods

    Use case Test data

    Successful direct sales (statusCode=9)

    Use our test environment simulator to simulate the redirection to and the feedback from Alipay+.

    See the Integration tab for a JSON example.

    • Use Apple's sandbox environment to perform test transactions. This requires: 
      • A separate PREPRAD AppleID from your for PROD one.
      • An active Apple developer account so that you can add your AppleID under "Sandbox testers".
      • Using the Apple test cards you can find here.
    • See the Integration tab for a JSON example.

    Use case Test data

    Successful direct sales (statusCode=4/9)
    • Send a standard requests to our TEST environment.
      See the Integration tab for a JSON example.

    • Use one of the following IBANs according to the selected country:

      BE45000253450589
      BE23000017071491

      FR7600000000007212272749749
      FR7600000000007738373402539

      DE18000000004105955519
      DE18000000001328642110

      NL81AAAA8558157030
      NL57AAAA1574700953

      GB74AAAA00000082036979
      GB22AAAA00000067677162

      ES5800000000015474125931
      ES2900000000061259313830

      IT06A0000000000816987740647
      IT57A0000000000874085444242
    • When activating Bank Transfer in your test account, we will always set it up for end-to-end testing.
    • To simulate the full payment flow resulting in statusOutput.statusCode=9, select country “Netherlands” and bank “SNS Bank“ on the bank selection page. Any other combination will result in the intermediate result statusOutput.statusCode=4
    • Your customers’ name and IBAN are not available in test.

    • To perform test transactions, you need to contact EPS for test credentials ("Benutzername”/”Passwort").
    • Depending on the use case, differences apply:
    Use case Test data

    Successful direct sales (statusCode=9) without customer bank account data

    To process a test transaction, follow these steps:

    1. On the EPS test page, enter "STZZATWWXXX" in the "Bankname/BIC/BLZ" field and click on the "Weiter zum Online-Banking" button.
    2. On the subsequent login page, enter your EPS test credentials for "Benutzername"/"Passwort".
    3. Click on "Login" and click on the "TAN ANFORDERN’ button. Enter the value next to "Ihr TAN" in the "TAN hier eintragen" field. Click on the "TAN SENDEN" button.

    See the Integration tab for a JSON example.

    Successful direct sales (statusCode=9) with customer bank account data

    To process a test transaction, follow these steps:

    1. On the login page, enter your EPS test credentials for "Benutzername"/"Passwort".
    2. Click on "Login" and click on the "TAN ANFORDERN" button. Enter the value next to "Ihr TAN" in the "TAN hier eintragen" field. Click on the "TAN SENDEN" button.

    See the Integration tab for a JSON example.

    Use case Test data

    Successful direct sales
    (statusCode=9)

    amount < 2000
    Unsuccessful authorisations/direct sales
    (statusCode=2)

    amount=4120000 
    Permanent uncertain direct sales
    (statusCode=51)

    amount=4020060
    Temporary uncertain direct sales
    (statusCode=51 with an update tostatusCode=9 after 30 seconds)

    amount=3000030

    See the Integration tab for a JSON example. Adapt the amount accordingly to reach the desired result.

    Our platform allows you to perform tests both via:

    • Our Klarna simulator (which is at your disposal by default). See the Integration tab for a JSON example.
    • End-to-end with the Klarna Playground environment. Contact us for setting this up. Use Klarna’s sample data for different markets to simulate different scenarios.
    We recommend placing a successful transaction (statusCode=9) (for each country/Klarna payment method) with our simulator before you test your integration with the Klarna Playground environment

    Use case Test data

    Successful direct sales (statusCode=9)

    Use our test environment simulator to simulate the redirection to and the feedback from Przelewy24.

    See the Integration tab for a JSON example.

    There are two ways to test your integration:

    1. Use our platform's PayPal simulator to process transaction in our test environment.
      As this is an internal tool, your transactions do not reach PayPal. Contact us to set up your account accordingly and to work with the use cases mentioned below.
    2. Use the PayPal Sandbox, allowing you to perform end-to-end tests from your test account. Contact us to set up your account accordingly.
    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)
    • Send a request with the following properties:
      authorizationMode="FINAL_AUTHORIZATION" / "SALE"
      amount=1000
    • See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)
    • Send a request with the following properties:
      authorizationMode="FINAL_AUTHORIZATION"

      amount=1304


      authorizationMode="SALE"
      amount=1302
    • See the Integration tab for a JSON example. Adapt the amount accordingly to reach the desired result.

    Special use cases

    Use case Test data

    Frictionless flow eci=5

    375418081197346
    371449635311004

    Frictionless flow eci=6

    376691390182618

    Frictionless flow eci=91

    375392300827514

    Challenge flow eci=5

    379764422997381

    Challenge flow eci=6

    379943305931143

    Challenge flow eci=91

    376632086941180

    Use case Test data

    Frictionless flow eci=5

    36004400015012
    3000000000000004

    Frictionless flow eci=6

    36004400072096
    3000009910995047

    Challenge flow eci=5

    36004400080248
    3000009227334104

    Challenge flow eci=6

    36341185608755

    Use case Test data

    Frictionless flow eci=5

    6011000991300009

    Frictionless flow eci=6

    6011006537286495

    Challenge flow eci=5

    6011001050519992

    Challenge flow eci=6

    6011413539170091

    Use case Test data

    Challenge flow eci=5

    3528801601699695
    3528398220562677

    Challenge flow eci=6

    3528410122368572

    Use case Test data

    Challenge flow eci=5

    5020802352808673

    Challenge flow eci=6

    6761806150084479

    Use case Test data

    Frictionless flow eci=5

    		 5137009801943438

    Frictionless flow eci=6

    5156400512420624

    Frictionless flow eci=91

    5168645305790452

    Challenge flow eci=5

    5130257474533310

    Challenge flow eci=6

    5168693992589936

    Challenge flow eci=91

    5144144373781246

    Use case Test data

    Frictionless flow eci=5

    		 4330264936344675

    Frictionless flow eci=6

    4450213273993630

    Frictionless flow eci=91

    4337328333414325

    Challenge flow eci=5

    4874970686672022

    Challenge flow eci=6

    4839645466321180

    Challenge flow eci=91

    4450022237973103

    Was this page helpful?

    Do you have any comments?

    Thank you for your response.
    Help & Info
    API Info
    Developer Tools
    Terms | Privacy |