Random Diners Club Card Number Generator

Diners Club number format and BIN guide

Diners Club samples use a 4–6–4 grouping. The 14-digit format is useful for checking that a form does not hard-code a 16-digit requirement. Other Diners Club and partner-network formats exist; the output here is specifically the classic 36-prefix format.

Card number length

14 digits

Generated network prefixes

36

Security code

3-digit CVV

Display grouping

4–6–4

36 identifies the selected Diners Club format, but it is only a two-digit network prefix. It is not a complete BIN/IIN and does not establish an issuer or an account. Partner-network acceptance can vary by payment provider and cannot be determined from a dummy card number.

How to read a sample Diners Club number

Format example: 3622 720627 1667

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.