Your BIN Data Is Probably Wrong

Every time a customer presents their card at checkout, you make a bunch of quick automated decisions: which network and processor to route through, what fees to expect, whether to apply a surcharge, and how risky the transaction might be. Most of those decisions depend in some part on BIN data, the card information tied to the first digits of a card number. If your BIN data is wrong, every decision you make around what to do with a customer’s card is potentially wrong, too, creating real operational and financial consequences for your business.

Many businesses operate on incorrect BIN data simply because their systems only look at the first six digits of a card number. BINs aren't six digits anymore—they’re eight or more. If you’re still only pulling six, the returned data could be wrong. To clarify this hard truth, we conducted an extensive analysis of a recent BIN Data Batch file. Let’s dig into the results:

Listening to the Data

On April 21, 2026, we updated our BIN Data Batch file with data pulled directly from the card networks (as we do every week). The file contains over 1.1 million BIN ranges, so we filtered to primary network ranges only; this isolated the main card network for each range and excluded secondary back-of-card networks, leaving us with over 700K primary ranges to analyze.

We then reviewed all the ranges living underneath each six-digit prefix to see if they all agreed on card brand, issuing bank, country of issuance, and card type (credit vs. debit). When the ranges under a given six-digit prefix returned more than one distinct combination of those attributes, we flagged that prefix as “ambiguous,” meaning a six-digit BIN lookup would return an answer that's wrong for at least some of the cards in that block.

The results:

• 13% of all 6-digit BIN prefixes are ambiguous - Of the 133,647 distinct 6-digit prefixes in the file, 17,884 contain ranges that disagree on at least one core attribute. 

• 51% of all primary BIN ranges sit under an ambiguous prefix - Of the 712,741 primary ranges in the file, 361,504 live under one of those ambiguous prefixes. Ambiguous BIN prefixes pack in many distinct issuer, country, and card type combinations, and it appears this small share of messy prefixes accounts for the majority of primary BIN ranges.

Why Modern Card Programs Break 6-Digit BINs

The 6-digit BIN standard was established when the card industry looked very different and there were fewer cards in circulation. Industry advancements and increased demand for card products lead payment networks to begin generating BINs with eight digits. This started in 2017 with a revision to the ISO/IEC 7812 standard for assigning BINs, and by April of 2022, Visa and Mastercard stopped issuing six-digit BINs altogether. 

In recent years, we’ve seen explosive growth in global fintech issuers like Klarna, Revolut, and Wise. These issuers operate across dozens of countries and issue cards to cardholders in multiple markets; as such, six digits just aren’t enough to sufficiently identify unique issuers and card types. These issuers in turn take advantage of the eight-digit system to distinguish one card product from another, even though they all roll up into the same six-digit prefix.

Take Klarna for example. Under one prefix alone, Klarna issues cards to cardholders in 78 countries. A six-digit BIN lookup on that prefix returns a single country, meaning that data is wrong for every Klarna cardholder in any of the other 77 countries. 

Klarna isn't a special case. It's a representative example of how the industry has evolved. The cards being presented at your checkout today were issued by programs that didn't exist when the 6-digit standard was designed. The standard hasn't kept up.

The Fix: Eight-Digit Granularity

You need BIN data at eight or nine-digit granularity, where the ranges are specific enough to uniquely resolve the attributes that 6-digit prefixes can't. The 15 most ambiguous six-digit prefixes in the April 2026 file each contain between 490 and 549 distinct brand, bank, country, and card type combinations, across 50 to 73 countries and 450 to 520 issuing banks. At 8 or 9 digits, those combinations resolve to individual ranges with consistent attributes.

Sourcing eight and nine-digit BIN data can be a real challenge. You need to get it directly from the card networks and keep it current via ongoing relationships and regular update cycles. Networks update BIN assignments continuously as new card programs launch, existing programs expand into new markets, and legacy six-digit super-BINs break down into more granular sub-ranges. The problem is getting worse over time as more eight-digit sub-ranges get assigned inside legacy six-digit blocks.

Your Fix: Pagos

Pagos receives updated BIN data every week, directly from Visa, Mastercard, Amex, Discover, and local debit networks around the world. We maintain every BIN range at eight and nine-digit granularity, and can return this data to you via the Pagos BIN Data API, our BIN Data Batch file, and even via our MCP server in the agent of your choice. 

Learn more about Pagos BIN Lookup Intelligence and sign up to start operating with better data today.