The Complete Stripe Test Cards Reference (Every Scenario in 2026)
Every Stripe test card you need — successful charges, declines, 3D Secure, disputes, SCA, regional cards, and the magic amounts that trigger specific failures.
· 9 min read
Stripe ships dozens of test cards, but most of them are scattered across the docs. This is the consolidated reference: every scenario you actually need to test, with the exact card number, expected behavior, and the gotchas that catch teams out the first time.
How Stripe test mode works
Test mode accepts any future expiry date, any 3-digit CVC (4-digit for Amex), and any postal code. Real card numbers will not work — you must use Stripe's published test numbers. Charges in test mode never touch a real card and never appear on a statement.
Switch your dashboard to test mode (toggle in the top nav) and use your test API keys (`pk_test_...` and `sk_test_...`). Live keys reject the test cards below with a `card_declined` error.
Successful payment cards
Visa: 4242 4242 4242 4242. Visa (debit): 4000 0566 5566 5556. Mastercard: 5555 5555 5555 4444. Mastercard (debit): 5200 8282 8282 8210. Mastercard (prepaid): 5105 1051 0510 5100. American Express: 3782 822463 10005. Discover: 6011 1111 1111 1117. Diners Club: 3056 9300 0902 0004. JCB: 3566 0020 2036 0505. UnionPay: 6200 0000 0000 0005.
Decline scenarios
Generic decline: 4000 0000 0000 0002. Insufficient funds: 4000 0000 0000 9995. Lost card: 4000 0000 0000 9987. Stolen card: 4000 0000 0000 9979. Expired card: 4000 0000 0000 0069. Incorrect CVC: 4000 0000 0000 0127. Processing error: 4000 0000 0000 0119. Velocity limit exceeded: 4000 0000 0000 6975.
These all decline at the authorization step. To test post-authorization failures, see the dispute and refund cards below.
3D Secure and SCA
3DS authentication required (always challenge): 4000 0027 6000 3184. 3DS authentication required (frictionless, succeeds): 4000 0025 0000 3155. 3DS supported but not required: 4000 0000 0000 3055. 3DS authentication fails: 4000 0084 0000 1629. Insufficient funds after successful 3DS: 4000 0082 6000 3178.
Use these to verify SCA-compliant flows in EU/UK markets. The challenge appears as a Stripe-hosted modal in test mode — click 'Complete' or 'Fail' to simulate the user's response.
Disputes and chargebacks
Charge succeeds, then disputed as fraudulent: 4000 0000 0000 0259. Disputed as not received: 4000 0000 0000 2685. Disputed and you win: 4000 0000 0000 1976. Disputed and you lose (inquiry closed): 4000 0000 0000 5423. Trigger the dispute manually from the dashboard's Payments page after the charge clears.
Refunds and partial captures
Most successful cards (4242…) support partial refunds and partial captures out of the box. To test refund failures use 4000 0000 0000 5126 — the refund will succeed initially then fail asynchronously, mirroring real-world bank rejections you must handle.
Regional and local payment methods
Brazil (CartesBancaires): 4000 0007 6000 0002. India (RuPay, requires e-mandate): 4000 0035 6000 0008. Australia (BECS direct debit success): use account 900123456 with BSB 000-000. SEPA debit success: DE89 3704 0044 0532 0130 00. iDEAL, Bancontact, Sofort, and Klarna all use redirect flows with 'Authorize Test Payment' buttons in test mode — no card needed.
Card brand and BIN testing
To verify your UI shows the right card brand, use the brand-specific success cards above. To test cards that look like one brand but are issued by another, use 4000 0566 5566 5556 (Visa debit) and 5200 8282 8282 8210 (Mastercard debit). Some merchants route debit and credit through different processors — these are how you flush out routing bugs.
Stop pasting these by hand
Every QA engineer ends up with a Notion page or sticky notes full of these numbers. Drop them into a TestAssets list organized by scenario (success, decline, 3DS, dispute) and paste straight into your checkout form from the browser, desktop, or mobile autofill — no typos, no expired tab.