agricole
Sign up

Test cases

    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 CAWL ecommerce 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, CAWL ecommerce 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)

    4150557357382737 (3-D Secure frictionless flow eci=5)
    4150551403657424 (3-D Secure frictionless flow eci=6)

    4150550997933993 (3-D Secure challenge flow eci=5)
    4150555480415796 (3-D Secure challenge flow eci=6)

    See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)

    4150552528410004 (3-D Secure frictionless flow eci=91)

    4150551453859136 (3-D Secure challenge flow eci=91)

    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)

    6011492100005191 (No 3-D Secure eci=12)

    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)

    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)

    6250947000000048 (3-D Secure frictionless flow eci=5)
    622800594044411751 (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)

    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.

    Co-badged cards

    Test data Remarks
    Successful authorisations/direct sales (statusCode=5/9)

    6775906379873550
    Unsuccessful authorisations/direct sales (statusCode=2)
    • Use any of the card numbers mentioned above.
    • To provoke a decline transaction (statusCode=2) instead, send a request with the following properties:
      amount=1302
      currencyCode=EUR
      authorizationMode=SALE

    Use case Test data

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

    5341013985664960

    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

    Use case Test data

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

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

    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

    Use case Test data

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

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

    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

    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 PREPROD 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=9) with challenge flow
    • 60600599999899064

    Successful direct sales (statusCode=9) with frictionless flow

    Successful direct sales (statusCode=9) with challenge flow
    Unsuccessful authorisations/direct sales (statusCode=2) with frictionless flow
    • 60600599999899817

    See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)
    • Card number: 5395955800904069 / Expiry date: 02/26 / CVV: 606
      Card number: 5395955605797189 / Expiry date: 02/26 / CVV: 916
      Card number: 5395954000742742 / Expiry date: 01/26 / CVV: 721
    • See the Integration tab for a JSON example.
    As the funds on the card are indeed blocked by authorisations / payment, please do not forget to refund transactions

    Use Google’s sample cards to perform test transactions. 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.

    Use case Test data

    Successful direct sales (statusCode=9)
    • Card number: 9250004780000044623
    • Password: 081
    • Banking card number: 2507264734782317 (to be used for paying remaining amounts).
    • Any cryptogram
    • Any expiry date
    • To perform test transactions, you need to contact Thunes for a test account.
    • See the Integration tab for a JSON example.
    • As the funds on the card are indeed blocked by authorisations / payment, please do not forget to refund transactions.

    Use case Test data

    Successful direct sales (statusCode=9)
    • 7000000000000000998 (With minimal purchase value 5 €)amount >= 500
    • 7000000000000000997 (With maximal purchase value 50 €)
      amount <= 5000
    • 7000000000000000000 (Successful standalone transaction (no complementary payment).
    • 7000000000000000001 (Successful standalone transaction (no complementary payment), ignoring the minimum/maximum of 5€/50€ for this gift card).
    • 7000000000000000002 (Successful transaction with complementary payment).

    • See the Integration tab for a JSON example.
    Unsuccessful authorisations/direct sales (statusCode=2)
    • 7000000000000000998 (With minimal purchase value 5 €)
      amount < 500
    • 7000000000000000997 (With maximal purchase value (50 €)
      amount > 5000
    • 7000000000000000003 (Rejected by acquirer)
    • 7000000000000000009 (Invalid parameters)
    • 7000000000000000099 (Invalid or unknown retailer)
    • 7000000000000000119 (Card or customer does not exist)
    • 7000000000000000999 (Timeout or communication failure)
    • 7000000000000001000 (No balance available on gift card)

    • See the Integration tab for a JSON example.
    Cancelled orders (statusCode=1)
    • 7000000000000000018 (Transaction cancelled by customer)
    • 7000000000000000101 (Cancellation failed)

    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

    • To perform test transactions, you need to contact Linxo Connect for test data.
    • See the Integration tab for a JSON example.

    Use case Test data

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

    Use our test environment simulator to simulate the redirection to and the feedback from MB Way. See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations (statusCode=51)

    Send a standard requests to our TEST environment. See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)
    • Card number: 4970 1011 1111 1112
    • Expiration Date: current month/+1 year in the future.
    • CVV: 3 random numbers.
    • To perform test transactions, you need to contact Thunes for a test account.
    • See the Integration tab for a JSON example.
    • As the funds on the card are indeed blocked by authorisations / payment, please do not forget to refund transactions.

    • To perform test transactions, you need to contact Oney for a test account and test credentials.
    • Alternatively, use our our platform's Oney Card simulator to process transaction in our test environment. Mind that our test environment does not feature customised branding.
    • See the Integration tab for a JSON example.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)
    • Card number: 8100400000000000000
    • Cryptogram: 3 random numbers
    • To perform test transactions, you need to contact Thunes for a test account.
    • See the Integration tab for a JSON example.
    • As the funds on the card are indeed blocked by authorisations / payment, please do not forget to refund transactions.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)
    • PAN: 5136 7100 9056 5714
    • Expiration Date: current month + 5 months in the future.
    • Cryptogram: 3 random numbers.

    • Use the following credentials to login to the Thunes portal:

      • Login: OuvertureQualif
      • Password: 5g563pMiCaLUv7eQPm33
    • To perform test transactions, you need to contact Thunes for a test account.
    • See the Integration tab for a JSON example.
    • As the funds on the card are indeed blocked by authorisations / payment, please do not forget to refund transactions.

    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.

    • To perform test transactions, you need to contact Pledg for test data.
    • See the Integration tab for a JSON example.

    Use our platform's PostFinance Pay simulator to process transactions in our test environment.

    Use case Test data

    Successful authorisations/direct sales (statusCode=5/9)
    • Send the request with any amount different than 4120000/4540100.
    • See the Integration tab for a JSON example.

    Unsuccessful authorisations/direct sales (statusCode=2)
    • amount=4120000
    • See the Integration tab for a JSON example. Adapt the amount accordingly to reach the desired result. 

    Uncertain authorisations/direct sales
    (statusCode=52)
    • amount=4540100
    • 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

    		 4150557357382737

    Frictionless flow eci=6

    4150551403657424

    Frictionless flow eci=91

    4150552528410004

    Challenge flow eci=5

    4150550997933993

    Challenge flow eci=6

    4150555480415796

    Challenge flow eci=91

    4150551453859136

    Use case Test data

    Frictionless flow eci=5

    		 4010051418887694

    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

    		 6282245762444500

    Challenge flow eci=5

    622800594044411751
    858007414000002809
    8171999900000018

    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
    © 2025 | CAWL | Terms of use | Cookie notice