Adyen test cards by scenario
Trigger-driven: brand cards authorize by default, a cardholder name trigger forces each refusal reason, and 3D Secure has dedicated cards. Each card lists its own expiry and CVC. Where a cell names a trigger, use it with any of Adyen's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.
| Scenario | Adyen | Flint |
|---|---|---|
| Successful payment | 4111 1111 1111 1111expiry 03/2030, CVC 737 | 4242 4242 4242 4242any future expiry, any CVC, any ZIP |
| Generic decline | Holder name DECLINED | 4000 0000 0000 0002 |
| Insufficient funds | Holder name NOT_ENOUGH_BALANCE | 4000 0000 0000 9995 |
| Lost or stolen card | Not documented | 4000 0000 0000 99874000 0000 0000 9979lost, stolen |
| Expired card | Holder name CARD_EXPIRED | 4000 0000 0000 0069 |
| Incorrect CVC | Holder name CVC_DECLINED | 4000 0000 0000 0127 |
| 3D Secure challenge | 4917 6100 0000 0000password password | 4000 0025 0000 3155 |
| 3D Secure authentication fails | Any challenge password other than password or 1234 | 4000 0000 0000 3220fail the challenge |
| Card saves, then charges fail | Not documented | 4000 0000 0000 0341 |
| Dispute or chargeback | Holder name Chargeback | 4000 0000 0000 02594000 0000 0000 1976fraudulent, inquiry |
Declines, 3D Secure, and disputes
How Adyen triggers declines
Adyen's brand cards authorize by default. To force a refusal, send a test card with a trigger in the holder name: DECLINED for a generic refusal, NOT_ENOUGH_BALANCE for insufficient funds, CARD_EXPIRED for an expired card, and CVC_DECLINED for a bad CVC. Each value returns its refusal reason, as listed in the trigger values below.
How Adyen tests 3D Secure
3D Secure 2 has dedicated cards, such as 4917 6100 0000 0000 for a challenge. Complete a challenge with password in a browser or 1234 in a native app; any other value fails authentication. Online Maestro payments always require 3D Secure.
How Adyen simulates disputes
Send Chargeback as the holder name and capture the payment: within 24 hours it moves to chargeback and sends a NOTIFICATION_OF_CHARGEBACK webhook. Chargeback:{reason code} picks the dispute reason.