Skip to main content

Test Cards

When you're building or testing your Yeti integrations that use Adyen (for example, Yeti ECOM with Adyen Drop-in/Components), you should use Adyen's official test card numbers. These only work on Adyen's test platform, and are ideal for exercising the different flows and result codes you'll see in production.

For the full, always up-to-date list of cards and scenarios, see Adyen test card numbers.

General notes​

  • Environment: These cards only work with Adyen's test endpoints. Use them together with Yeti's test base URLs (for example, https://test.yeti.host/v1/ecom) and Adyen's environment: 'test' on the frontend.
  • No real money: Transactions created with these cards in the test environment don't move real funds.
  • 3D Secure: Some cards are enrolled in 3D Secure 2 so you can test challenge/frictionless flows.

Commonly used cards​

Below are some of the most useful test cards you can use for end-to-end testing. For more brands and scenarios, refer to the Adyen documentation.

Visa (authorised)​

  • Number: 4111 1111 1111 1111
  • Expiry: any future date (for example, 03/2030)
  • CVC: any 3 digits (for example, 737)
  • Behaviour: Standard successful authorisation.

Mastercard (authorised)​

  • Number: 5555 5555 5555 4444
  • Expiry: any future date
  • CVC: any 3 digits
  • Behaviour: Standard successful authorisation.

American Express (authorised)​

  • Number: 3700 0000 0000 002
  • Expiry: any future date
  • CID: any 4 digits (for example, 7373)
  • Behaviour: Standard successful authorisation.

Testing 3D Secure 2​

Adyen provides specific cards that trigger 3D Secure 2 so you can verify your handling of redirects and additional details:

  • Visa – 3DS2 challenge
    • Example: a Visa card that consistently triggers a 3DS2 challenge.
  • Mastercard – 3DS2 challenge
    • Example: a Mastercard card enrolled for 3DS2.

Use these together with:

  • The Adyen Drop-in or Components (which will show the 3DS challenge to the shopper).
  • Yeti's /payments and /payments/details endpoints for your server-side integration.

For exact card numbers and the latest list of 3DS2 scenarios, see Adyen test card numbers.

Other brands and scenarios​

Adyen also provides test cards for:

  • Alternative schemes and regions (for example, Bancontact, Cartes Bancaires, Dankort, China UnionPay, Elo, Hipercard, JCB, Maestro, UATP, and others).
  • US debit routing scenarios (Visa, Mastercard, Discover debit with domestic networks).
  • Failure and edge cases, such as:
    • Refused transactions
    • Various result codes and refusal reasons
    • Different risk and fraud flows (when used with RevenueProtect)

Because these lists change over time, you should always use the official reference at Adyen test card numbers as the source of truth.