What is a BIN on a credit card?

A BIN, or Bank Identification Number, is the leading digits of a card number that identify the issuing bank and the card product. It was traditionally the first six digits, expanded to eight following the ISO changes introduced in 2022, and some providers are now preparing for 10-digit structures. It is the first signal in a transaction, and it tells the payment stack the card's type, issuer, geography and network before any other decision is made.

What is the difference between a 6-digit and an 8-digit BIN?

Length, and with it granularity. As card programs, issuers and product variations multiplied, the combinations available under the 6-digit structure became insufficient to distinguish between card types and issuer configurations. The 8-digit format restores that precision. In practice merchants often still store only the first six digits for operational reasons, but payment providers need to interpret the full 8 to 10 digits to identify a card correctly — so the risk sits with providers still working on 6-digit assumptions.

How does BIN routing affect approval rates?

The BIN determines the path a payment takes, and that path determines whether it is approved. Smart BIN-based routing, particularly in multi-acquirer setups, sends a transaction to the acquirer or network most likely to approve it, based on issuer proximity, card type compatibility and regulatory preferences. Without accurate BIN logic, transactions go down less optimal paths, producing higher declines, unnecessary authentication step-ups and increased processing costs.

Why are my commercial or virtual cards being declined?

One common cause is misclassification. B2B, commercial and virtual cards are fairly often read as personal consumer cards, which triggers incorrect interchange fees, misrouting and a higher risk of declines, because issuer approval logic and pricing structures differ between these products. Business cards also need dedicated acceptance, routing, fraud and cost logic rather than the rules applied to consumer traffic.

How often should BIN tables be updated?

Ideally monthly, through a dynamic, automated process. BIN tables can become obsolete within months because of issuer mergers, new product launches and reassigned ICA ranges. If a PSP or acquirer hasn't refreshed BIN data since 2022, that is worth challenging directly — stale tables mean stale decisioning logic, and the performance degradation is gradual enough to go unnoticed.

What happens if a co-badged card is routed to the wrong network?

It usually costs more and converts less. Many cards in Europe carry two networks, such as Cartes Bancaires/Visa or Girocard/Mastercard. When the customer does not select a preferred network at checkout, the merchant or PSP decides. Failing to prioritise the domestic network — where fees are typically lower and approval rates higher — produces unnecessary cost and avoidable declines.

Can network tokenisation hide the real BIN?

Yes, and it is one reason BIN logic needs revisiting. Network tokenisation replaces the card number with a token, which can obscure the true BIN. Separately, issuers on legacy systems or with only partial tokenisation support may not recognise, authenticate or authorise tokenised transactions consistently, which produces unexpected declines on wallet payments like Apple Pay and on recurring subscription renewals even when the account is valid and funded.

Article

Is Your BIN Setup Killing Conversions?

Most merchants optimising payments focus on fraud tools, checkout UX and approval rates by geography. Behind all of them sits a quieter operator: the BIN. This is a look at what BIN logic actually decides, where it goes wrong, and what to ask of the providers who manage it on your behalf.

Paypr.work × Norbr26 August 202614 min readFree to read and cite

6→8

Digits in a BIN since the ISO change, with 10 anticipated

2022

When the expansion from 6- to 8-digit BINs was introduced

Monthly

Refresh cadence a BIN table needs to stay current

The quiet operator behind your approval rate

When it comes to optimising payments, most merchants focus on fraud tools, checkout UX, and approval rates by geography, but there's one quiet operator behind the scenes doing a lot of heavy lifting: the BIN.

BINs, also known as Bank Identification Numbers, are more than a technical detail. They're a crucial part of how payments are processed, routed, and authorised.

But here's the catch: if your BIN setup is outdated, overly simplistic, or blind to issuer behaviour, it could be silently working against you, leading to unnecessary declines, higher fees, and missed opportunities to recover revenue.

From six digits to eight, and soon ten

BINs are the starting point for understanding a card transaction. While a transaction begins with a card being presented, it's the Bank Identification Number — traditionally the first six digits of the card, now expanded to eight — that kicks off the decision-making process behind the scenes.

As card programs, issuers, and product variations have multiplied, the available combinations under the old 6-digit structure have become insufficient. This has driven the industry's gradual transition towards 8- and even 10-digit BINs, offering greater granularity to distinguish between different card types and issuer configurations.

While merchants typically continue to store only the first six digits for operational reasons, payment providers must now be capable of interpreting the full 8–10 digits to correctly identify card characteristics. This level of precision isn't just a technical upgrade — it's a critical foundation for smarter routing, better fraud detection, optimised fee management, and higher conversion rates.

