Test cases
1. 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 v2 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!
2. 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) If not specified, any value for properties
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
3. Use test cards
Credit Cards
-
Show Hide
American Express
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
-
Show Hide
Carte Bancaire
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
-
Show Hide
Diners
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
-
Show Hide
JCB
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
-
Show Hide
Maestro
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
-
Show Hide
MasterCard
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
-
Show Hide
UnionPay International
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
-
Show Hide
Visa
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
-
Show Hide
Special cases
- 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
Co-badged Cards
-
Show Hide
Carte Bancaire (Maestro)
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
-
Show Hide
Carte Bancaire (MasterCard CREDIT)
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
-
Show Hide
Carte Bancaire (Visa CREDIT)
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
-
Show Hide
Carte Bancaire (Visa DEBIT)
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
-
Show Hide
Alipay+
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
-
Show Hide
Apple Pay
- Use Apple's sandbox environment to perform test transactions
- See the Integration tab for a JSON example
-
Show Hide
Bancontact
Use case Test data Successful direct sales (statusCode=9)
- 67030500000000002
- See the Integration tab for a JSON example
Unsuccessful authorisations/direct sales (statusCode=2) - 67030500000000127
- 4871049999999910 (Visa co-badged card)
- See the Integration tab for a JSON example
-
Show Hide
Bizum
Use case Test data Successful direct sales (statusCode=9)
- Phone number: 700 000 000
- Password: any random string
- amount<= 1500
- currencyCode=EUR
- authorizationMode=SALE
- See the Integration tab for a JSON example
Unsuccessful authorisations/direct sales (statusCode=2) - Phone number: 700 000 000 / ko@ko.ko
- Password: any random string
- amount >1500
- currencyCode=EUR
- authorizationMode=SALE
- See the Integration tab for a JSON example
Successful refunds (statusCode=8) - Send a CreatePayment/CreatedHostedCheckout request with amount=1500 to create a transaction in statusCode=9
- Refund this transaction with amount=1400
- See the Integration tab for a JSON example. Adapt amount accordingly to reach the desired result
Unsuccessful refunds (statusCode=83) - Send a request with order.amountOfMoney.amount=1500 and a subsequent RefundPayment request with order.amountOfMoney.amount<=1500
- See the Integration tab for a JSON example. Adapt amount accordingly to reach the desired result
-
Show Hide
Chèque-Vacances Connect
Use case Test data Successful authorisations/direct sales (statusCode=5/9)
- To perform test transactions, you need to
- Contact Limonetik for a test account and registering your e-mail address
- Install the Chèque-Vacances mobile app on your device
- See the Integration tab for a JSON example
- To perform test transactions, you need to
-
Show Hide
Cpay
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 - Card number: 5395955800904069 / Expiry date: 02/26 / CVV: 606
-
Show Hide
Google Pay
Use Google’s sample cards to perform test transactions. See the Integration tab for a JSON example
-
Show Hide
iDEAL
Use case Test data Successful direct sales (statusCode=9)
- amount=1000
- currencyCode=EUR
- issuerId=RABONL2U
- See the Integration tab for a JSON example. Adapt the amount accordingly to reach the desired result
Unsuccessful authorisations/direct sales (statusCode=2) - amount=1314 (Authorisation declined)
- amount=1514 (Your customer cancels the payment on 3rd party website)
- currencyCode=EUR
- issuerId=RABONL2U
- See the Integration tab for a JSON example. Adapt the amount accordingly to reach the desired result
Uncertain direct sales (statusCode=92) - amount=1214
- currencyCode=EUR
- issuerId=RABONL2U
- See the Integration tab for a JSON example. Adapt the amount accordingly to reach the desired result
-
Show Hide
Illicado
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 Limonetik 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
-
Show Hide
Intersolve
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)
- See the Integration tab for a JSON example
-
Show Hide
Klarna
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 -
Show Hide
Mealvouchers
Use case Test data Successful direct sales (statusCode=9)
- UpChequeDejeuner
Apetiz- Card number: 4970 1011 1111 1112
- Expiry date: Current date + 1 year in the future
- CVV: any 3-digit number
- SodexoBE
- Banking card number: 5017 6700 0000 1800
- Expiry date: Any date in the future
- CVV: any 3-digit number
- Monizze
- Login: limo1@monizze.be
- Password: limonetiktest
- Banking card number: 4111 1111 1111 1111
- Expiry date: Any date in the future
- CVV: any 3-digit number
- PassRestaurant
- 1st generation
- Card number: 8100 4000 0000 0000 ()
-
2nd generation
-
Card number: 5075 9700 0173 6316
-
Expiry date: 09/19
-
CVV: 602
-
-
Credit card
- Card number: 4970 1011 1111 1112
- Expiry date: Current date + 1 year in the future
- CVV: any 3-digit number
- 1st generation
- To perform test transactions, you need to contact Limonetik for a test account
- See the Integration tab for a JSON example
- UpChequeDejeuner
-
Show Hide
Multibanco
Use case Test data Successful authorisations (statusCode=51)
Send a standard requests to our TEST environment. See the Integration tab for a JSON example
-
Show Hide
Oney 3x-4x
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 Limonetik 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.
-
Show Hide
OneyBrandedGiftCard
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 Limonetik 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.
-
Show Hide
Oney Financement Long
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 Limonetik Portal:
- Login: OuvertureQualif
- Password: 5g563pMiCaLUv7eQPm33
- To perform test transactions, you need to contact Limonetik 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
-
Show Hide
Paypal
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)
- 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
- Use our platform's PayPal simulator to process transaction in our test environment
-
Show Hide
SEPA Direct Debit
Use case Test data Successful direct sales (statusCode=9)
- Send a request with one of the following IBANs:
BE45000253450589
BE23000017071491
FR7600000000007212272749749
FR7600000000007738373402539
DE18000000004105955519
DE18000000001328642110
NL81AAAA8558157030
NL57AAAA1574700953
GB74AAAA00000082036979
GB22AAAA00000067677162
ES5800000000015474125931
ES2900000000061259313830
IT06A0000000000816987740647
IT57A0000000000874085444242 - See the Integration tab for a JSON example
Unsuccessful authorisations/direct sales (statusCode=2)
- Use any of the IBANs mentioned above
- Send a request with an expired/revoked mandate in property uniqueMandateReference
See the Integration tab for a JSON example
- Send a request with one of the following IBANs:
4. Special use cases
-
Show Hide
3-D Secure - Carte Bancaire
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
-
Show Hide
3-D Secure - Carte Bancaire (Visa CREDIT co-badged card)
Use case Test data Frictionless flow eci=5
4010051418887694 -
Show Hide
3-D Secure - MasterCard
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
-
Show Hide
3-D Secure - UnionPay International
Use case Test data Frictionless flow eci=5
6250947000000048 Challenge flow eci=5
622800594044411751
-
Show Hide
3-D Secure - Visa
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