Testing Your Integration

You can use the following test card numbers to simulate various transaction scenarios across multiple card brands. These test cards are meant for development and testing purposes only and will not result in actual charges.

Test Cards

Card Type	Card Number	Expiry Date	CVV	Scenario
Visa Debit	4400 0015 2374 0004	03/30	525	Successful transaction
Visa	4212 3432 8425 0006	03/30	525	3D Secure 2 challenge action
Mastercard	5201 2815 0512 9736	03/30	525	Frictionless flow
Maestro	5002 5132 5341 0013	03/30	525	Non 3DS transaction
Discover Debit	6011 6032 5623 0003	03/30	525	Non 3DS transaction
Amex	3700 0000 0000 002	03/30	5252	Non 3DS transaction
Visa	4917 6155 8823 0000	03/30	525	3D Secure 2

Successful Transaction Behavior

All "successful" cards listed above will return a simulated Authorised response. For deeper integration tests, you can simulate other outcomes like Refused, RedirectShopper, and more by configuring your test environment.

Testing Result Codes and Refusal Reasons

You can test how your integration can handle different responses to make sure your integration can handle failure scenarios. In such scenarios, you receive a result code and a refusal reason that tells you why a payment request did not succeed.

You can trigger specific refusal reasons in your payment requests to test how your integration handles failure scenarios.

Benefits of Testing Refusal Reasons

This describes how to trigger specific refusal reasons in your payment requests and test unhappy scenarios. There are several benefits to making sure your integration can handle unhappy flows, for example:

Presenting your shoppers with specific error messages per refusal reason.

Ensuring that you have a retry logic to handle refused payments.

Building your order management system logic to make sure unhappy scenarios are handled correctly.

Refusal Test Card Details

Card Number: 4111 1111 2222 1111

Expiry Date: 03/30

CVV: 525

Values for Testing Refusal Reasons

The following table provides the values you need to specify in Cardholder Name to trigger specific refusal reasons in the response:

The Refusal Reason and Result Code columns indicate the responses you can trigger.

The Cardholder Name column provides the value to use if you want to trigger the response.

Refusal Reason	Result Code	Cardholder Name
Unknown	Error	UNKNOWN
-	Authorised	APPROVED
Refused	Refused	DECLINED
Referral	Refused	REFERRAL
Acquirer Error	Error	ERROR
Blocked Card	Refused	BLOCK_CARD
Expired Card	Refused	CARD_EXPIRED
Invalid Amount	Refused	INVALID_AMOUNT
Invalid Card Number	Refused	INVALID_CARD_NUMBER
Issuer Unavailable	Refused	ISSUER_UNAVAILABLE
Not supported	Refused	NOT_SUPPORTED
3D Not Authenticated	Refused	NOT_3D_AUTHENTICATED
Not enough balance	Refused	NOT_ENOUGH_BALANCE
-	Received	PENDING
Acquirer Fraud	Refused	ACQUIRER_FRAUD
Cancelled	Refused	CANCELLED
Shopper Cancelled	Refused	SHOPPER_CANCELLED
Invalid Pin	Refused	INVALID_PIN
Pin tries exceeded	Refused	PIN_TRIES_EXCEEDED
Pin validation not possible	Refused	PIN_VALIDATION_NOT_POSSIBLE
FRAUD	Refused	FRAUD
Not Submitted	Refused	NOT_SUBMITTED
FRAUD-CANCELLED	Cancelled	FRAUD_CANCELLED
Transaction Not Permitted	Refused	TRANSACTION_NOT_PERMITTED
CVC Declined	Refused	CVC_DECLINED
Restricted Card	Refused	RESTRICTED_CARD
Revocation Of Auth	Refused	REVOCATION_OF_AUTH
Declined Non Generic	Refused	DECLINED_NON_GENERIC
Withdrawal amount exceeded	Refused	WITHDRAWAL_AMOUNT_EXCEEDED
Withdrawal count exceeded	Refused	WITHDRAWAL_COUNT_EXCEEDED
Issuer Suspected Fraud	Refused	ISSUER_SUSPECTED_FRAUD
AVS Declined	Refused	AVS_DECLINED
Card requires online pin	Refused	PIN_REQUIRED
No checking account available on Card	Refused	NO_CHECKING_ACCOUNT_AVAILABLE_ON_CARD
No savings account available on Card	Refused	NO_SAVINGS_ACCOUNT_AVAILABLE_ON_CARD
Mobile PIN required	Refused	MOBILE_PIN_REQUIRED
Contactless fallback	Refused	CONTACTLESS_FALLBACK
Authentication required	Refused	AUTHENTICATION_REQUIRED
RReq not received from DS	Refused	RREQ_NOT_RECEIVED
Current AID is in Penalty Box.	Refused	BAN_CURRENT_AID
CVM Required Restart Payment	Refused	CVM_REQUIRED_RESTART_PAYMENT
3DS Authentication Error	Refused	THREED_SECURE_AUTHENTICATION_ERROR
Online PIN required	Refused	ONLINE_PIN_REQUIRED
Try another interface	Refused	TRY_ANOTHER_INTERFACE
Chip downgrade mode	Refused	CHIP_DOWNGRADE_MODE
Transaction blocked by Adyen to prevent excessive retry fees	Refused	ERPS_BLOCK

Tips for Testing

Expiry Date: 03/30

CVV: 525/5252

Amount: Use specific values (like £100.00 or $1.00) to trigger specific logic in your application

📌

Always use these cards in sandbox or staging environments only. Never use real card data during testing.

Testing Your Integration

Test Cards#

Successful Transaction Behavior#

Testing Result Codes and Refusal Reasons#

Benefits of Testing Refusal Reasons#

Refusal Test Card Details#

Values for Testing Refusal Reasons#