What the BIN reveals

Each BIN carries more than just a card number. It provides key signals about the card type, issuer, geography, and network, which in turn influence how the transaction is routed through acquirers, issuers, fraud engines, authentication steps, and ultimately whether it gets approved or declined. In essence, the BIN determines the path a payment will take, and that path is shaped by what the BIN reveals about the card itself.

The characteristics a BIN conveys include:

Credit vs. debit
Domestic vs. international
Regulated vs. unregulated
Issuing bank and geography
Consumer vs. commercial
Prepaid vs. standard

The vocabulary behind BIN logic

BIN (Bank Identification Number): The leading digits of a card number that identify the issuer and the card product. Traditionally the first six digits, now expanded to eight, with some providers preparing for 10-digit structures. It is the first signal in the transaction and the one every downstream decision is built on.
BIN logic: The set of rules and decisions a merchant makes based on the Bank Identification Number: how the BIN is used for routing, fraud rules, 3DS logic, retry flows and analytics. It is the difference between holding BIN data and actually acting on it.
BIN table and BIN lookup: The reference data merchants and providers use to translate a BIN into card characteristics. Merchants typically use static BIN tables or real-time BIN lookup services to make fast, automated decisions during the transaction flow. Tables can become obsolete within months as issuers merge, launch products, or have ICA ranges reassigned.
Enriched BIN intelligence: BIN data extended with detailed metadata such as card level, issuer, country of issuance, scheme and funding type. Enriched data allows the true nature of a card to be detected in real time, which is what makes dynamic routing, risk and pricing strategies possible.
Co-badged card: A card carrying two networks at once, common in Europe — Cartes Bancaires/Visa or Girocard/Mastercard, for example. When the customer does not explicitly select a preferred network at checkout, it falls to the merchant or PSP to apply a default routing choice.
Network tokenisation: The replacement of a card number with a network-issued token, used for wallets and stored credentials. It can obscure the true BIN behind the token, which is why issuer tokenisation support and BIN recognition have to be considered together rather than separately.

What BIN logic actually decides

Every BIN carries valuable metadata about the card — credit or debit, card brand, issuing bank, country of issuance, commercial vs. consumer, prepaid, regulated, unregulated, co-branded, and more. BIN logic is how a merchant uses that data inside the payment stack. Those decisions can influence:

Routing — choosing which network to process the transaction through, especially for debit.
Fraud rules — flagging high-risk countries, prepaid cards, or commercial products.
Authentication logic — determining when to trigger 3DS or apply an exemption.
Pricing and acceptance strategy — understanding which cards come with higher interchange or lower approval likelihood.

If the BIN logic is out of date, overly simplistic, or misaligned with issuer behaviour, merchants are likely leaking revenue without realising it. The symptoms show up as lower approval rates — a regulated debit card routed over an expensive credit network, a high-risk BIN sent through a flow that triggers declines, a prepaid BIN misidentified and caught by fraud rules. They show up as higher costs, where low-cost routing options go unused and interchange is overpaid because the logic never detects a commercial card. And they show up in the customer experience, as transactions declined when they shouldn't be and unnecessary step-ups in authentication.

Why it drifts

Typically, the BIN setup is a "set and forget" configuration buried deep in PSPs or in-house systems. Many merchants don't actively think about their BIN setup after go-live. It's one of those technical configurations handled during integration with a payment service provider and then left untouched for years.

But the payments landscape has moved on. The complexity of card products and the sophistication of optimisation strategies have dramatically increased, making static or shallow BIN logic a liability. With the expansion to 6- and 8-digit BINs adding granularity but requiring updated data sets, network tokenisation obscuring true BINs behind tokens, debit routing strategies requiring precise identification of eligible cards, and dynamic fraud and retry logic benefiting from issuer-level insights, revisiting a BIN setup is no longer optional. It is a competitive edge for any merchant serious about conversion, cost control, and performance.

Where BIN setups go wrong

A growing number of transactions are affected by outdated or inaccurate BIN setups. These aren't theoretical problems: they show up in real conversion drop-offs, retry loops, and unexplained declines, especially in international or high-growth environments.

