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 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 view the details and the result of test payments in your test Customer Area under Transactions > Payments.

Adyen test card

You can order a free Adyen test card from your test Customer Area as an accessory for your terminal.

The Adyen 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). Using the Adyen test card, you can:

  • Test different card brands.
  • Test different CVMs.
  • Test declined payments.
  • Simulate the terminal UI in a different language.

B2 test card sets

Apart from the test card provided by Adyen, you can also buy an Adyen test card set from B2. Such a set includes several cards, each with a unique brand, language, country, and currency. These cards work in our test environment, and are primarily intended to test if your integration supports various card brands.

Which test card are you using?

Select your test card below to learn how to use it.

Test cards from providers other than Adyen or B2 may not be compatible with our test terminals.

Testing gift cards

In general, gift card providers have a test environment and physical test gift cards for end-to-end test transactions. However, it takes time and effort to set up the correct testing details and credentials. Also, these test environments are not always online. For those reasons, we provide a testing system that lets you simulate gift card transactions.

When simulating transactions:

  • Use a specific gift card number depending on your gift card provider.
  • Test a few scenarios by providing specific transaction amounts.

You can test other scenarios in your live environment using real gift card details and small amounts.

You can view the details of the test payments in your test Customer Area under Transactions > Payments. For the details of your live tests, go to your live Customer Area.

Gift card numbers

To simulate gift card transactions, use the following gift card numbers.

Type Number Security code Expiry date
Givex gift card 6036280000000000000 Any Any 4 digits
Generic gift card 6364530000000000 Any Any 4 digits
SVS gift card 6006490000000000 Any Any 4 digits
Fiserv (formerly ValueLink) gift card 7777182708544835 Any Any 4 digits

If the simulator asks for a Fiserv (formerly ValueLink) promo code, enter any value.

To test the balance check, make a test payment for an amount higher than EUR 50.

Test scenarios

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

The following table shows:

  • The last three digits of the amount to specify for simulating a specific response.
  • The Result, ErrorCondition, AdditionalResponse.refusalReason and AdditionalResponse.message from the Terminal API response.
Amount ending in Result ErrorCondition refusalReason message
100 Authorised
123 Failure Refusal 214 Declined online DECLINED
124 Failure Refusal 210 Not enough balance NOT_ENOUGH_BALANCE
125 Failure Refusal 199 Card blocked BLOCK_CARD
126 Failure Refusal 228 Card expired CARD_EXPIRED
130 Failure Refusal 214 Declined online CONVERTER_ERROR_REQUEST
134 Failure WrongPIN 129 Invalid online PIN INVALID_PIN
135 Failure Refusal 128 Online PIN tries exceeded PIN_TRIES_EXCEEDED

Testing NFC wallets

Payments with NFC wallets like Apple Pay can only be tested in a live environment.

Testing QR code wallets

To test QR code payments, you can:

  1. Make test payments using our simulator.
  2. 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).

You can view the details of the test payments in your test Customer Area under Transactions > Payments. For the details of your live penny tests, go to your live Customer Area.

Adyen simulator

We provide a simulator that lets you try out QR code payments in the various flows.

  • Merchant-presented flow:
    If you are testing QR code payments initiated by the terminal or initiated by the POS app, 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.

Test scenarios

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)DescriptionTransaction result
401

Simulates an approved transaction.

The payment is immediately approved.

Approved
501

In the merchant-presented flows (initiated from terminal or initiated from POS app), 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.

Approved
502

In the shopper-presented flow (initiated from barcode scanner), 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.

Approved
504

Simulates an abandoned transaction.

The payment will be refused due to an issuer time-out.

Error
505

In the shopper-presented flow, simulates a refused transaction.

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

Refused

See also