Skip to content
Card BIN Checker
BINIINISO 7812card networkspaymentsprivacy

What Is a BIN (Bank Identification Number)?

The leading digits of any payment card encode its network, issuer, and card type — but never the account or cardholder. Here's what a BIN is, what it reveals, and what it can't.

7 min read

Every payment card number tells a small story before you ever reach the account it belongs to. The first handful of digits — the BIN, or Bank Identification Number — identify the network, the issuer, and the kind of card in your hand. The rest of the number identifies the account, and that part is nobody's business but the issuer's.

This distinction is the whole reason BIN lookups are safe and useful. You can learn a great deal about what kind of card a number is without learning whose card it is. This article explains what a BIN is, where it came from, exactly what it can and cannot reveal, and how it's used legitimately. If you'd rather just try it, our BIN Checker reads those leading digits right in your browser.

BIN vs. IIN: two names for the same thing

You'll see two terms used almost interchangeably: BIN (Bank Identification Number) and IIN (Issuer Identification Number). They refer to the same leading digits. "BIN" is the older, more common term, coined when these prefixes were assigned mostly to banks. "IIN" is the modern, technically correct name used by the ISO/IEC 7812 standard, because today the issuer might be a fintech, a co-brand program, or a network itself — not strictly a bank.

In everyday payments conversation, people say "BIN." In the standards documents, you'll see "IIN." Treat them as synonyms and you'll never be confused.

The short version

A BIN (or IIN) is the identifying prefix of a card number. It maps to a network and an issuer. It does not identify the account, the balance, or the person.

A little history: ISO/IEC 7812

Card numbers aren't random. Their structure is defined by ISO/IEC 7812, the international standard for identification cards. It specifies that a Primary Account Number (PAN) is made up of three parts:

  • Issuer Identification Number (IIN/BIN) — the leading digits that identify the network and issuer.
  • Individual account number — the middle digits that identify the specific account.
  • Check digit — a single trailing digit computed with the Luhn algorithm to catch typos.

The very first digit of the IIN is the Major Industry Identifier (MII), which signals the broad category of issuer. That's why the leading digit is so telling: 4 is Visa's, 3 covers travel-and-entertainment cards like American Express and Diners Club, and so on. The rest of the BIN narrows it down from there.

Our card engine encodes exactly these documented prefix ranges. For example, Visa numbers start with 4; Mastercard uses 51–55 plus the newer 2221–2720 range; American Express uses 34 and 37; and Discover covers 6011, 65, 644–649, and a 622126–622925 carve-out. Reading those digits is all a network lookup does.

The 6-to-8 digit shift

For decades, a BIN was 6 digits. That's the number most developers grew up with, and it's still what many older systems and BIN databases assume. But as card programs multiplied, six digits ran out of room — there simply weren't enough 6-digit prefixes to go around.

So the standard moved to an 8-digit IIN. A 2017 revision of ISO/IEC 7812 formalized the longer format, and the major networks began issuing 8-digit BINs to expand capacity. This is the single most important nuance for anyone building BIN logic today.

Don't hard-code "6 digits"

A 6-digit prefix may resolve to a different, more specific issuer once you look at 8 digits. If your fraud or routing logic slices exactly 6 characters, you can misroute or mis-attribute cards issued under the 8-digit scheme. Always design for both lengths.

Network detection itself doesn't need a fixed BIN length — it just needs enough leading digits to resolve the pattern. Some networks are decided by two digits, others need four or six. Our detector matches the longest, most specific prefix and reports network identity progressively as you type, rather than assuming any single cutoff.

What a BIN reveals

Look up a BIN and you can typically learn several attributes of the card — all of them properties of the card program, not the account:

  • Network — Visa, Mastercard, American Express, Discover, JCB, Diners Club, UnionPay, RuPay, or Maestro. This is derived purely from the leading digits.
  • Card type — credit, debit, or prepaid. (Maestro, for instance, is Mastercard's debit brand.)
  • Category / tier — consumer, business/commercial, or premium tiers like platinum, where the program publishes it.
  • Issuer — the bank or fintech that issued the card program.
  • Country — the issuing country of the program, useful for currency and regional routing decisions.

Our in-browser BIN Checker focuses on the facts it can determine with certainty from the digits alone — the network, the valid lengths, and the grouping pattern. Everything it reports is deterministic and computed locally; nothing about the number leaves your device.

4111 11•• •••• ••••
└──┬─┘
   │
   └─ Leading digits (the BIN): here they resolve to Visa.
      The remaining digits are the account number and a
      trailing Luhn check digit — not derivable from the BIN.

What a BIN can NEVER reveal

This is the part that matters most for privacy, and it's absolute. A BIN describes a category of card, not an individual. From the leading digits you cannot determine — not now, not with any lookup service — any of the following:

  • The account number. The middle digits are unique per card and are not encoded in, or recoverable from, the BIN.
  • The cardholder's name or identity. BIN data has no personal information in it at all.
  • The balance, credit limit, or available funds. A BIN lookup is structural, not financial.
  • Whether the card is active, expired, stolen, or even real. A BIN can look perfectly valid on a number that was never issued to anyone.

BIN lookup ≠ authorization

Confirming a network and passing the Luhn checksum only tells you a number is well-formed. It says nothing about whether the card exists or can be charged. Only the issuer, at authorization time, knows that.

Because a BIN carries no account or personal data, looking one up is inherently privacy-safe — provided the tool you use doesn't transmit or store the full number you paste. That's a deliberate design choice here: our tools run entirely in your browser and never send or save card numbers.

Legitimate uses for BINs

BIN intelligence is a workhorse of modern payments. A few of the everyday, above-board uses:

  • Fraud and risk checks. Flag mismatches — for example, a billing country that disagrees with the card's issuing country — as one signal among many.
  • Payment routing. Route a transaction to the cheapest or most reliable processor based on network and issuer, and pick the right acquirer for the region.
  • Cost optimization. Interchange fees vary by card type and category, so knowing a card is commercial vs. consumer helps forecast and reconcile costs.
  • Better UX. Show the correct network logo, apply the right digit grouping, and set the security-code length as the user types — American Express, for instance, uses a 4-digit code while most networks use 3.
  • Analytics. Understand your customer base by network mix, issuing country, and card type — without ever touching an individual account.

Notice that none of these require the full account number. They all operate on the BIN — the safe, non-personal part of the card. That's what makes BIN-based logic both powerful and privacy-respecting when it's built responsibly.

Try it yourself

The fastest way to build intuition is to enter a few prefixes and watch the network, valid lengths, and grouping resolve as you type. Nothing you enter is stored or transmitted. For definitions of any term above — MII, IIN, PAN, interchange — see the glossary, and if you have broader questions our FAQ covers how the tools handle your data.

Read the leading digits of any card, privately and instantly in your browser.

Open the BIN Checker