Misclassification of card types
It is fairly common to see B2B (commercial) or virtual cards incorrectly classified as personal consumer cards. This misidentification distorts key decision points in the payment flow, because it often triggers incorrect interchange fees, misrouting, and a higher risk of declines — issuer approval logic and pricing structures differ between these card products. Enriched BIN databases help detect the true nature of the card in real time and allow routing, risk and pricing strategies to adapt dynamically.
Geo-mismatches
When there's a mismatch between the cardholder's location and the issuer's country — a card issued in Brazil but presented by a customer currently in Europe, for example — it can raise fraud flags, increase the chance of authentication challenges, or lead to outright rejections. Smart BIN logic helps identify legitimate cross-border scenarios and adapt fraud and routing strategies to reduce unnecessary declines without compromising risk management.
Poor issuer tokenisation support
Some issuers, particularly those on legacy systems or with partial tokenisation support, have limited ability to recognise, authenticate, or authorise tokenised transactions consistently. This can lead to unexpected declines for wallet-based payments like Apple Pay, or for recurring subscription renewals, even when the underlying account is valid and funded.
Lack of adaptation to 8-digit BINs
Following the ISO changes introduced in 2022, BINs expanded from 6 to 8 digits, and some providers are now preparing for 10-digit structures. If systems, PSPs, or routing logic still rely on 6-digit assumptions, the result is incomplete card recognition, misrouted transactions, and missed optimisation. Ensuring partners fully support 8- and 10-digit BIN parsing is critical to accurate issuer identification, proper network routing, and cost management.
Misrouting of co-badged cards
In regions like Europe, many cards are co-badged. If a customer does not explicitly select a preferred network at checkout, it falls to the merchant or PSP to apply smart default routing. Failing to prioritise the domestic network — where fees are typically lower and approval rates higher — leads to unnecessary costs and avoidable declines. Strong BIN intelligence combined with network-aware routing ensures co-badged cards are processed over the most cost-effective and high-performing rails when no customer choice is made.

Set-and-forget versus actively managed

	Set-and-forget BIN setup	Actively managed BIN setup
Update cadence	Configured at integration, then left untouched for years	Dynamic, automated refresh — ideally monthly
BIN length support	6-digit assumptions inherited from the original build	Full 8-digit parsing, with 10-digit structures anticipated
Card-type classification	Commercial and virtual cards read as consumer cards	Enriched data detects card level and funding type in real time
Cross-border handling	Issuer/cardholder geo-mismatch raises fraud flags	Legitimate cross-border scenarios identified and handled
Co-badged routing	Default network applied blindly when the customer doesn't choose	Network-aware routing prioritises the domestic rail
Tokenisation awareness	Wallet and stored-credential declines go unexplained	Issuer tokenisation support factored into routing and retries
Performance monitoring	Generic reporting, aggregated above BIN level	Decline rates, retries and cost tracked by BIN range
B2B traffic	Treated on the same rules as consumer traffic	Dedicated acceptance, routing, fraud and cost logic

Why it matters for merchants

BINs drive decisioning before your fraud rules, before your UX, and before issuer logic kicks in. If this layer is misfiring, everything downstream suffers.

Routing matters
Smart BIN-based routing, especially in multi-acquirer setups, can make or break authorisation rates in key markets. Identifying the card's true characteristics allows transactions to be routed to the acquirer or network most likely to approve them, based on issuer proximity, card type compatibility, and regulatory preferences. Without accurate BIN logic, merchants risk sending transactions down less optimal paths, resulting in higher declines, unnecessary step-ups, or increased processing costs.
Fraud controls depend on it
BIN data is a foundational input into many fraud prevention systems. Inaccurate or incomplete BIN information leads to false positives — unnecessary challenges, friction at checkout, or blocking legitimate customers altogether. Understanding the true nature of the card via enriched BIN signals such as country of issuance, commercial vs. consumer, or prepaid status allows merchants to fine-tune fraud thresholds and reduce both good-customer friction and fraud losses.
Fees and scheme costs
Certain card types, regions, or funding models — commercial cards or cross-border transactions, for instance — carry significantly higher processing costs. A clear and accurate BIN profile helps merchants optimise for margin as well as conversion, by applying cost-efficient routing, pricing surcharges where needed, or avoiding expensive acceptance paths altogether. Ignoring BIN nuances can quietly erode payment profitability even when approval rates appear healthy on the surface.
B2B cards require separate logic
Business cards, particularly virtual or corporate-issued ones, do not follow the same acceptance, pricing, or risk management rules as consumer cards. BIN setups need a dedicated B2B logic that recognises these differences, applying tailored acceptance criteria, specialised routing and fraud rules, and cost strategies adapted to corporate payment behaviours. Without separate treatment for B2B traffic, merchants risk higher decline rates, inflated processing costs, and poor alignment between payment flows and customer expectations.

