# Adyen test cards

> Test card numbers and other details for Adyen's sandbox, and the result each one gives.

Use these details to try payments in an Adyen sandbox (test) account. They work only in the sandbox: never use them in live, and never put real card or bank details into a sandbox.

You need an Adyen test account first: see [Creating an Adyen sandbox account](/payment-providers/adyen-sandbox/). If you use Adyen's RevenueProtect, it can block test payments that look fraudulent; Adyen suggests adding the test card and shopper details to a trust list while testing.

:::note[Where these details come from]
These are Adyen's test details, not ours. They were copied from Adyen's [Test card numbers](https://docs.adyen.com/development-resources/test-cards-and-credentials/test-card-numbers), [Testing result codes and refusal reasons](https://docs.adyen.com/development-resources/testing/result-codes), [Testing 3D Secure 2 authentication](https://docs.adyen.com/development-resources/testing/3d-secure-2-authentication), [Testing card CVC/CVV/CID result codes](https://docs.adyen.com/development-resources/testing/result-codes/cvc-cvv-cid-result-codes) and [Testing risk features](https://docs.adyen.com/development-resources/testing/risk-features) pages on 19 October 2026, and were correct on that date as far as those pages show. Adyen can change or withdraw them at any time, and we can't confirm that they work. Check Adyen's pages for the current details, and ask Adyen if one doesn't behave as described.
:::

## How to choose a test result

- The card number sets the card brand and the 3D Secure result. Adyen's test cards approve with the expiry date and security code it lists for them ([Test card numbers](https://docs.adyen.com/development-resources/test-cards-and-credentials/test-card-numbers)).
- For a decline, the cardholder name sets the result ([Testing result codes and refusal reasons](https://docs.adyen.com/development-resources/testing/result-codes)). The checkout doesn't ask for a name on the card: we send Adyen the customer's first and last name, joined with a space. Enter the trigger exactly as shown, for example `NOT_ENOUGH_BALANCE`, as the customer's first name and leave the last name empty (or the other way round). If both are filled in, Adyen receives both and the trigger won't match.
- The security code sets the CVC check result ([Testing card CVC/CVV/CID result codes](https://docs.adyen.com/development-resources/testing/result-codes/cvc-cvv-cid-result-codes)).
- We ask Adyen for 3D Secure only when the customer is paying in the checkout, not on staff-entered (MOTO) or recurring payments. Adyen's own Dynamic 3D Secure rule also decides whether it is requested ([Testing 3D Secure 2 authentication](https://docs.adyen.com/development-resources/testing/3d-secure-2-authentication)).
- To test address checks, switch on **Require address (AVS)** in the Adyen connection settings, as well as AVS in your Adyen account. We send address line 1 as the street and address line 2 as the house number or name, and send no address at all unless line 1, line 2, town, postcode and country are all filled in. For `10 Downing Street`, enter `Downing Street` in line 1 and `10` in line 2.

## Cards

Adyen lists its test cards with expiry date 03/2030 and security code `737`, or `7373` for American Express. Use those unless a row says otherwise.

### Successful payments

| Card | Number | Notes |
| --- | --- | --- |
| Visa | `4111 1111 1111 1111` | |
| Visa (debit) | `4400 0000 0000 0008` | |
| Mastercard | `5555 5555 5555 4444` | |
| Mastercard (2-series) | `2223 0000 4841 0010` | |
| American Express | `3700 000000 00002` | Security code `7373` |
| Discover | `6011 6011 6011 6611` | |
| Diners Club | `3600 6666 3333 44` | |
| Maestro | `6771 7980 2100 0008` | 3D Secure is mandatory for online Maestro payments |
| Maestro | `5000 5500 0000 0029` | Used in our own tests, which send no security code: Adyen lists none for this card. Adyen lists it among its 3D Secure 2 test cards |

The checkout asks for a start date on Maestro cards. Adyen doesn't list one; our own tests with Adyen's sandbox use `03/2024`.

### Declines and errors

Enter one of these values as the customer's first name, with the last name empty, and use any test card above (see [How to choose a test result](#how-to-choose-a-test-result)). Adyen lists more values on its [Testing result codes and refusal reasons](https://docs.adyen.com/development-resources/testing/result-codes) page.

| Number or trigger | Result |
| --- | --- |
| Name `DECLINED` | Refused |
| Name `NOT_ENOUGH_BALANCE` | Refused: not enough balance |
| Name `BLOCK_CARD` | Refused: blocked card |
| Name `CARD_EXPIRED` | Refused: expired card |
| Name `CVC_DECLINED` | Refused: CVC declined |
| Name `RESTRICTED_CARD` | Refused: restricted card |
| Name `TRANSACTION_NOT_PERMITTED` | Refused: transaction not permitted |
| Name `FRAUD` | Refused: fraud |
| Name `ISSUER_SUSPECTED_FRAUD` | Refused: issuer suspected fraud |
| Name `REFERRAL` | Refused: referral |
| Name `ISSUER_UNAVAILABLE` | Refused: issuer unavailable |
| Name `AUTHENTICATION_REQUIRED` | Refused: authentication required |
| Name `ERROR` | Error: acquirer error |
| Name `PENDING` | Received (pending) |
| Name `AVS_DECLINED` | Refused: AVS declined |

### 3D Secure

If Adyen's Dynamic 3D Secure default rule is set to **Prefer Not**, set it to **Always** while testing, or 3D Secure may not be requested. When a challenge asks for a password, enter `password`. Any other password fails the challenge.

| Number | Result |
| --- | --- |
| `4917 6100 0000 0000` | Visa enrolled in 3D Secure: authenticate with the password |
| `5454 5454 5454 5454` | Mastercard enrolled in 3D Secure: authenticate with the password |
| `3714 496353 98431` | American Express enrolled in 3D Secure: authenticate with the password (security code `7373`) |
| `4212 3456 7891 0006` | Challenge requested |
| `5201 2815 0512 9736` | Frictionless: authenticated |
| `5201 2850 9382 3592` | Authentication attempted but couldn't be verified |
| `5201 2812 6243 5268` | Not authenticated: payment denied |
| `5201 2864 9681 6589` | Authentication rejected by the issuer |
| `5201 2828 2836 6351` | Authentication couldn't be performed |
| `5201 2829 9900 5515` | 3D Secure timeout error |
| `4917 6100 0000 0000` with challenge password `NoLiabilityShift` | Authenticated, but without liability shift |

### Address and CVC checks

**CVC:** enter one of these as the security code: `00` followed by the CVC result code to simulate.

| Value | Result |
| --- | --- |
| `001` | CVC matches: approved |
| `002` | CVC doesn't match: declined |
| `003` | CVC not checked: approved |
| `004` | No CVC given, but one was required: declined |

**Address (AVS):** Adyen's AVS test cards and the billing address each one is checked against. Adyen returns the AVS result with the payment; it doesn't list the result for each possible address. To force a refusal instead, use the name `AVS_DECLINED` (see [Declines and errors](#declines-and-errors)).

| Value | Result |
| --- | --- |
| `5555 5555 5555 4444` | Billing address: 10 Downing Street, London, SW1A 2AA, GB |
| `4400 0000 0000 0008` | Billing address: 1 Infinite Loop, Cupertino, CA, 95014, US |
| `4444 3333 2222 1111` | Billing address: 8-10 Broadway, Westminster, London, SW1H 0BG, GB |
| `3742 510187 20018` | Billing address: 1600 Pennsylvania Ave NW, Washington, DC, 20500, US (security code `7373`) |

## Apple Pay and Google Pay

We take Apple Pay and Google Pay as network tokens, through our own wallet integration rather than Adyen's. To test them, see [Testing Apple Pay and Google Pay](/platforms/testing/apple-pay-google-pay/).