Search

Are you looking for test card numbers?

Would you like to contact support?

Point-of-sale icon

Testing your integration

Test your point of sale integration before going live.

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.

Here we provide information on testing your Adyen point of sale integration, including:

Testing credit and debit cards

With each Adyen test terminal you receive one test card. You can use this to make dummy payments on the test terminal. (Dummy payments do not result in actual credits or debits to a live bank account.) The test card has several "applications" programmed onto it that each simulate a card with a unique brand, language, country, and currency. For example, a US-issued MasterCard credit card.

You can view the details of test payments, including the result, in your test Customer Area under Transactions > Payments.

You can also buy Adyen test card packs from shop.b2ps.com (US and Europe) that work in our test environment. These packs include several cards, each with a unique brand, language, country, and currency.

Which test card are you using?

Select your Adyen test card below to learn which card details to use for simulating card types and testing CVMs.

Testing gift cards

In general, the gift card provider (Givex, Stored Value Solutions (SVS), ValueLink) will provide you with testing details and enable a test environment for you.

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.

Card Number Balance
9826150920000060 1200.00
9826150920000003 9999.99
9826150920000045 560.00
9826150920000029 987500

Testing QR code wallets

Nearly all test QR code payments will result in the transaction being Approved.

  • Terminal or cash register initiated flow
    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.

  • Barcode scanner initiated flow
    If you are accepting test QR code payments using a barcode scanner, our simulator immediately approves the transaction when you scan the barcode.

    You do not need to use an actual Alipay or WeChat Pay QR code to make test payments. 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 an Alipay or WeChat Pay code:

    • Alipay wallet ID: string of 16-24 digits, starting with: 25, 26, 27, 28, 29 or 30
    • WeChat Pay wallet ID: 18 numbers, 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. See QR code acquirer responses for more information.

You can view the details of test payments, including the result, in your test Customer Area under Transactions > Payments.

Testing acquirer responses

To simulate different acquirer responses, change the three last digits of the RequestedAmount that you specify in the payment request.

You can test acquirer responses for:

Credit and debit card acquirer responses

Example: to test how your integration responds when the issuer suspects fraud, specify a RequestedAmount of 1.51.

Amount (last three digits) Acquirer Response Transaction Result
Any (except the special cases below) Approved Approved
121 Acquirer Cancelled Refused
122 Fraud Refused
123 Declined Refused
124 Not enough balance Refused
125 Blocked card Refused
126 Expired card Refused
127 Invalid amount Refused
128 Invalid card number Refused
129 Not supported Refused
130 Acquirer error Error
131 Acquirer declined Refused
132 Acquirer declined Refused
133 Referral Refused
134

Incorrect online PIN

Use the correct PIN for the application on your test card, either test card v1 or test card v2.

Error
135 PIN tries exceeded Refused
136 Issuer unavailable Refused
137

Withdrawal Amount Exceeded

Refused
138

Withdrawal Count Exceeded

Refused
139

Amount partially approved

Approved
142

Contactless Withdrawal Amount Exceeded (Only for contactless, otherwise APPROVED)

Refused
143 Contactless Withdrawal Count Exceeded (Only for contactless, otherwise APPROVED) Refused
144 Not Submitted Refused
145 Cancelled due to Fraud Refused
146 Transaction Not Permitted Refused
147 CVC Declined Refused
148 Restricted Card Refused
149 Revocation Of Auth Refused
150 Declined Non Generic Refused
151 Issuer Suspected Fraud Refused
152 No checking account Refused
153 No savings account Refused
154 Contactless fallback Retry
155 Mobile PIN required Retry
Any Card removed during app selection Error
Any Cancelled via terminal Cancelled
Any Cancelled through the library by merchant Cancelled

Transactions can be cancelled from the terminal or cash register. A cancellation will generate the result Cancelled. Refunds will generate the result Approved.

QR code acquirer responses

Example: to test how your integration responds to an abandoned transaction, specify a RequestedAmount of 5.04.

Amount (last three digits) Acquirer Response Transaction Result
401

Simulates an approved transaction.

The payment is immediately approved.

Approved
501

Simulates a scenario where the shopper needs to authorise the transaction in their app. A QR code appears on the terminal, and the payment is approved after 15 seconds.

Applies to terminal initiated and cash register initiated transactions.

Approved
502

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.

Applies to barcode initiated transactions.

Approved
504

Simulates an abandoned transaction.

The payment will be refused due to an issuer timeout.

Error
505

Simulates a refused transaction.

A QR code appears on the terminal, and the payment is refused after 15 seconds.

Applies to barcode initiated transactions.

Refused

See also