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 Direct 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, Direct offers you a great way to simulate any business case you might encounter in your activities!
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 Refers to property cardPaymentMethodSpecificInput.authorizationMode (CreateHostedCheckout/CreatePayment)
amount
currency
authorizationMode
are valid for any given scenario-
Output properties (values you receive from our platform after submitting a request)
Properties Description eci Refers to property paymentOutput.cardPaymentMethodSpecificOutput.threeDSecureResults.eci (GetPayment/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.statusCodeLearn more about these properties and which of our API calls return them in our dedicated guide
Use 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
Credit Cards
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
371449635311004 (3-D Secure frictionless flow eci=5) 379764422997381 (3-D Secure challenge flow eci=5) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
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) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
4150552528410004 (3-D Secure frictionless 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) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
36155897388518 (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) |
6011492100005191 (No 3-D Secure eci=12) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
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) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
3569990010083821 (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) |
5020802352808673 (3-D Secure challenge flow eci=5) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
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) 5130257474533310 (3-D Secure challenge flow eci=5) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
5168645305790452 (3-D Secure frictionless flow eci=91) Alternatively:
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) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
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) See the Integration tab for a JSON example |
Unsuccessful authorisations/direct sales (statusCode=2) |
4450022237973103 (3-D Secure challenge flow eci=91)
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) |
|
Pending direct sales (statusCode=51) |
|
Successful refunds (statusCode=8) |
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) |
|
Unsuccessful refunds (statusCode=83) |
|
Uncertain captures (statusCode=92) |
|
Unsuccessful captures (statusCode=93) |
|
Co-badged Cards
Test data | Remarks |
---|---|
Successful authorisations/direct sales (statusCode=5/9) | 6775906379873550 |
Unsuccessful authorisations/direct sales (statusCode=2) |
|
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 case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
4010061372166100 (3-D Secure frictionless flow eci=5) |
Unsuccessful authorisations/direct sales (statusCode=2) |
|
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
- See the Integration tab for a JSON example
Use case | Test data |
---|---|
Successful direct sales (statusCode=9) |
|
Unsuccessful authorisations/direct sales (statusCode=2) |
|
Use case | Test data |
---|---|
Successful direct sales (statusCode=9) |
|
Unsuccessful authorisations/direct sales (statusCode=2) |
|
Successful refunds (statusCode=8) |
|
Unsuccessful refunds (statusCode=83) |
|
- To perform test transactions, you need to contact Thunes for a test account
- Alternatively, use our platform's Cadhoc simulator to process transaction in our test environment
- See the Integration tab for a JSON example
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
|
- To perform test transactions, you need to Bimpli Cado for a test account
- Alternatively, use our platform's CADO Carte simulator to process transaction in our test environment
- See the Integration tab for a JSON example
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
|
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
|
- To perform test transactions, you need to contact Thunes for a test account
- Alternatively, use our platform's Cetelem 3x/4x simulator to process transaction in our test environment
- See the Integration tab for a JSON example
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
|
Unsuccessful authorisations (statusCode=2) |
|
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/statusCode=9) |
Use our test environment simulator to simulate the redirection to and the feedback from Cofidis. See the Integration tab for a JSON example |
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
|
Use case | Test data |
---|---|
Successful direct sales (statusCode=9) |
Use our test environment simulator to simulate the redirection to and the feedback from EPS See the Integration tab for a JSON example |
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) |
|
Unsuccessful authorisations/direct sales (statusCode=2) |
|
Uncertain direct sales (statusCode=92) |
|
Use case | Test data |
---|---|
Successful direct sales (statusCode=9) |
|
- 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) |
|
Unsuccessful authorisations/direct sales (statusCode=2) |
|
Cancelled orders (statusCode=1) |
|
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
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/statusCode=9) |
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 direct sales (statusCode=9) |
|
- To perform test transactions, you need to contact Thunes for a test account
- 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) |
|
- 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) |
|
- 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) |
|
- 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 P24 See the Integration tab for a JSON example |
There are two ways to test your integration:
- 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 - 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) |
|
Unsuccessful authorisations/direct sales (statusCode=2) |
|
Use case | Test data |
---|---|
Successful direct sales (statusCode=9) |
|
Unsuccessful authorisations/direct sales (statusCode=2) |
|
- Use our our platform's Sofinco 3x/4x simulator to process transactions in our test environment
- See the Integration tab for a JSON example
- To perform test transactions, you need to contact Spirit of Cadeau for a test account
- Alternatively, use our platform's Spirit of Cadeau simulator to process transaction in our test environment
- See the Integration tab for a JSON example
Use case | Test data |
---|---|
Successful authorisations/direct sales (statusCode=5/9) |
|
- Use our platform's TWINT simulator to process transactions in our test environment
- See the Integration tab for a JSON example
- To simulate one of the following special uses cases, adapt amount in your request accordingly
Use case | amount |
---|---|
Cancelled payment (statusCode=1) | 1302 |
Expired payment (statusCode=2) | 1402 |
Unsuccessful authorisations (statusCode=2) | 1502 |
To simulate these statuses, we need to configure your account accordingly. Contact us to make this happen