Random JCB Card Number Generator

JCB number format and BIN guide

JCB samples are grouped into four blocks of four digits. The 3528–3589 range is more precise than accepting every number starting with 35. Other JCB number lengths exist; this page focuses on the 16-digit format for predictable fixtures and card previews.

Card number length

16 digits

Generated network prefixes

3528–3589

Security code

3-digit CVV

Display grouping

4–4–4–4

The four-digit prefix range is a brand-detection rule rather than a full BIN directory. A random prefix inside that range does not establish a Japanese issuer, a particular bank, or an active account. Use verified issuer data when your application requires those facts.

How to read a sample JCB number

Format example: 3566 0020 2036 0505

The 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

1. Choose a card brand or keep all brands selected.
2. Generate a batch of sample cards and review their numbers, expiry dates, and dummy security codes.
3. 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.