Card

Support Guide

Card Number Format by Network

Compare card number lengths, starting digits, and format differences across major payment networks.

Card numbers are not all built the same way. Networks use their own prefix ranges and permitted lengths, which is why a validator needs more than a generic digits-only check.
Try the validator

Try the validator

You do not need to leave this guide to run a structural check. Use the same validator here, then continue reading if you need more context.

What changes by network

What changes by network

Visa, Mastercard, American Express, Discover, UnionPay, JCB, Maestro, and others do not share identical numbering patterns. Some are always 16 digits, while others can vary.

A good validator combines network pattern recognition with checksum logic instead of treating all card strings as interchangeable.

Why format references still matter

Why format references still matter

Network format guides are useful for product teams, QA engineers, and support staff. They help explain why some test numbers are accepted and others fail instantly.

They are also useful when documenting accepted card types for a checkout or onboarding workflow.

Where format guidance stops

Where format guidance stops

A format guide does not replace live payment checks. It can tell you what a plausible number looks like, but not whether the underlying card account is usable.

For that reason, format reference pages work best as educational support content linked from the main validator.

Supported card formats

Supported card formats

  • VisaStarts with 4 · 16 digits4242 4242 4242 4242
  • Mastercard51–55 or 2221–2720 · 16 digits5500 0000 0000 0004
  • American Express34 or 37 · 15 digits3782 822463 10005
  • Discover6011 or 65 · 16 digits6011 1111 1111 1117
  • UnionPay62 · 16–19 digits6250 9470 0000 0014
  • JCB3528–3589 · 16–19 digits3566 0020 2036 0505
  • Diners Club300–305, 36, 38 · 14 digits3056 9309 0259 04
  • Maestro6304, 6759, 6761–63 · 12–19 digits6759 6498 2643 8453
  • Mir2200–2204 · 16 digits2200 0000 0000 0004
  • RuPay6521, 6522 · 16 digits6521 0000 0000 0000
  • Elo4011, 5066, 6277… · 16 digits6362 9700 0457 9680
  • Troy9792 · 16 digits9792 0303 1010 3019
  • Unknown · 13–19 digits— (Luhn valid, no known BIN)
Use Cases

Use Cases

  • Building clearer checkout requirements by network.
  • Preparing QA test cases by card brand.
  • Helping support teams explain brand-specific format expectations.
FAQ

FAQ

Are all card numbers 16 digits long?

No. Some networks use other lengths, including 15-digit and variable-length formats.

Can prefix recognition replace Luhn?

No. Prefix recognition and checksum validation solve different problems.

Important Disclaimer

This tool checks format only. It validates structure and checksum, but does not confirm that a card exists, is active, has funds, is not blocked, or can be charged. It does not perform payment authorization or issuer verification.

Related Guides

Back to the main tool

Use the main validator when you need a fast structural check. Use support guides when you need deeper context, implementation detail, or troubleshooting help.

Open Card
More from this hub

IBAN & Card Validator

Free, private, instant bank tools.

What we store

Language preference is saved in a cookie (NEXT_LOCALE). Light/dark theme is saved in localStorage (theme). Nothing else — no data is sent anywhere.

This site uses Google Ads to stay free.

© 2026 IBAN & Card Validator. All rights reserved.