ISO/IEC 7812 PAN Architecture and 8-Digit BIN Expansion
Every payment card Primary Account Number (PAN) is structured according to the ISO/IEC 7812-1 numbering standard, typically spanning 13 to 19 digits depending on the card network. The leading digits form the Issuer Identification Number (IIN)—commonly called the Bank Identification Number (BIN)—followed by the individual account identifier and a trailing check digit.
The very first digit is the Major Industry Identifier (MII), which assigns the broad sector: 3 for travel and entertainment (American Express, Diners Club, JCB), 4 for Visa banking and financial cards, 5 for Mastercard banking cards, and 6 for merchandising and banking networks such as Discover and UnionPay. Between 2022 and 2026, Visa and Mastercard completed the industry-wide migration from 6-digit to 8-digit BINs, expanding total assignable issuer prefixes from 1,000,000 to 100,000,000 while keeping standard 16-digit PAN lengths intact.
| Card Network | BIN/IIN Prefix Ranges | PAN Length | 8-Digit BIN Status (2026) | Primary MII |
|---|---|---|---|---|
| Visa | 4 (400000–499999) | 13, 16, 19 digits | Mandatory 8-digit allocation for new ranges | 4 (Banking) |
| Mastercard | 51–55, 2221–2720 | 16 digits | Mandatory 8-digit standard across issuers | 5 / 2 (Banking) |
| American Express | 34, 37 | 15 digits | 6-digit IIN retained; 15-digit PAN structure | 3 (Travel/Ent.) |
| Discover | 6011, 622126–622925, 644–649, 65 | 16–19 digits | 8-digit BIN supported for partner issuers | 6 (Merchandising) |
| UnionPay | 62, 81 | 16–19 digits | 6-to-8-digit IIN routing in cross-border rails | 6 / 8 (Telecom/Fin) |
| JCB | 3528–3589 | 16–19 digits | 6-digit primary IIN with sub-range partitioning | 3 (Travel/Ent.) |
Because fintechs, neobank BIN sponsors, and B2B virtual card programs now share parent ranges, querying only the first 6 digits frequently returns outdated or ambiguous issuer data. Modern payment orchestration engines parse all 8 leading digits before routing an authorization or calculating interchange.
Luhn Algorithm (Mod 10) Formula and Calculation Example
Before a checkout form or payment API transmits a card number to an acquirer, it validates the trailing check digit using the Luhn algorithm (ISO/IEC 7812-1 Annex B, Mod 10). The checksum catches single-digit typos and most adjacent digit transpositions in under a millisecond on the client or server.
To compute the check digit for a 15-digit payload (positions 1 through 15 from left to right), double every digit in an odd position (1, 3, 5, 7, 9, 11, 13, 15). Whenever doubling produces a value greater than 9, subtract 9 (which equals summing its two digits). Sum all 15 resulting values to obtain S, then calculate the check digit as d_check = (10 - (S mod 10)) mod 10.
Consider a concrete Visa 8-digit BIN prefix 45320151 followed by account digits 1283036 (15-digit payload 453201511283036):
- Odd positions (doubled, minus 9 if > 9): pos 1 (4×2=8), pos 3 (3×2=6), pos 5 (0×2=0), pos 7 (5×2=10→1), pos 9 (1×2=2), pos 11 (8×2=16→7), pos 13 (0×2=0), pos 15 (6×2=12→3).
- Even positions (unchanged): pos 2 (5), pos 4 (2), pos 6 (1), pos 8 (1), pos 10 (2), pos 12 (3), pos 14 (3).
- Total sum S: 8 + 5 + 6 + 2 + 0 + 1 + 1 + 1 + 2 + 2 + 7 + 3 + 0 + 3 + 3 =
44. - Check digit:
(10 - (44 mod 10)) mod 10 = (10 - 4) mod 10 = 6, producing the valid 16-digit PAN4532 0151 1283 0366(total sum44 + 6 = 50, divisible by 10).
Card Product Classification: Prepaid, Virtual, and Interchange
Beyond identifying the issuing bank and country, BIN tables encode the funding source (DEBIT, CREDIT, PREPAID, CHARGE) and product tier (Classic, Gold, Platinum, Infinite, World Elite, or Corporate/Commercial). Distinguishing between a consumer debit card and a corporate virtual card directly impacts both fraud exposure and unit economics.
In the European Economic Area (EEA), the EU Interchange Fee Regulation caps consumer debit interchange at 0.20% and consumer credit at 0.30%. However, commercial, corporate, and inter-regional non-EEA BINs are exempt from these caps and routinely cost merchants 1.50% to 2.90% per transaction. Similarly, media buyers and SaaS teams rely on dedicated corporate virtual BINs to isolate ad-spend billing; you can compare issuer reliability in our virtual cards rating for media buying and digital operations.
AVS, 3DS 2.2, and Fraud Risk Scoring via BIN Intelligence
Risk engines combine BIN attributes with Address Verification Service (AVS) responses, IP geolocation, and EMV 3-D Secure (3DS 2.2 / 2.3) telemetry to decide whether a payment qualifies for a frictionless flow or requires a Strong Customer Authentication (SCA) challenge. Under PSD2 Transaction Risk Analysis (TRA) rules, acquirers can exempt transactions up to €500 if their overall fraud rate stays below 0.01%, €250 below 0.06%, and €100 below 0.13%.
| BIN Risk Signal | Typical Fraud / Cost Vector | Risk Weight | Recommended Gateway Action |
|---|---|---|---|
| BIN Country ≠ IP / Billing Country | Stolen card credentials routed via residential proxy or VPN | High (+35 pts) | Force 3DS 2.2 challenge; verify AVS postal match |
| Non-Reloadable Prepaid / Gift BIN | SaaS trial abuse, synthetic identity, high dispute ratio | Medium-High (+25 pts) | Block recurring trials; require 3DS or alternative rail |
| Commercial / Corporate Virtual BIN | Uncapped interchange (1.5%–2.9%); legitimate B2B spend | Low-Medium (+10 pts) | Apply B2B surcharge logic if legal; allow frictionless |
| AVS Full Mismatch + High-Risk BIN | Card-not-present (CNP) testing or automated BIN attack | Critical (+50 pts) | Soft decline before authorization; rate-limit IP/session |
| Closed or Sanctioned Issuer Range | Expired BIN sponsor program or regulatory block | Critical (Auto-Block) | Reject pre-gateway to avoid scheme decline fees |
When an issuer rejects a transaction after BIN routing, interpreting the exact ISO 8583 response code prevents unnecessary retry loops; consult our bank card decline codes and 3DS troubleshooting guide for remediation steps.
NW24 BIN Checker Methodology and Verification Workflow
The NW24 BIN Checker executes a deterministic four-stage lookup pipeline designed for payment engineers, compliance analysts, and e-commerce risk teams without transmitting sensitive full PANs across third-party logs:
- Prefix Sanitization & Length Normalization: Strips whitespace and non-numeric characters, extracting the leading 6 to 8 digits while preserving scheme-specific formatting (15 digits for Amex, 16–19 for Visa/Mastercard).
- Luhn Mod-10 Structural Check: When a full or test PAN is entered, computes the Mod-10 checksum locally to flag typos before any issuer table lookup occurs.
- 8-Digit Issuer Registry Resolution: Matches the longest available prefix (8-digit first, falling back to 6-digit) against updated scheme ranges to return the issuing bank, card brand, funding type, product tier, and ISO 3166-1 alpha-2 country.
- Risk & Interchange Flagging: Surfaces prepaid/virtual indicators, EEA vs. non-EEA interchange classification, and 3DS 2.2 readiness so teams can tune gateway routing rules immediately.
Keep in mind that BIN intelligence is strictly structural and metadata-driven: it cannot verify cardholder balances, CVV2 values, or whether a specific card has been frozen by the issuer.