Test Credit Card Number Generator
Generate Luhn-valid Visa, Mastercard, American Express, and Discover numbers for testing checkout forms — plus the official Stripe and PayPal sandbox test cards. Nothing is a real card; nothing leaves your browser.
For software testing only. Every number on this page is fake — none of them are valid for a real purchase.
For software testing only — not valid cards
These numbers are fake and not valid for any real transaction. They only pass a Luhn checksum, the same math-only sanity check every real card number happens to satisfy — they are not issued by any bank, are not linked to any funds, and will be declined by every real payment processor. Use them only to test form fields and client-side validation logic, never to attempt an actual purchase.
What is a test credit card number?
A test credit card number is a string of digits that has the same structure as a real card — the right length, the right issuer prefix, and a valid Luhn checksum — without belonging to an actual account. Card networks and payment processors use them (and so does this tool) to exercise checkout forms, client-side validation, and payment integrations without ever touching real money or real cardholder data.
How Luhn validation works
Every major card network uses the Luhn algorithm as a first-pass sanity check before a number is even sent to a processor. Starting from the rightmost digit, every second digit is doubled (subtracting 9 if the result is over 9), and all digits are summed. A valid card number's total is always a multiple of 10. This tool computes a genuine Luhn check digit for every number it generates, so anything that validates card format client-side — length, prefix, checksum — will accept these numbers just like a real one.
Official Stripe test cards
If you're integrating with Stripe, use their published test numbers instead of a random Luhn-valid one — Stripe's test mode reads the specific digits to simulate a scenario. Use any future expiry date and any 3-digit CVC (4 digits for Amex).
| Brand | Number | Scenario | |
|---|---|---|---|
| Visa | 4242 4242 4242 4242 | Success — the default test card | |
| Visa (debit) | 4000 0566 5566 5556 | Success, as a debit card | |
| Mastercard | 5555 5555 5555 4444 | Success | |
| Mastercard (2-series) | 2223 0031 2200 3222 | Success | |
| American Express | 3782 822463 10005 | Success — use a 4-digit CVC | |
| Discover | 6011 1111 1111 1117 | Success | |
| Visa | 4000 0000 0000 0002 | Generic decline | |
| Visa | 4000 0000 0000 9995 | Decline — insufficient funds | |
| Visa | 4000 0000 0000 0069 | Decline — expired card | |
| Visa | 4000 0000 0000 0127 | Decline — incorrect CVC | |
| Visa | 4000 0027 6000 3184 | Requires 3D Secure authentication |
Source: Stripe testing documentation. Stripe periodically expands this list — check their docs for the full set of decline and 3D Secure scenarios.
Official PayPal sandbox test cards
PayPal's sandbox accepts these static numbers for Expanded Checkout testing. Use any future expiration
date. Since sandbox cards don't carry a real CVV, PayPal's docs note you can use 123 for
Visa, Mastercard, Discover, and Diners Club, or 1234 for American Express.
| Brand | Number | Note | |
|---|---|---|---|
| Visa | 4111 1111 1111 1111 | CVV 123 | |
| Mastercard | 2223 0000 4840 0011 | CVV 123 | |
| American Express | 3714 4963 5398 431 | CVV 1234 | |
| American Express | 3766 8081 6376 961 | CVV 1234 | |
| Diners Club | 3646 1510 0000 39 | CVV 123 | |
| Maestro | 6304 0000 0000 0000 | CVV 123 | |
| JCB | 3636 5000 0000 0260 | CVV 123 |
Source: PayPal sandbox card testing documentation. PayPal also offers a dashboard generator for additional one-off numbers.
What's included
- Card number — Luhn-valid, formatted for the brand (4-4-4-4, or 4-6-5 for Amex)
- Brand — Visa, Mastercard, American Express, or Discover, matched by IIN prefix
- Expiry date — a random future MM/YY
- CVV — 3 digits, or 4 for American Express
- Cardholder name — a fake name to pair with the number
Use cases
- Checkout form testing — verify client-side format and Luhn validation without a real card
- UI and demo screenshots — populate a payment form without exposing anything sensitive
- QA fixtures — generate a batch of numbers across brands for automated test suites
- Payment gateway integration — pair these with Stripe's or PayPal's official numbers to trigger specific processor responses
Important: none of these cards are valid
Every number on this page — generated or from the reference tables — is fake and cannot be used to pay for anything. Passing a Luhn check only proves a number is structurally valid; it says nothing about whether an account exists behind it. These numbers are not tied to any bank, cardholder, or funds, and no real payment processor will authorize a charge against them, outside of the specific Stripe and PayPal sandbox numbers above, which only work inside those companies' own test environments and never move real money. Do not enter any number from this page anywhere expecting a real transaction to complete, and never present it as a genuine payment method.
Fill checkout forms without copy-pasting
The FormFiller extension fills the rest of a checkout form — name, email, billing address — in one click, so you only have to think about the card field you're actually testing. For a full walkthrough of testing checkout flows end to end, see How to Test Checkout Forms Without Real Card Data.
Frequently asked questions
Will any of these numbers actually charge money?
No. None of the generated or reference numbers are attached to a real bank, cardholder, or funds. Outside of the Stripe and PayPal sandbox numbers — which only work inside those companies’ own test environments — no real payment processor will authorize a charge against any number on this page.
Why do fake numbers pass Luhn validation if they are not real cards?
The Luhn algorithm is a checksum that only proves a number is structurally well-formed — the right length, issuer prefix, and check digit. It cannot verify that an account actually exists behind the number, which is why a Luhn-valid number is still perfectly safe to use as fake test data.
Can I use these numbers for a real purchase instead of my own card?
No. These numbers exist purely for testing checkout forms, client-side validation, and payment integrations during development. Attempting to use one for a real transaction will simply be declined.
What is the difference between the generated numbers and the Stripe/PayPal test cards?
The generated numbers are random but Luhn-valid, useful for generic format and validation testing across any brand. The Stripe and PayPal numbers are specific, published values that those processors’ sandboxes recognize to simulate exact scenarios, like a decline or a 3D Secure challenge.