We provide a basic testing system to simulate transaction scenarios and functionalities. You can use this system to ensure your test integration is working as expected, before you switch to an integration that can make live transactions.
You need to :
- Test the happy flow.
- Test non-happy flows such as time-outs and connection problems, verifying the transaction status.
- Simulate various acquirer responses to test your handling of declined transactions.
- Test different Cardholder Verification Methods (CVM).
We strongly recommend you also test your live integration.
Testing credit and debit cards
To test card payments on your test terminal, you need to have a test card. With this, you can make dummy payments that do not result in actual credits or debits to a live bank account.
You can order a free Adyen test card from your test Customer Area as an accessory for your terminal.
The test card has several "applications" programmed onto it that each simulate a card with a specific brand, language, country, currency, and Cardholder Verification Method (CVM) (for example, PIN, signature, contactless). You can also use these applications to simulate the terminal UI in a different language.
- To use a specific application on the test card, use the corresponding currency in your payment request.
- To test different Cardholder Verification Methods (CVM), use different combinations of transaction amount and currency.
- To test declined payments, use the last three digits of the transaction amount.
You can view the details of test payments, including the result, in your test Customer Area under Transactions > Payments.
Which test card are you using?
Select your Adyen test card below to learn which card details to use for testing different card types, CVMs, and acquirer responses.
Apart from the test card provided by Adyen, you can also buy Adyen test card packs from shop.b2ps.com (North America and Europe) that work in our test environment. These packs include several cards, each with a unique brand, language, country, and currency.
Test cards from other providers may not be compatible with our test terminals. Check with our POS Support Team before purchasing test cards that are not issued by Adyen or B2PS.
Testing gift cards
When testing gift cards provided by FIS Global, you can use the card numbers and balances below to simulate transaction scenarios.
Charge an amount against your test card with the last three digits reflecting the test transaction you want to simulate.
The balance is reduced for the duration of the transaction only.
Testing QR code wallets
To test QR code payments, you can:
- Make test payments using our simulator.
- Perform live, in-app tests.
For this, you need to get the QR code wallet app, set it up with a credit or debit card, and do live penny tests (payments for a minimal amount).
We provide a simulator that lets you try out QR code payments in the various flows.
If you are testing QR code payments initiated by the terminal or initiated by the cash register, our simulator shows a QR code on the terminal and automatically approves the transaction after 15 seconds.
- Shopper-presented flow
If you are testing QR code payments initiated by a barcode scanner, our simulator immediately approves the transaction when you scan the barcode.
To make test payments, you do not need to use an actual payment method QR code (for example, an Alipay QR code). Any barcode or QR code can be used, but we highly recommend testing your integration using a barcode or QR code that uses the same specifications as the payment method:
- Alipay wallet ID: string of 16-24 digits, starting with 25, 26, 27, 28, 29 or 30
- WeChat Pay wallet ID: 18 digits, starting with 10, 11, 12, 13, 14 or 15
By changing the value of the transaction, you can test other payment scenarios, such as abandoned or refused transactions.
Nearly all test QR code payments will result in the transaction being Approved. To simulate different scenarios, change the last three digits of the
RequestedAmount that you specify in the payment request.
For example, to test how your integration responds to an abandoned transaction, specify a
RequestedAmount with 504 as the last three digits, such as 105.04 or 25.04.
|Amount (last three digits)||Description||Transaction result|
Simulates an approved transaction.
The payment is immediately approved.
A QR code appears on the terminal, and the payment is approved after 15 seconds.
In the shopper-presented (barcode initiated) flow, simulates a scenario where the shopper needs to authenticate the transaction using their app.
You need to scan the shopper's barcode with your terminal. The payment is approved after 15 seconds.
Simulates an abandoned transaction.
The payment will be refused due to an issuer time-out.
In the shopper-presented flow, simulates a refused transaction.
A QR code appears on the terminal, and the payment is refused after 15 seconds.