Where to focus

Merchants don't manage BIN tables themselves. But recognising BIN management as a strategic lever, and holding providers accountable for its quality, is critical to optimising payment performance. BIN changes happen fast: issuer mergers, new product launches, and reassigned ICA ranges can make static tables obsolete within months.

Ensure providers update BIN tables regularly
Including support for both 6- and 8-digit formats, and increasingly, preparation for 10-digit BINs. If a PSP or acquirer hasn't refreshed BIN data since 2022, it's time to challenge them. A dynamic, automated update process, ideally refreshed monthly, is essential to avoid stale decisioning logic and performance degradation.
Monitor BIN performance continuously
Beyond regular updates, merchants should work with partners who track BIN-level performance in real time, monitoring authorisation rates, routing success, and cost variations rather than reviewing them after the fact.
Use enriched BIN intelligence
Partner with providers who can supply detailed metadata — card level, issuer, country, scheme, funding type — to power better routing, risk, and fee strategies.
Track performance by BIN range
Work with your PSP or orchestration platform to track decline rates, retries, and conversion drops by BIN range. Patterns often emerge at the issuer or product level that generic reporting misses entirely.
Test and optimise routing strategies
Where possible, A/B test transactions through different acquirers or routing paths by BIN characteristics, to find the optimal authorisation and cost outcomes rather than assuming them.

In a nutshell

A BIN setup isn't just a table — it's a strategic asset. Merchants who treat it that way are able to optimise both cost and performance, while those who ignore it risk falling behind without knowing why.

By challenging your partners and leveraging BIN intelligence, you can optimise both cost and conversion rates, and gain one of the clearest views into what's really happening inside your payment flow.

If you're not actively tracking BIN-driven performance yet, now is the time.

Frequently asked questions

What is a BIN on a credit card?: A BIN, or Bank Identification Number, is the leading digits of a card number that identify the issuing bank and the card product. It was traditionally the first six digits, expanded to eight following the ISO changes introduced in 2022, and some providers are now preparing for 10-digit structures. It is the first signal in a transaction, and it tells the payment stack the card's type, issuer, geography and network before any other decision is made.
What is the difference between a 6-digit and an 8-digit BIN?: Length, and with it granularity. As card programs, issuers and product variations multiplied, the combinations available under the 6-digit structure became insufficient to distinguish between card types and issuer configurations. The 8-digit format restores that precision. In practice merchants often still store only the first six digits for operational reasons, but payment providers need to interpret the full 8 to 10 digits to identify a card correctly — so the risk sits with providers still working on 6-digit assumptions.
How does BIN routing affect approval rates?: The BIN determines the path a payment takes, and that path determines whether it is approved. Smart BIN-based routing, particularly in multi-acquirer setups, sends a transaction to the acquirer or network most likely to approve it, based on issuer proximity, card type compatibility and regulatory preferences. Without accurate BIN logic, transactions go down less optimal paths, producing higher declines, unnecessary authentication step-ups and increased processing costs.
Why are my commercial or virtual cards being declined?: One common cause is misclassification. B2B, commercial and virtual cards are fairly often read as personal consumer cards, which triggers incorrect interchange fees, misrouting and a higher risk of declines, because issuer approval logic and pricing structures differ between these products. Business cards also need dedicated acceptance, routing, fraud and cost logic rather than the rules applied to consumer traffic.
How often should BIN tables be updated?: Ideally monthly, through a dynamic, automated process. BIN tables can become obsolete within months because of issuer mergers, new product launches and reassigned ICA ranges. If a PSP or acquirer hasn't refreshed BIN data since 2022, that is worth challenging directly — stale tables mean stale decisioning logic, and the performance degradation is gradual enough to go unnoticed.
What happens if a co-badged card is routed to the wrong network?: It usually costs more and converts less. Many cards in Europe carry two networks, such as Cartes Bancaires/Visa or Girocard/Mastercard. When the customer does not select a preferred network at checkout, the merchant or PSP decides. Failing to prioritise the domestic network — where fees are typically lower and approval rates higher — produces unnecessary cost and avoidable declines.
Can network tokenisation hide the real BIN?: Yes, and it is one reason BIN logic needs revisiting. Network tokenisation replaces the card number with a token, which can obscure the true BIN. Separately, issuers on legacy systems or with only partial tokenisation support may not recognise, authenticate or authorise tokenised transactions consistently, which produces unexpected declines on wallet payments like Apple Pay and on recurring subscription renewals even when the account is valid and funded.