Are you looking for test card numbers?

Would you like to contact support?

Developer-resource icon

Test with cards

Test your integration with our test card numbers.

Testing POS payments?

We provide physical test cards to use with our test payment terminals. For more information, see our point-of-sale test cards.

Before accepting live payments, you can use the cards and payment method details on this page to test your integration. These are only valid on our test platform, and will not result in a real transaction or transfer of funds.

You can check the status of test payments in your Customer Area > Transactions > Payments.

When you use RevenueProtect, test payments might be blocked because they can appear fraudulent. To continue testing, you can temporarily add the test card and shopper details to a trust list.

The test card numbers are only valid on the Adyen test platform and will not work anywhere else.

Some test cards do not require a security code. These are tagged with security code optional.

Find the source code on GitHub

Our test cards extension is open-source.
Find the repository on GitHub.

Test Cards Chrome extension

Install the Adyen Test Cards extension from the Chrome Web Store to access, copy, and prefill card details for some of the test cards on this page from within your browser. This page includes further information about testing special flows.

Test special flows

Test 3D Secure 2 authentication

If your default dynamic 3D Secure rule is set to Prefer Not, then the following test cards will not trigger 3D Secure. You can either set your default dynamic 3D Secure rule to Always or force 3D Secure by passing authenticationData.attemptAuthentication in your API request.

To test how your integration handles different 3D Secure 2 authentication scenarios, you need to use a card number for the specific flow.

When prompted for 3D Secure 2 text challenges, use the following credentials to authenticate:

  • For native mobile integrations, use password: 1234
  • For web and mobile browser integrations, use password: password

Depending on the authentication optjon, you can receive the following result codes:

  • RedirectShopper: you receive this result code if you are using the Redirect authentication flow.
  • IdentifyShopper: you receive this result code if you are using the Native authentication flow.
  • ChallengeShopper: you receive this result code after you submit the 3D Secure 2 device fingerprinting result in a Native authentication, unless you specify a frictionless flow.

Depending on your integration, use the following test cards to simulate different authentication flows.

Card Type Card Number Expiry Date Security Code (CVC/CVV/CID)
American Express 3714 4963 5398 431 03/2030 7373
BanContact 6060 0599 9998 99015 03/2030 737
Cartes Bancaires / Visa Debit 4035 5014 2814 6300 03/2030 737
Cartes Bancaires 4360 0000 0100 0005 03/2030 737
China UnionPay (Credit) 6250 9470 0000 0014 03/2030 123
China UnionPay (Debit) 6250 9460 0000 0016 03/2030 123
Diners 3056 9309 0259 04 03/2030 737
Discover 6011 1111 1111 1117 03/2030 737
Maestro 5000 5500 0000 0029 03/2030 n/a
MasterCard 5454 5454 5454 5454 03/2030 737
MasterCard Credit 2222 4000 1000 0008 03/2030 737
Visa 4917 6100 0000 0000 03/2030 737
Visa Classic 4166 6766 6766 6746 03/2030 737

Challenge without fingerprint

