Random UnionPay Card Number Generator

UnionPay number format and BIN guide

UnionPay supports more number lengths and ranges than this page generates. The 620 family keeps these fixtures within a clear, commonly recognized range. All samples here pass Luhn, although some payment libraries do not require Luhn for every real UnionPay card.

Card number length

16 digits

Generated network prefixes

620

Security code

3-digit CVN

Display grouping

4–4–4–4

620 is a selected network prefix, not a full BIN/IIN. It avoids partner-range ambiguity in these sample fixtures. A generated six-digit or eight-digit prefix does not prove an issuing bank, country, card product, or live account.

How to read a sample UnionPay number

Format example: 6200 0000 0000 0005

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.