Generate Bulk Fake Credit Card Numbers
Generate bulk sample credit card numbers for payment testing and checkout mockups. Select card brands to explore BIN structures and number formats. Each generated card includes a valid Luhn checksum, a future expiration date, and a dummy CVV.
Credit card number formats and BIN guide
Card brands use different number lengths, prefixes, and security-code fields. This generator uses the selected formats below. Some networks support additional lengths or prefix families; these output rules are not a complete production card-validation specification.
| Card brand | Digits | Network prefix | Grouping | Security code |
|---|---|---|---|---|
| Visa | 16 | 4 | 4–4–4–4 | 3-digit CVV |
| Mastercard | 16 | 51–55 or 2221–2720 | 4–4–4–4 | 3-digit CVC |
| American Express | 15 | 34 or 37 | 4–6–5 | 4-digit CID |
| Discover | 16 | 6011 | 4–4–4–4 | 3-digit CID |
| JCB | 16 | 3528–3589 | 4–4–4–4 | 3-digit CVV |
| Diners Club | 14 | 36 | 4–6–4 | 3-digit CVV |
| UnionPay | 16 | 620 | 4–4–4–4 | 3-digit CVN |
A network prefix helps recognize a card brand. A BIN, also called an IIN, identifies an issuer account range and can use six or eight digits. A randomly generated prefix does not establish an issuing bank or an active account.
How to read a sample Visa number
Format example: 4242 4242 4242 4242
424242Illustrative 6-digit prefix424242424Remaining sample digits2Luhn check digitThe illustrated prefix is not a verified issuer BIN. The first segment illustrates a six-digit boundary; an eight-digit BIN has a different boundary. This example explains the number structure without identifying a bank or card product.
What does the Luhn checksum validate?
Luhn calculates a check digit from the other digits in a card number. It helps a form detect many typing errors. Every generated sample passes this calculation, but a correct checksum does not verify an issued card, its security code, available funds, or payment authorization.
How to generate a batch of sample cards
- Choose a card brand or keep all brands selected.
- Generate a batch of sample cards and review their numbers, expiry dates, and dummy security codes.
- Copy the numbers or download CSV or JSON for form checks, mockups, and test datasets.
When importing CSV into a spreadsheet, set the number and security-code columns to Text to preserve every digit and leading zeros. JSON stores these values as strings.
For payment authorization tests, use your gateway’s documented sandbox cards. Random samples are useful for local validation and layouts; a gateway may require its own specific test numbers to simulate a payment result.