The short answer
BIN is the familiar payments-industry term; IIN is the standards term, meaning Issuer Identification Number. In everyday use, both often describe the leading digits of a Primary Account Number (PAN).
ISO revised the numbering framework because the supply of issuer identifiers was becoming constrained. Existing six-digit IINs can represent a block of one hundred eight-digit IINs. That means a single six-digit lookup result may hide more specific sub-range assignments.
Where the extra digits come from
The overall card number did not simply gain two digits. The issuer-identification portion uses two more positions inside the PAN, reducing the issuer-controlled account-number space available under each individual IIN.
The PAN still carries the account identifier and a final check digit. The Luhn check can detect common entry errors, but it does not confirm that an account exists, is active or can be authorized.
What can go wrong with a six-digit-only lookup
| Use case | Six-digit risk | Safer approach |
|---|---|---|
| Issuer display | One legacy prefix can cover several eight-digit assignments with different labels. | Prefer an authoritative eight-digit match; label six-digit results as broader or legacy. |
| Product classification | Credit, debit, prepaid or commercial attributes may differ below the six-digit level. | Do not use a broad match as the sole source for customer-facing or risk decisions. |
| Routing | Rules hard-coded around six digits can send a transaction or workflow to the wrong branch. | Confirm routing data with the acquirer, processor or network-authorized source. |
| Fraud analytics | Different programs become aggregated, distorting rates and thresholds. | Version the source, record match length and monitor changes by eight-digit range. |
| Reporting | Historical trends can appear to change when only the classification granularity changed. | Store source date, matched prefix length and the returned attributes. |
Migration checklist for an existing application
How to read BINtools results today
The current public BINtools directory contains 375,518 distinct six-digit records. Its lookup results are useful as informational legacy-prefix metadata, and the site deliberately describes that granularity rather than presenting it as universal eight-digit coverage.
A six-digit match can still help with broad issuer, country, network and product exploration. For production routing, fraud decisions or definitive eight-digit classification, verify the result with an issuer, processor, acquirer or network-authorized source.
Frequently asked questions
Is a BIN six digits or eight digits?
Both formats can appear in current payment systems. Legacy issuer identification commonly uses the first six PAN digits, while the current ISO framework supports eight-digit IINs. Systems should not assume that six digits always identify the narrowest issuer range.
Did the payment card number become longer?
No. The change reallocates digits inside the existing primary account number. The IIN portion can use eight digits, leaving fewer digits for the issuer-defined account range while the PAN remains within its supported total length.
Can two cards with the same first six digits have different metadata?
Yes. A legacy six-digit range can contain multiple eight-digit ranges. Those sub-ranges can differ in product, program or routing attributes, so six-digit data can be less specific than an authoritative eight-digit source.
Should an application store the full card number for BIN lookup?
No. A BIN or IIN lookup should receive only the minimum prefix required for the task. Full PAN storage and handling creates additional security and compliance obligations and is unnecessary for a metadata lookup.