A credit card BIN number is the first set of digits on a payment card, usually the first 6 or 8. BIN stands for Bank Identification Number. The international standard calls it an IIN, or Issuer Identification Number. Same thing, two names.
The BIN tells you which institution issued the card and which card program it belongs to. It doesn’t tell you who’s holding the card. For merchants, that’s both the value and the limit. BIN data helps with routing, reporting, and risk checks, but it can’t prove a buyer is real or fake.
What Is a BIN or IIN?
A BIN is the issuer prefix at the start of a card number. Card networks and payment teams say “BIN.” ISO, the body that writes the numbering standard, says “IIN.” That standard is ISO/IEC 7812-1, which defines the numbering system for card issuers and the format of both the IIN and the primary account number (PAN).
Think of it like an area code. It points to a bank and a slice of its card portfolio, not to one person. Thousands of cards, sometimes millions, can share the same BIN.
Mastercard describes BINs as the first 6 to 11 digits of a card number, identifying the issuer along with a range of other attributes. That flexible length is the part people miss, and it shapes everything below.
A few terms worth keeping straight:
- PAN: the full card number.
- BIN or IIN: the issuer prefix at the front of the PAN.
- Account range: a block of card numbers tied to a BIN that can carry its own attributes, like product type or country.
Where Is the BIN on a Card Number?
The BIN always sits at the very start of the card number. Read left to right. The first digit hints at the network. Visa cards start with 4. Mastercard uses 51 to 55 plus its 2-series range from 222100 to 272099.
How many digits count as the BIN depends on the card. Older cards often run on a 6-digit BIN. Newer issuance runs on 8. So on a 16-digit card starting 4123 4567, the BIN could be 412345 or 41234567. You can’t tell by looking. You need current BIN or account-range data that says how long that specific BIN is.
That’s why “the BIN is the first six digits” is outdated advice. It’s still true for plenty of cards. It’s just not a rule anymore.
After the BIN comes the individual account number, and the last digit is a check digit calculated with the Luhn formula from the same ISO standard. The Luhn check catches typos. It doesn’t confirm the card exists or has money on it.
6-Digit vs 8-Digit BINs
ISO’s January 2017 revision of ISO/IEC 7812-1 changed the IIN length from 6 digits to 8, because issuers were running out of 6-digit prefixes. ISO confirmed that edition in 2022, so it’s still current.
Visa gave acquirers and processors until April 2022 to support 8-digit issuing BINs. Since then, Visa only assigns 8-digit BINs but still supports the 6-digit ones in circulation, and issuers set their own timeline for moving old ones. Mastercard’s BIN Lookup API returns a BIN length field for every account range, so your system can tell which format a card uses instead of guessing.
So in 2026 you’re dealing with a mixed setup:
- Legacy cards still running on 6-digit BINs
- New cards issued on 8-digit BINs
- Some issuers that migrated old portfolios and some that didn’t
Why should you care? Any rule built on the first six digits might now be too broad. Visa warned merchants that logic left on 6-digit BINs could cause negative cardholder impacts, like missed benefits or higher costs. A block list or fraud score keyed to six digits can catch cards from a completely different program that happens to share them.
There’s a compliance angle too. Under PCI DSS Requirement 3.4.1, screens and reports can show no more than the BIN and the last four digits of a PAN unless someone has a documented business need to see more. If your systems mask card numbers, check that they handle 8-digit BINs the way your assessor expects.
What Information Can BIN Data Provide?
BIN data is a set of attributes tied to an issuer prefix or account range. What you get depends on the source, but the useful fields usually look like this:
Data point | What it tells you | How merchants use it |
Card brand | Visa, Mastercard, and so on | Acceptance and routing rules |
Issuing institution | The bank or fintech behind the card | Decline analysis, support |
Issuer country | Where the card was issued | Cross-border pricing, risk context |
Funding source | Credit, debit, or prepaid | Fee planning, prepaid policies |
Product type | Consumer, commercial, premium tier | Interchange analysis, B2B flows |
Account range | The low and high card numbers in the range | Precise matching on 8-digit BINs |
Visa’s BIN Attribute Sharing Service (VBASS) is one official source. It comes in two tiers. Basic has no program fees or registration and covers the issuer BIN, account range, BIN length, and a few flags like domestic-only and online gambling blocks. Enhanced adds funding source, product ID and name, issuer country code, funding source subtype, and issuer name. Both tiers include a BIN length field.
Mastercard offers its BIN and account-range data through a BIN Lookup API, plus a lighter file called the Simplified BIN Account Range Table (SBART). The API returns the low and high ends of each account range, the linked BIN, and the BIN length.
That BIN length field is underrated. It tells your system how many digits to read before it decides what card it’s looking at, which is exactly the problem the 6-to-8 shift created.
Want a quick one-off check? Run a prefix through Chargeblast’s free BIN lookup tool. For production routing and risk rules, you’ll want a source that refreshes often.
Why BIN Data Matters to Merchants
BIN data shows up in more of your payment stack than you’d think. BIN data matters in four places.
Routing. Some setups route by BIN, sending debit to a cheaper network or cross-border cards to a local acquirer. Your payment API or orchestration layer reads the BIN before it picks a path. If the BIN data is stale, the route is wrong.
Payment analytics. Grouping declines by BIN shows patterns by issuer. If one bank’s cards decline far more often than the rest, that’s a specific conversation to have with your acquirer.
Account-range accuracy. With 8-digit BINs, two card programs can share the first six digits. Matching on the full BIN or account range keeps a premium credit program and a prepaid one from blending in your reports.
Risk context. BIN country versus shipping country versus IP location. A prepaid flag on a high-ticket order. A burst of attempts on one BIN, which is a classic card testing pattern. These are inputs your fraud rules weigh alongside AVS, CVV, 3D Secure, and velocity checks, not verdicts.
What BIN Data Cannot Tell You
It doesn’t identify the buyer. BIN data describes the card program, not the person. Two people with cards from the same BIN look identical at the BIN level.
It doesn’t prove fraud. A foreign BIN on a domestic order could be a traveler, an expat, or a student using a card from home. A prepaid card could be a gift. Block on BIN alone and you’ll turn away real customers along with the bad ones.
It doesn’t prove a card is valid or active. A BIN match plus a passing Luhn check only means the number is shaped correctly. Only an authorization tells you whether the account is open and has funds.
It doesn’t stop friendly fraud. When the real cardholder buys something and later disputes it, every BIN signal looks clean because the card is legit. That’s a dispute problem, not a card-data problem. Pre-dispute alerts through Ethoca and Verifi, like the ones in Chargeblast’s Deflection product, are built for that gap.
Treat BIN data as context. Pair it with order history, device data, and authentication results before you decide anything. Our payment fraud detection tips go deeper on stacking those signals.
What Does “BIN Not Found” Mean?
A “BIN not found” result means the lookup source has no record for those digits. It doesn’t mean the card is fake. These are the usual reasons.
Stale data. New BINs get assigned constantly. If your BIN table hasn’t refreshed in a while, new card programs show up as unknown.
Incomplete 8-digit support. If your system sends six digits to a source organized around 8-digit BINs and account ranges, the match can fail or return the wrong issuer. The reverse happens too, when you send eight digits to a source that only stores six.
Provider or database mismatch. BIN providers build their data differently. One might have the range and another might not. Mastercard warns that unauthorized BIN data may be incomplete or outdated, so it’s worth asking where your provider’s data actually comes from.
Tokens instead of card numbers. Wallet payments often carry a network token, not the underlying PAN. Visa’s VBASS documentation treats these as two different things: account-range files and token-range files are requested separately, with a separate call for each. A lookup built only for PANs may return nothing for a token.
Private-label or closed-loop cards. Some store cards and gift cards may not appear in network BIN tables.
So what should you do? Treat “not found” as unknown, not declined. Let the authorization make the call, log the BIN, and ask your provider whether it supports 8-digit lookups and how often it updates.
BIN Lookup vs BIN Generator
These two get mixed up a lot, and they do opposite things.
A BIN lookup reads a real prefix and returns issuer details. Merchants use it to understand the cards hitting their checkout.
A BIN generator creates card numbers from a BIN that pass the Luhn check. Developers use test generators for sandbox QA. Fraudsters use the same idea for card testing, cycling through generated numbers until one goes through.
If you want the tool side of this, including how generated numbers show up in your traffic, read our guide to BIN generator and checker tools for fraud prevention.
Frequently Asked Questions
Is a BIN number the same as an IIN?
Yes. Card networks and merchants say BIN. The ISO/IEC 7812-1 standard says IIN. Both mean the issuer prefix at the start of a card number.
Is a BIN 6 or 8 digits?
Both. New Visa BINs have been 8 digits since April 2022, but legacy 6-digit BINs still circulate. Your systems should read the BIN length from current data instead of assuming one.
Can a BIN number identify the cardholder?
No. A BIN identifies the issuing institution and the card program, not the individual. Every card in that BIN or account range shares the same BIN-level attributes. To learn anything about the actual buyer, you need order data, authentication results, and the authorization response, not BIN data.
Is it safe to store BINs?
A BIN alone doesn’t expose a cardholder, but the full PAN does. PCI SSC FAQ 1492 restates Requirement 3.4.1: displays can show no more than the BIN and last four digits without a documented business need. It says acceptable truncation formats depend on each payment brand, so check with the brands and your QSA.
Why does a BIN lookup show the wrong bank or country?
Usually the data is old, or your system is matching on six digits when the card uses an 8-digit BIN. Check the source’s refresh date and 8-digit support before changing any rules.
Should I block cards by BIN?
Rarely, and never on BIN alone. A targeted block can help during an active card testing attack on one BIN. Broad country or prepaid blocks can cost you real customers, so treat BIN data as one input in your fraud scoring.
Sources
- ISO, ISO/IEC 7812-1:2017 Identification cards, Identification of issuers, Part 1: Numbering system, retrieved 2026-10-19, https://www.iso.org/standard/70484.html
- Visa, Preparing for the Eight-Digit BIN: Numerics FAQ, retrieved 2026-10-19, https://usa.visa.com/dam/VCOM/global/partner-with-us/documents/visa.com-numerics-faq.pdf
- Visa, Numerics Initiative: Simplified Requirements for Eight-Digit Issuing BIN Adoption, retrieved 2026-10-19, https://usa.visa.com/content/dam/VCOM/global/support-legal/documents/numerics-initiative-simplified-requirements-for-eight-digit-issuing-bin-adoption.pdf
- Visa, What Merchants Need to Know: Preparing for Eight-Digit BINs, retrieved 2026-10-22, https://usa.visa.com/content/dam/VCOM/global/partner-with-us/documents/merchant-action-sheet.pdf
- Visa Developer, Visa BIN Attribute Sharing Service: Getting Started, retrieved 2026-10-21, https://developer.visa.com/capabilities/visa-bin-attribute-sharing-service/docs-getting-started
- Mastercard, Simplified BIN Account Range Table (Mastercard BIN Data), retrieved 2026-10-19, https://www.mastercard.com/global/en/business/support/simplified-bin-account-range-table.html
- Mastercard Developers, BIN Lookup: API Data Elements, retrieved 2026-10-19, https://developer.mastercard.com/bin-lookup/documentation/data-elements/
- Mastercard, Frequently Asked Questions (2-series BIN range), retrieved 2026-10-19, https://www.mastercard.co.za/en-za/frequently-asked-questions.html
- PCI Security Standards Council, FAQ 1492: PAN masking and truncation, retrieved 2026-10-19, https://www.pcisecuritystandards.org/faqs/1492/



