Your decline rate shifted. You pulled the error logs, scanned the response codes, and found the usual spread of soft declines and “do not honor” returns. Nothing in those logs explains why a specific slice of your transaction mix is failing at a higher rate than everything else. What they also won’t tell you: those failures are likely downstream of a routing decision your PSP made on your behalf — one that happens at the BIN level, before the transaction ever reaches the issuer. Card BIN routing is the mechanism behind most unexplained authorization gaps, and it’s almost never surfaced in a PSP dashboard.

What a BIN Is and Why It Controls More Than You Think

A Bank Identification Number (BIN) is the first six to eight digits of any card number. That sequence encodes more than most teams realize: the issuing bank, the card network, the card product type, the country of issuance, and in many cases the account type tied to the card. Issuers read this data before evaluating anything else in an authorization request.

What issuers see in a BIN range

When a payment is submitted, the issuing bank reads the BIN to establish the baseline context for authorization. Is this a domestic or cross-border transaction? Is the card a consumer product or a corporate card? Is it prepaid, debit, or credit? Each of those signals feeds into the issuer’s risk and fraud logic before any transaction-specific variables come into play. A cross-border transaction from a domestic card triggers different issuer scrutiny than a domestic transaction from a high-limit corporate card — even if the transaction amounts are identical.

What processors do with the same data

Your PSP looks at that same BIN data and uses it to make a routing decision. Most processors maintain internal routing tables that map BIN ranges to specific acquiring paths. Those tables exist, they influence your authorization rates, and they’re rarely shown to you as the merchant. The routing decision is treated as infrastructure, not configuration.

The Four BIN Signals That Drive Approval Rates

Card BIN routing decisions hinge on four variables that consistently affect whether a transaction approves. Understanding them is the starting point for a routing framework that actually does what you intend.

Country of issuance

A German card routed through a non-European acquirer looks like a cross-border transaction to the issuing bank, even if your customer is sitting in Berlin. That classification alone can cut approval probability by five to twenty percentage points depending on the issuer and card product. Route the same card through a European acquirer and it becomes a domestic transaction in the issuer’s eyes. Country of issuance is the single most impactful variable in cross-border BIN routing, and it’s one that most single-PSP setups can’t act on because they lack the acquiring diversity to offer an alternative path.

Corporate vs. consumer cards

Corporate cards carry different fraud profiles than consumer cards. They’re issued against business accounts, often carry higher limits, and behave differently inside issuer risk models. Some processors have weaker relationships with the banking networks that back corporate card products, which produces structurally higher decline rates for those BIN ranges regardless of the underlying transaction quality. A routing framework that treats corporate cards as a distinct category can direct those transactions to processors with demonstrated approval rates for that card class, rather than letting them absorb the default.

Card scheme and network

Visa, Mastercard, Amex, and UnionPay each have distinct acquiring networks and issuer relationships. A processor with strong Visa performance in North America may be significantly weaker on Mastercard in Southeast Asia. Understanding how payment routing strategies differ by scheme and geography is the foundation for building payment routing rules that hold up across your full card mix. Routing by scheme means you’re matching the card network’s specific characteristics to the processor best positioned to handle them.

Value thresholds and issuer velocity rules

High-value transactions trigger additional issuer scrutiny. Some card products have daily authorization limits or velocity restrictions that only activate above certain transaction amounts. If your PSP lacks strong relationships with the issuers that back high-limit card products, you absorb those declines without any signal in your logs that a routing mismatch is the cause. BIN-level routing that accounts for transaction value sends high-value transactions to processors with the issuer relationships to support them.

What Your PSP Is Actually Doing on Your Behalf

The gap between what a PSP tells you and what it’s actually doing with your transactions is widest at the routing level. PSP dashboards are built to show you outcomes — approved, declined, error. The routing decisions that produced those outcomes are treated as operational infrastructure, not something you’re meant to inspect or configure.

Default routing decisions that go undocumented

PSPs maintain internal routing tables that map BIN ranges to acquiring paths. Those tables are optimized for the PSP’s own cost structure and operational priorities, not necessarily for your authorization rates. When a PSP has stronger acquiring relationships in some markets than others, BIN ranges from underserved markets route through whatever channel is available — not necessarily the one with the best approval rate for your card mix. That gap shows up in your decline data without a clear explanation: a cluster of failures that reads like noise but is actually a routing mismatch hiding behind a generic response code.

When PSP defaults work against you

Look at your decline rate segmented by card country of origin and card type. If your overall rate looks stable but a specific BIN segment is failing consistently, that’s a routing signal, not a fraud signal. The cards aren’t higher risk. The routing path they’re taking is poorly matched to the issuer’s behavior for that card class, and your PSP isn’t going to proactively tell you that.

Building a BIN-Aware Routing Framework

Moving from passive acceptance of PSP routing defaults to deliberate card BIN routing doesn’t require rebuilding your payment stack. It requires the right segmentation logic and the processor diversity to act on it.

Define the routing dimensions that matter for your mix

Start with country of issuance, card type (consumer, corporate, prepaid), card scheme, and a transaction value band. These four dimensions define a routing matrix that covers the majority of BIN-level decisions affecting your authorization rates. You don’t need exhaustive BIN database access to start — you need enough segmentation to identify where your current routing is mismatched against issuer behavior.

Map BIN segments to processor performance

For each BIN segment, which processor in your network shows the highest historical approval rate? That data lives in your transaction logs if you’re running multi-processor routing. If you’re single-PSP today, the mapping starts the moment you add a second provider. A multi-processor payment strategy gives you the comparison set to run this analysis; without it, you don’t have the reference data to know where the gaps are.

Update rules as performance shifts

BIN routing rules configured at implementation degrade over time. Issuer behavior changes. Processor relationships shift. New card products introduce new BIN ranges with different performance profiles. A routing layer that updates based on live performance data consistently outperforms one that maps BIN ranges to processors once and leaves them there. Static payment routing rules are better than no rules, but they’re a starting point, not a strategy.

Where the 2-4% Authorization Rate Uplift Actually Comes From

The 2-4% authorization rate uplift cited in payment orchestration research isn’t abstract. It’s the aggregate result of closing multiple BIN-level gaps across a transaction mix. Country-of-issuance mismatches, corporate card decline patterns, and high-value transaction failures on processors without the right issuer relationships each contribute to the gap between current approval rates and what’s recoverable through deliberate routing. Card BIN routing is the specific mechanism that produces the improvement — not orchestration in general, but the BIN-aware decisions it enables.
The gains aren’t evenly distributed. Cross-border BIN segments and corporate card ranges tend to show the largest recoverable uplift. Identifying which segments are underperforming in your transaction mix gives you a prioritized roadmap for where routing optimization will have the most impact, and grounds the 2-4% figure insomething specific enough to actually act on.

Make the Invisible Routing Decisions Visible

Card BIN routing happens on every transaction you process. The only question is whether it’s happening deliberately or by default. If you’re running single-PSP today, those decisions are being made for you — optimized for your provider’s operational priorities, not your authorization rate.
Orchestra’s intelligent payment routing evaluates every transaction in real time against processor performance history segmented by BIN, issuing country, card type, and transaction value. When a BIN segment starts showing decline rate movement, routing adjusts before the problem compounds in your aggregate metrics. That’s the difference between knowing what happened and controlling what happens next. If you want to understand where your current routing is leaving approval rates on the table, reach out and we’ll walk through what that analysis looks like for your specific transaction mix.