To test the web-based flow where the device fingerprinting step is skipped (because the issuer's ACS has not configured a threeDSMethodURL), and you get a ChallengeShopper resultCode immediately after submitting the payment request, use the following card:

Card Type Card Number Expiry Date Security Code (CVC/CVV/CID)
Visa 4212 3456 7891 0006 03/2030 737

Fingerprint without challenge

To test the frictionless flow, in which you perform a fingerprint but no challenge, use the following test card number:

Card number Expiry Date Security Code (CVC/CVV/CID) Authentication scenario
5201 2815 0512 9736 03/2030 737 Fingerprint but no challenge

Native authentication

To test authentication scenarios for native mobile (app-based) integrations, use the following test cards:

Card number Expiry Date Security Code (CVC/CVV/CID) Authentication scenario
5201 2855 6567 2311 03/2030 737 Basic text authentication
5201 2874 9905 2008 03/2030 737 Basic single select
5201 2815 9233 1633 03/2030 737 Basic multi select
5201 2888 2269 6974 03/2030 737 Basic out-of-band (OOB) authentication
5201 2895 0084 3268 03/2030 737 HTML out-of-band (OOB) authentication
5201 2861 5377 1465 03/2030 737 App single select then text authentication
4917 6100 0000 0042 03/2030 737 Advanced: ACS sends an empty Challenge Response (CRes)
4917 6100 0000 0067 03/2030 737 Advanced: Invalid content in the acsSignedContent field
4917 6100 0000 0059 03/2030 737 Advanced: Challenge Response (CRes) timeout

Technical error

To test simulate an error due to a timeout during the 3D Secure 2 authentication on the issuer side, use the following test card:

Card number Expiry Date Security Code (CVC/CVV/CID) Scenario
5201 2829 9900 5515 03/2030 737 Depending on your configuration, the transaction might still proceed to a successful authorization.

Advanced scenarios

Use the following test cards to test scenarios returning ARes with different transStatus values:

  • Y: Authentication / account verification successful.
  • N: Not Authenticated / account not verified. Transaction denied.
  • A: Authentication / verification was attempted but could not be verified.
  • U: Authentication / account verification could not be performed.
  • R: Authentication / account verification rejected by the Issuer.
Card number Expiry Date Security Code (CVC/CVV/CID) Scenario
5201 2815 0512 9736 03/2030 737 Return ARes with transStatus=Y
5201 2812 6243 5268 03/2030 737 Return ARes with transStatus=N
5201 2850 9382 3592 03/2030 737 Return ARes with transStatus=A
5201 2828 2836 6351 03/2030 737 Return ARes with transStatus=U
5201 2864 9681 6589 03/2030 737 Return ARes with transStatus=R
5201 2846 7071 7533 03/2030 737 Return ARes with transStatus=U and transStatusReason=06
5201 2829 9900 5515 03/2030 737 Timeout error
5201 2886 9531 5843 03/2030 737 Connection failure error
5201 2858 9491 2800 03/2030 737 Version number not supported error
5201 2852 4062 4612 03/2030 737 Access denied error
5201 2859 4986 5169 03/2030 737 MCC not valid error
5201 2829 4084 9714 03/2030 737 Invalid endpoint error

Test Address Verification System (AVS)

Use the following shopper details to test AVS:

Card Number Card Type House Number Address ZIP Code Country Expiry Date Security Code (CVV/CVC/CID)
5555555555554444 Mastercard 10 Downing Street, London. SW1A 2AA GB 03/2030 737
374251018720018 Amex 1600 Pennsylvania Ave NW Washington, DC. 20500 US 03/2030 7373
374251021090003 Amex 1 Infinite Loop Cupertino, CA. 95014 US 03/2030 7373
374101012180018 Amex 10 Downing Street, London. SW1A 2AA GB 03/2030 7373
374251033270007 Amex 8-10 Broadway, Westminster, London. SW1H 0BG GB 03/2030 7373
4400000000000008 Visa 1 Infinite Loop Cupertino, CA. 95014 US 03/2030 737
4444333322221111 Visa 8-10 Broadway, Westminster, London. SW1H 0BG GB 03/2030 737

Refer to the list of the avsResult values you can receive.

Test Real Time Account Updater scenarios

To test how different Real Time Account Updater scenarios work for your integration, use the following test card numbers in your payments request.

You can only use our standard Real Time Account Updater services if all of the following conditions are met:

  • The amount specified in the payment is not zero.
  • The shopperInteraction parameter is set to ContAuth.
  • The payment does not contain CVC.

You will receive the corresponding status in the additionalData.realtimeAccountUpdaterStatus field of your response.

Status Card number Expiry Date
CardChanged 5454 5476 9908 4950 03/2030
CardExpiryChanged 5454 5418 5840 6567 Any date except 03/2030
CloseAccount 5454 5415 8031 1093 03/2030
ContactCardAccountHolder 4111 1131 5971 2925 03/2030

If you are not fully PCI compliant and unable to process raw card data, add a prefix of test_ to the credentials. This allows you to test using encrypted card details.

Test submitting encrypted card details

If you want to test API calls from your server but your client-side integration is not ready yet, add a prefix of test_ to the test card credentials.

For example, to use Mastercard test card 5555555555554444, specify the following in your /payments request:

{
...
"paymentMethod": {
    "type": "scheme",
    "encryptedCardNumber": "test_5555555555554444",
    "encryptedExpiryMonth": "test_03",
    "encryptedExpiryYear": "test_2030",
    "encryptedSecurityCode": "test_737"
  }
}

Test submitting Level 2/3 data

Contact our Support Team to enable the includeEnhancedSchemeDataLevel setting in your Customer Area.

To verify that you are correctly sending Level 2 or Level 3 data, submit a /payments request with one of the following card numbers. The card numbers correspond to a type of response:

Card number Expiry Date CVC Response
4444 3333 2222 1111 03/2030 737 VGIS
2222 4107 4036 0010 03/2030 737 L2
5555 5555 5555 4444 03/2030 737 L3

If you receive one of the above responses in an additionalData object (for example, "cardSchemeEnhancedDataLevel" : "L2") , you have successfully set up your account to handle Level 2 or Level 3 data.

American Express (Amex)

Card Number Issuing Country Expiry Date CID
3700 0000 0000 002 NL 03/2030 7373
3700 0000 0100 018
security code optional
NL 03/2030 7373

Bancontact (BCMC)

Card Number Card Type CVV2/CVC2 Username Password Issuing Country Expiry Date
6703 4444 4444 4449 BCMC / Maestro None user password BE 03/2030
6703 0000 0000 0000 003 BCMC / Maestro None user password BE 03/2030
4871 0499 9999 9910 1 BCMC / Visa Debit BCMC: None
Visa: 737
user password BE 03/2030

1 Depending on your payment method setup, transactions with this test card are routed to Bancontact or Visa.

Cartes Bancaires

Card Number Card Type Issuing Country Expiry Date CVV2/CVC3
4035 5010 0000 0008 Visa Debit / Cartes Bancaires FR 03/2030 737
4360 0000 0100 0005 Cartes Bancaires FR 03/2030 737

China UnionPay

ExpressPay Credit Card (cup)

Card Number Expiry Date CVC Issuing Country
8171 9999 2766 0000 10/2030 737 CN
8171 9999 0000 0000 021 10/2030 737 CN
6243 0300 0000 0001 12/2029 737 CN

SMS verification codes:

Channel Verification code
Mobile 123456
Desktop 111111

Dankort

Card Number Expiry Date CVV2/CVC3
5019 5555 4444 5555 03/2030 737

Diners

Card Number Issuing Country Expiry Date CVV2/CVC3
3600 6666 3333 44 US 03/2030 737
3607 0500 0010 20
security code optional
NL 03/2030 737

Discover

Card Number Issuing Country Expiry Date CVD/CID
6011 6011 6011 6611 US 03/2030 737
6445 6445 6445 6445 GB 03/2030 737

Elo

Card Number Issuing Country Expiry Date CVE
5066 9911 1111 1118 BR 03/2030 737

Hipercard

Card Number Issuing Country Expiry Date CVV2/CVC3
6062 8288 8866 6688 BR 03/2030 737

JCB

Card Number Card Type Issuing Country Expiry Date CVV2/CVC3
3569 9900 1009 5841 Consumer US 03/2030 737

Maestro

For online Maestro payments, 3D Secure is mandatory. See Test 3D Secure 2 authentication.

Card Number Issuing Country Expiry Date CVV2/CVC3
6771 7980 2100 0008 US 03/2030 737

Mastercard

Card Number Card Type Issuing Country Expiry Date CVC3
2222 4000 7000 0005 Commercial Debit CA 03/2030 737
5555 3412 4444 1115

security code optional

Consumer NL 03/2030 737
5577 0000 5577 0004 Consumer PL 03/2030 737
5555 4444 3333 1111 Consumer GB 03/2030 737
2222 4107 4036 0010 Corporate NL 03/2030 737
5555 5555 5555 4444 Corporate GB 03/2030 737
2222 4107 0000 0002 Corporate Credit NL 03/2030 737
2222 4000 1000 0008 Credit CA 03/2030 737
2223 0000 4841 0010 Credit NL 03/2030 737
2222 4000 6000 0007 Debit CA 03/2030 737
2223 5204 4356 0010 Debit NL 03/2030 737
2222 4000 3000 0004 Fleet Credit CA 03/2030 737
5100 0600 0000 0002 Premium Credit US 12/2029 737
2222 4000 5000 0009 Purchasing Credit CA 03/2030 737
5103 2219 1119 9245 Prepaid BR 03/2030 737

UATP

Card Number Card Type Expiry Date CVV2/CVC3
1354 1001 4004 955 UATP 03/2030 None

Visa

Card Number Card Type Issuing Country Expiry Date CVV2
4111 1111 4555 1142
security code optional
Classic NL 03/2030 737
4111 1120 1426 7661
eight-digit BIN
Debit FR 12/2030 737
4988 4388 4388 4305 Classic ES 03/2030 737
4166 6766 6766 6746 Classic NL 03/2030 737
4646 4646 4646 4644 Classic PL 03/2030 737
4000 6200 0000 0007 Commercial Credit US 03/2030 737
4000 0600 0000 0006 Commercial Debit US 03/2030 737
4293 1891 0000 0008 Commercial Premium Credit AU 03/2030 737
4988 0800 0000 0000 Commercial Premium Debit IN 03/2030 737
4111 1111 1111 1111 Consumer NL 03/2030 737
4444 3333 2222 1111 Corporate GB 03/2030 737
4001 5900 0000 0001 Corporate Credit IL 03/2030 737
4000 1800 0000 0002 Corporate Debit IN 03/2030 737
4000 0200 0000 0000 Credit US 03/2030 737
4000 1600 0000 0004 Debit IN 03/2030 737
4002 6900 0000 0008 Debit AU 03/2030 737
4400 0000 0000 0008 Debit US 03/2030 737
4484 6000 0000 0004 Fleet Credit US 03/2030 737
4607 0000 0000 0009 Fleet Debit MX 03/2030 737
4977 9494 9494 9497 Gold FR 03/2030 737
4000 6400 0000 0005 Premium Credit AZ 03/2030 737
4003 5500 0000 0003 Premium Credit TW 03/2030 737
4000 7600 0000 0001 Premium Debit MU 03/2030 737
4017 3400 0000 0003 Premium Debit RU 03/2030 737
4005 5190 0000 0006 Purchasing Credit US 03/2030 737
4131 8400 0000 0003 Purchasing Debit GT 03/2030 737
4035 5010 0000 0008 Visa FR 03/2030 737
4151 5000 0000 0008 Visa Credit US 03/2030 737
4199 3500 0000 0002 Visa Proprietary FR 03/2030 737

Visa Electron

Card Number Issuing Country Expiry Date CVV2/CVC3
4001 0200 0000 0009 BR 03/2030 737

V Pay

Card Number Issuing Country Expiry Date CVV2/CVC3
4013 2500 0000 0000 006 PL 03/2030 737

See also