Search

Are you looking for test card numbers?

Would you like to contact support?

Point-of-sale icon

Test 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.

You need to :

  • Test the happy flow.
  • Test non-happy flows such as timeouts and connection problems, verifying the transaction status.
  • Simulate various acquirer responses to test your handling of declined transactions.
  • Test different card types and CVMs.

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, that do not result in actual credits or debits to a live bank account. The test card has several "applications" programmed onto it that let you test different card types, currencies, and verification methods (for example, PIN, signature, contactless). You can also use these applications to simulate the terminal UI in a different language.

  • To test transactions with a particular type of card, use the details for the corresponding application on the test card.
  • To test different Cardholder Verification Methods (CVM), use different combinations of transaction amount and currency with a test card application.
  • To test the responses you can receive from acquirers, 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.

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.

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.

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 QR code acquirer responses

To simulate different acquirer responses, 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) 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