Skip to main content
Screendesk
Free tool

Test Credit Card Numbers

Stripe, Braintree, and Adyen test cards for successful payments, declines, and 3D Secure, with a Luhn validator and a generator for form testing.

Open source on GitHub

Use any future expiry date and any 3-digit CVC (4 digits for American Express). Test mode keys only.

Test card numbers change; check the provider’s docs. List checked October 2026. Stripe testing docs

Stripe test card numbers
Card numberBrandScenarioCopy
4242 4242 4242 4242VisaSuccessful payment
4000 0566 5566 5556VisaSuccessful payment (debit)
5555 5555 5555 4444MastercardSuccessful payment
5200 8282 8282 8210MastercardSuccessful payment (debit)
2223 0031 2200 3222MastercardSuccessful payment (2-series)
3782 822463 10005American ExpressSuccessful payment
6011 1111 1111 1117DiscoverSuccessful payment
3566 0020 2036 0505JCBSuccessful payment
4000 0000 0000 0002VisaGeneric decline
4000 0000 0000 9995VisaInsufficient funds
4000 0000 0000 9987VisaLost card
4000 0000 0000 9979VisaStolen card
4000 0000 0000 0069VisaExpired card
4000 0000 0000 0127VisaIncorrect CVC
4000 0000 0000 0119VisaProcessing error
4000 0025 0000 3155Visa3D Secure: authenticate unless set up for future payments
4000 0027 6000 3184Visa3D Secure: always authenticate

Luhn validator

Checks the mod 10 checksum and brand prefix. Runs in your browser; nothing is sent anywhere. Don’t paste real card numbers.

Enter at least 12 digits to check.

Luhn-valid number generator

Testing only

Synthetic numbers that pass the Luhn check, for form validation and input-mask testing. They are not real cards and will not work in Stripe, Braintree, or Adyen sandboxes. Use the provider tables above for payment flows.

Expiry and CVC

Expiry and CVC by provider. What to enter alongside the test card number.

Test card expiry date and CVC rules by payment provider
ProviderExpiry dateCVCEnvironmentSource
StripeAny future dateAny 3 digits (4 for Amex)Test-mode API keysdocs.stripe.com/testing
BraintreeA future dateAny; 200 and 201 trigger CVV responses when rules are onSandbox accountBraintree testing reference
Adyen03/30737 (7373 for Amex); optional on some cardsTest environmentAdyen test card numbers
Testing payments

How to test a checkout. Success is one card. The bugs live in the other scenarios.

  • Use test-mode keys

    Test cards only work with the provider’s sandbox or test-mode API keys. In live mode they are declined, and real cards never belong in test mode.

  • Cover the unhappy paths

    Run declines, insufficient funds, expired cards, and 3D Secure challenges, not just the success card. Most checkout bugs sit in error handling.

  • Capture what failed

    When a payment test fails, record the error message, the network response from your server, and the provider’s request ID so a developer can reproduce it.

FAQ

Frequently asked questions

What is the Stripe test card number?

The most used Stripe test card is 4242 4242 4242 4242 (Visa), which simulates a successful payment. Use any future expiry date and any 3-digit CVC. Stripe also publishes cards that simulate declines, such as 4000 0000 0000 0002 for a generic decline and 4000 0000 0000 9995 for insufficient funds.

Can I use these test credit card numbers to buy things?

No. Test card numbers only work in a payment provider’s sandbox or test mode. They are not linked to any account, carry no funds, and are declined in live mode.

Do the generated Luhn-valid numbers work in Stripe or Braintree?

No. The generator creates synthetic numbers that pass the Luhn checksum, which is useful for testing form validation, input masks, and brand detection. Payment sandboxes only accept their own published test numbers, listed in the tables above.

How do I test a 3D Secure payment?

Use a card the provider marks as requiring authentication, for example Stripe’s 4000 0027 6000 3184 or Adyen’s 3D Secure 2 test card. The sandbox shows a test challenge page where you can approve or fail the authentication.

Why did my test card stop working?

Providers occasionally change or retire test numbers and scenarios. Check the provider’s testing docs for the current list, confirm you are using test-mode keys, and check that your integration isn’t blocking the card through its own validation or fraud rules.

Customer support runs on Screendesk.

Start for free