Where to Find Stripe Test Card Numbers

Stripe publishes its test card numbers for free in its own documentation, on the Testing page of the Stripe docs. You do not need to buy a list, subscribe to a channel, or pay anyone for access. The best known number is 4242 4242 4242 4242, which returns a successful charge in test mode with any future expiry date and any three digit CVC. The same page lists numbers that trigger specific outcomes: a declined charge, a 3D Secure challenge, an insufficient funds error, or a lost or stolen card response. All of them work only with a test mode API key, and all of them cost nothing.

synonym stripe fake card number generator

If someone offers to sell you "fresh Stripe test cards," treat the offer as either a resale of free public documentation or, far more often, an attempt to move stolen card data. Test numbers carry no resale value because every developer already has them. Real card numbers, CVVs, and fullz are illegal to buy or sell in the United States under 18 U.S.C. 1029, and holding them exposes your own accounts, devices, and identity to the same fraud trade. Buy the documentation habit instead: read the source, test against your own sandbox, and keep live keys out of reach.

related stripe test card numbers vs real card numbers

What to Look For in a Test Card Source

Primary documentation over republished lists

Third party blog posts copy Stripe's table and then go stale. When Stripe adds a card brand or changes a 3D Secure flow, the official page updates and the copies do not. Start at the source and treat every other list as a hint.

related article

Coverage of the outcomes you actually test

A useful source groups numbers by behavior: success, generic decline, insufficient funds, expired card, incorrect CVC, processing error, and authentication required. If a list only gives you one working number, it cannot test your error handling.

related article

Card brand and region coverage

Check that the list includes Visa, Mastercard, American Express, Discover, and at least one international scheme if you sell outside the US. Amex matters because it uses a four digit CVC and a fifteen digit number, which breaks code that assumes sixteen and three.

Authentication test cases

If you handle Strong Customer Authentication or 3D Secure, you need the test cards that force a challenge, force a failure, and force a frictionless pass. These behave differently from the plain success number and are the ones that expose broken checkout flows.

Parameter Bands to Expect

  • Card number length: 15 to 19 digits across brands, with Visa and Mastercard test numbers at 16 digits.
  • Expiry date: any future date in test mode, though dedicated expired card numbers exist for failure testing.
  • CVC: three digits for most brands, four digits for American Express.
  • Postal code and billing address: any value unless the specific test case requires a mismatch.
  • Amount: any value your integration allows, since no funds move in test mode.
  • Key prefix: test keys start with sk_test_ and pk_test_, live keys start with sk_live_ and pk_live_.

How to Use a Test Card Without Breaking Things

  1. Confirm the dashboard is in test mode and the API key in your environment starts with the test prefix.
  2. Run the success number first to prove the happy path, then run decline numbers to prove your error copy and retry logic.
  3. Keep test and live credentials in separate environment files so a live key never reaches a staging deploy.
  4. Log the last four digits and the outcome, never the full number, even in test mode, so your logging habits stay clean in production.
  5. Clear test data before launch so abandoned test customers do not appear in reports.

Common Pitfalls

  • Entering a test number into a live checkout. It will fail, and repeated attempts can trip fraud rules on the account.
  • Hardcoding a single test number across every test so decline paths never run.
  • Paying a seller for a list that Stripe gives away, or worse, accepting what turns out to be stolen data.
  • Storing CVC values after authorization in any environment. PCI DSS forbids retaining sensitive authentication data once a transaction is authorized.
  • Assuming test mode proves a real bank will approve the charge. It proves your integration works, nothing more.

FAQ

Are Stripe test card numbers free?

Yes. They are published in Stripe's public documentation and require no account upgrade, payment, or permission.

Do test card numbers ever charge real money?

No. They resolve only against test mode keys. A test number sent with a live key is treated as an invalid card and declines.

Can I use the same test card for 3D Secure testing?

Not reliably. Stripe publishes separate authentication test cards that force a challenge or a failed authentication, and those are the ones you need.

Someone is selling a pack of verified Stripe test cards. Is that legitimate?

No. Test numbers have no market value, so a paid pack is either copied documentation or a front for stolen card data. Do not buy it.

Where do I find the current list?

On Stripe's own testing documentation page. It is updated whenever new test behaviors ship and is the only list you should trust.