White Adyen point-of-sale test card

When making test payments with this card:

• To test a specific application on the test card, use the corresponding currency in your payment request.
• To test different CVMs, 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 in your test Customer Area under Transactions > Payments.

The card simulates Mastercard and Maestro payment methods. To verify that your POS app and terminal are communicating as expected and to test your reconciliation, no other card payment methods are needed. But as an alternative, you can order test card packs from B2PS.

Card applications

Use the table below to see which application on the test card corresponds with the scenario you want to test.

To try a particular application, use the corresponding currency in your payment request. You can also select an application on the terminal: when the terminal shows Present card, insert the card and select the application on the display.

Application	Payment method	Issuing country	Currency	Expiration date	Locale	PIN	PAN
MC NL	Mastercard	BE	EUR	02/28	Dutch	1234	5413 3300 8909 9999
MS EN	Maestro	BE	EUR	02/28	English	1234	6799 9989 0000 0099 990
MC F	Mastercard	US	USD	02/28	French	1234	5413 3300 8999 9990
MC ES	Maestro	US	USD	02/28	Spanish	1234	6799 9989 0000 0999 991
MSR	Mastercard	US	USD	12/25	English	1234	5413 3300 8902 0037

Testing CVMs

To test different CVMs, use different combinations of transaction amount and currency.

Application	Amount	Currency	CVM
MC NL	>200.00	EUR	CVM 1: online enciphered PIN
	>100	EUR	CVM 2: EMV chip enciphered PIN
	0-100	EUR	CVM 3: signature
MS EN	>200.00	EUR	CVM 1: online enciphered PIN
	>100	EUR	CVM 2: EMV chip enciphered PIN
	0-100	EUR	CVM 3: signature
MC F	All	All	CVM 1: EMV chip enciphered PIN
MC ES	All	All	CVM 1: EMV chip enciphered PIN
MSR	All	All	CVM 1: service code 101 - Signature

For online PIN, with the card inserted in the card reader, the test system will accept any PIN code you enter.

For offline PIN, with the card inserted in the card reader, the transaction will be declined if you enter an invalid PIN.

Simulating declined payments

In general, test payments generate the result Approved. To simulate declined payments, you can change the last three digits of the RequestedAmount that you specify in the payment request.

For example, to test how your integration responds when the issuer suspects fraud, specify an amount with 151 as the last three digits, such as 101.51 or 21.51.

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.

Raw responses

In our back end, we receive the payment response from card schemes and issuers. In case of a declined payment, we map the raw response to a combination of ErrorCondition, refusalReason, and message and return this in the Terminal API response.

Raw responses provide additional information, but you don't need to test them because you should not code against them. If you base your failure-handling logic on raw responses, that might break your integration because acquirers and issuers sometimes change their raw responses without notice.

If you still want to receive the raw response, you can:

• Set up standard notifications with the additional setting Add Raw Acquirer Result enabled.
• For a Terminal API integration, configure receiving raw responses.

See also