Generate 15-Digit Amex Card Numbers
Generate sample American Express credit card numbers featuring standard 34 and 37 BIN prefixes. Each card includes a 15-digit Luhn-compliant number, a 4-digit dummy CID, and upcoming expiration details.
American Express number format and BIN guide
American Express numbers are displayed in a 4–6–5 grouping rather than four groups of four. The security code is four digits. These differences make Amex samples useful for testing input masks, character limits, card previews, and security-code validation.
- Card number length
- 15 digits
- Generated network prefixes
- 34 or 37
- Security code
- 4-digit CID
- Display grouping
- 4–6–5
34 and 37 are American Express network prefixes. Neither two-digit prefix is a complete BIN/IIN or evidence of a specific card product. The generated number and CID are independent sample values and are not issued account credentials.
How to read a sample American Express number
Format example: 3782 822463 10005
378282Illustrative 6-digit prefix24631000Remaining sample digits5Luhn 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.