A Stripe test card is a fake card number that works only in Stripe test mode. A charge built with one routes through Stripe's sandbox, so you can watch your checkout handle approvals, declines, and 3D Secure prompts without moving real money. Stripe publishes these numbers in its API docs, and they cost nothing to use.
Test mode runs on separate keys, usually prefixed pk_test and sk_test. Customers, charges, and subscriptions you create there stay in the sandbox and never appear in your live account. A test card typed against a live key gets rejected.
Start with 4242 4242 4242 4242. It is the Visa number Stripe documents for a plain successful charge, and it also attaches to a saved customer record.
Reach for the decline numbers before launch. A checkout that handles the happy path but breaks on a failed payment will cost you support tickets.
Stripe keeps a set of cards that force an authentication step, including 4000 0025 0000 3155 and several numbers in the 4000 0000 0000 3xxx range. Use them to see the challenge screen, the redirect, and the return URL in your app. The card you need depends on the 3D Secure version your account uses, so check the Stripe docs list before you build a test plan.
Use any 3-digit CVC, any 4-digit CVC for Amex, and any future expiry date. Any billing ZIP works on a standard test charge that succeeds.
Some decline cards return their code no matter what you type in the CVC field. Change the card number, not the CVC, when you want a different error.
Stripe also exposes test tokens such as tok_visa and test payment method IDs such as pm_card_visa. They stand in for raw card numbers in server-side calls, which keeps your suite short and stops you from pasting numbers into fixtures.
For client-side testing, Stripe's own browser test helpers fill the card field for you.
No. Live keys reject every published test number. Test numbers sit in public documentation, so a processor that accepted them would be handing out free goods.
If a charge against a live key returns a decline for 4242 4242 4242 4242, that result is correct. The problem is the key, not the number.
One more detail: these numbers are public. Anyone can type them. They identify no person and prove nothing about a card.
No. Selling a real card number, CVC, or full track data is illegal in the US and in most other countries, and the FTC treats it as fraud. Sites that trade card data operate outside the law and outside the card networks.
PCI DSS bans keeping the CVC or CVV2 in any form after a transaction authorizes. That rule covers merchants, processors, and anyone else in the payment chain.
For developers, the clean path is Stripe test mode plus the test cards listed above. You get the same request and response shapes with no legal exposure.
Yes. In test mode it creates a customer, saves the card, and starts a subscription. Pair it with a test clock to move through billing cycles.
Because Stripe blocks every published test number outside test mode. Switch to your test keys and try again.
Stripe's API documentation holds the master list, grouped by decline reason and by region. Treat that page as the source of truth when a number copied from a blog post stops working.
You will receive the digital voucher immediately.
All your data is transmitted with unbreakable SSL-RSA encryption.
You can give away, resell or keep the vouchers.
We are available for you 24 hours a day.
Be informed as soon as new vouchers are added or when there are discounts.