Test Card Generator
Published test card numbers for Visa, Mastercard, Amex, Discover, JCB, Diners and UnionPay — with the CVC, expiry and ZIP rules — for approved, declined, CVC/AVS check and 3D Secure scenarios. A selection of Stripe’s official test cards plus classic PayPal Payflow and Braintree sandbox numbers.
Follows Stripe test cards · Braintree and PayPal Payflow sandbox lists · ISO/IEC 7812-1 Luhn·verified Oct 2026· double-checked Oct 2026— 31 PANs Luhn- and IIN-checked independently; Stripe rows confirmed from Stripe’s own repository fixtures, seven from secondary copies
Use test data only. All calculations run locally in your browser — PayProbe never sees, transmits, or stores your PAN, CVV, keys, PINs, or cryptographic inputs. How we handle data →
| Scheme | PAN | Expiry | CVC | Scenario | Works in | Notes | |
|---|---|---|---|---|---|---|---|
| Visa | 4242424242424242 | 12/29 | 123 | Approved | Stripe | The standard Stripe test card | |
| Visa | 4000056655665556 | 12/29 | 123 | Approved | Stripe | Visa debit | |
| Mastercard | 5555555555554444 | 12/29 | 123 | Approved | Stripe | Mastercard | |
| Mastercard | 2223003122003222 | 12/29 | 123 | Approved | Stripe | Mastercard 2-series BIN | |
| Mastercard | 5200828282828210 | 12/29 | 123 | Approved | Stripe | Mastercard debit | |
| Mastercard | 5105105105105100 | 12/29 | 123 | Approved | Stripe | Mastercard prepaid; also on PayPal Payflow’s list | |
| Amex | 378282246310005 | 12/29 | 1234 | Approved | Stripe | 15 digits, 4-digit CVC | |
| Amex | 371449635398431 | 12/29 | 1234 | Approved | Stripe | Second Stripe Amex | |
| Discover | 6011111111111117 | 12/29 | 123 | Approved | Stripe | Discover | |
| Discover | 6011000990139424 | 12/29 | 123 | Approved | Stripe | Discover (alternative) | |
| Diners | 3056930009020004 | 12/29 | 123 | Approved | Stripe | Diners Club, 16 digits | |
| Diners | 36227206271667 | 12/29 | 123 | Approved | Stripe | Diners Club, 14 digits | |
| JCB | 3566002020360505 | 12/29 | 123 | Approved | Stripe | JCB | |
| UnionPay | 6200000000000005 | 12/29 | 123 | Approved | Stripe | UnionPay | |
| Visa | 4000000000000002 | 12/29 | 123 | Generic decline | Stripe | card_declined / generic_decline | |
| Visa | 4000000000009995 | 12/29 | 123 | Insufficient funds | Stripe | card_declined / insufficient_funds | |
| Visa | 4000000000009987 | 12/29 | 123 | Lost card | Stripe | card_declined / lost_card | |
| Visa | 4000000000000069 | 12/29 | 123 | Expired card | Stripe | expired_card, even with a future expiry date | |
| Visa | 4000000000000127 | 12/29 | 123 | Incorrect CVC | Stripe | incorrect_cvc | |
| Visa | 4000000000000119 | 12/29 | 123 | Processing error | Stripe | processing_error | |
| Visa | 4000000000000101 | 12/29 | 123 | CVC check fails | Stripe | If you send a CVC, cvc_check = fail; declined if your Radar rules block failed CVC checks | |
| Visa | 4000000000000028 | 12/29 | 123 | Address check fails | Stripe | address_line1_check = fail; succeeds unless a custom Radar rule blocks it | |
| Visa | 4000000000000036 | 12/29 | 123 | ZIP check fails | Stripe | If you send a postal code, address_zip_check = fail; declined if your Radar rules block failed ZIP checks | |
| Visa | 4000000000000044 | 12/29 | 123 | Checks unavailable | Stripe | address_line1_check and address_zip_check = unavailable; succeeds unless a Radar rule blocks it | |
| Visa | 4000000000003220 | 12/29 | 123 | 3DS required | Stripe | 3DS2 authentication must be completed to succeed | |
| Visa | 4000000000003055 | 12/29 | 123 | 3DS supported | Stripe | 3DS may run but is not required; not requested by default | |
| Visa | 4000008400001629 | 12/29 | 123 | 3DS then declined | Stripe | 3DS required; declined (card_declined) after authentication | |
| Visa | 4111111111111111 | 12/29 | 123 | Usually approved | Braintree, PayPal Payflow | The most widely listed test Visa | |
| Diners | 30569309025904 | 12/29 | 123 | Usually approved | PayPal Payflow | 14-digit Diners Club; Payflow’s test number (not on Braintree’s list) | |
| Diners | 36259600000004 | 12/29 | 123 | Usually approved | Braintree | 14-digit Diners Club; Braintree’s test number | |
| JCB | 3530111333300000 | 12/29 | 123 | Usually approved | Braintree, PayPal Payflow | Classic test JCB |
What this generator is for
Payments engineers cannot test an authorisation flow, a tokenisation pipeline, or a fraud rule against real cardholder data — that would be a PCI DSS violation. Instead they use test card numbers: synthetic PANs that are structurally valid (correct BIN range, correct length, passing the Luhn check) but are not linked to any real account and cannot move money. This tool collects those values for sandbox and certification environments: it lists published test numbers rather than generating random ones (for random Luhn-valid PANs and track data use the Card Data Generator).
The numbers are ones gateways publish for exactly this purpose: a selection of Stripe’s official test cards (see Stripe’s testing docs for the full list), plus classic numbers from the PayPal Payflow and Braintree sandbox lists — the “Works in” column says which. Other gateways accept only their own lists. They are recognised only by test/sandbox systems; presenting one to a live acquirer simply returns a decline. Use them to seed unit tests, drive checkout scenarios, or validate that your software handles each scheme’s format correctly.
Which CVC, expiry date and ZIP code should I use?
With Stripe test cards any future expiry date works, any 3-digit CVC (4 digits for American Express) and any ZIP or postal code. The CVC and address checks only fail when you use the cards made for that: 4000 0000 0000 0101 fails the CVC check, 4000 0000 0000 0028 the address line check and 4000 0000 0000 0036 the ZIP (postal code) check. The CVC and ZIP checks only run when you send a CVC or postal code; the payment then succeeds unless your Radar rules block failed checks, in which case it is declined — so you can test how your checkout and Radar rules react. 4000 0000 0000 0127 declines with incorrect_cvc. Other gateways publish their own rules (some use fixed CVC values or amounts to trigger results), so check your provider's sandbox documentation.
Why do test numbers fail on a live site?
Test PANs are not linked to any account. A sandbox recognises them and simulates a result; a live gateway sends them to the card network like any other number and gets a decline. To try a real payment end to end, use a real card for a small amount and refund it.
What it is not
This generator does not and cannot create working payment credentials. It has no access to issuer systems, generates no valid CVVs or cryptograms for real accounts, and produces nothing that can authorise a transaction. Never enter a real card number into any test system, and never use a generated number to attempt a real payment.