Multi-acquirer routing: get more payments approved.
Multi-acquirer routing sends each card authorisation to the acquiring bank most likely to approve it, and retries a soft decline through a second acquirer before the customer sees an error.
A decline is often a routing outcome, not a verdict on the card. Paybyrd picks the acquirer most likely to get each transaction approved — by BIN, by issuer, by market — and re-presents when the first answer is wrong.
- Approval rate
- 92.7%
- cohort average, rolling
- +3.12pp
- routing decision
- <1ms
Not a retry loop.
A decision, made every time.
Before an authorisation leaves us it is scored against the signals below and sent to the acquirer most likely to approve it. The same card, presented two different ways, gets two different answers.
- Issuer country
- BIN range
- Local licence available
- Historic approval rate
- Network token present
- 02Acquirer Across-border
- 01Acquirer Blocal licence · JP
- 03Acquirer Cbackup
Illustrative simulation. Identifiers are generated for this page; the signals, ranking and failover behaviour mirror production.
Three stacked layers.
Not one magic flag.
Approval uplift is not a setting somebody forgot to switch on. It is three independent mechanisms compounding.
- Layer 01
Multi-acquirer routing
Each BIN goes to the acquirer most likely to approve it, on a decision graph fed by your own historical outcomes rather than a static preference list.
- Layer 02
Local acquiring
A Tokyo card hits a Tokyo issuer through a locally licensed acquirer, not a remote one. Domestic transactions are trusted differently, and the difference is measurable.
- Layer 03
Network tokenisation
Visa, Mastercard and Amex tokens survive card reissue and carry higher issuer trust than a raw PAN, lifting success on stored credentials and refunds.
Measured against
the incumbents.
Same merchants, same traffic, same period — parallel-processed against the provider they came from.
Cohort-blended uplift across all comparisons. Figures pending clearance; see the proof registry.
- vs Adyen +1.72%
- vs Elavon +3.16%
- vs Checkout.com +4.86%
- vs Nuvei +4.92%
Approval rate is the least-managed
number in your payment stack.
Merchants negotiate the rate for months and never ask what proportion of their transactions actually get approved. One is a line on a contract. The other decides how much revenue reaches the bank — and it is the one nobody is accountable for.
- 01
A tenth of a point is not a rounding error
At €100M of volume, one percentage point of approval rate is €1M. Merchants who would fight for two basis points on their processing fee routinely accept an approval rate nobody has ever benchmarked. The fee is visible on every invoice; the declines are not on any of them. That asymmetry is why the smaller number gets all the attention.
- 02
Geography is not a detail, it is the mechanism
A card issued in Tokyo presented by an acquirer in Amsterdam looks, to the issuer, like a cross-border transaction from an unfamiliar counterparty — and is scored accordingly. The same card presented by an acquirer holding a local licence looks domestic. Nothing about the cardholder, the basket or the risk changed. The route did, and issuers treat the two differently.
- 03
Your BIN mix is not anyone else's
A static acquirer preference list is a guess made once, by someone who has never seen your traffic. Routing that learns from your own outcomes gets better on the specific issuers, markets and card types you actually process, rather than on an industry average that describes nobody. The longer it runs on your volume, the less it resembles a default.
- 04
The gains are independent, so they compound
Multi-acquirer routing, local acquiring and network tokenisation solve different failures: the wrong counterparty, the wrong geography, and a credential the issuer no longer trusts. Because they are independent, they stack rather than overlap — which is why the blended figure is a cohort result and not a single lever anybody switched on.
You negotiated the rate for months. Nobody asked what your approval rate was.
Routing is not a setting to enable. It is the decision made on every authorisation before it leaves us, and on Paybyrd it is already running on the traffic you send today — with your existing acquirer agreements intact.
Routing, answered plainly.
Do I have to change acquirers to use this?
No. Paybyrd is acquirer-agnostic: keep your existing acquirer agreements, your negotiated rates and your in-flight volume commitments. Routing orchestrates on top of what you already have. If you later decide to consolidate, we can act as your acquirer across 90+ markets, but that stays a separate decision on a separate contract.
How does the router decide where a transaction goes?
On the signals available at authorisation time: issuer country, BIN range, whether a locally licensed acquirer is available in that market, the historic approval rate for that combination, and whether a network token exists. The decision graph is fed by your own outcomes, so it gets more accurate on your traffic specifically rather than on an industry average.
Does routing add latency to checkout?
The routing decision itself is sub-millisecond — it happens before the authorisation leaves us, not as an extra round trip. A retry through a second acquirer adds one authorisation cycle, typically a few hundred milliseconds, which is why same-session recovery is usually invisible to the shopper.
What happens if an acquirer goes down?
Traffic fails over to the next candidate automatically. Because the router already holds a ranked list per BIN, an outage is handled as a routing change rather than an incident — you do not need to make a decision or deploy anything for failover to happen.
Can I override the routing?
Yes. You can pin specific traffic to a specific acquirer — by BIN range, market, card type or merchant account — where a commercial agreement or a regulatory requirement demands it. Overrides sit above the automatic decision, and you can see what the router would have chosen instead.
See what routing is worth on your traffic.
Send a month of authorisation data and we will show you the uplift on your own BIN mix — no integration, no commitment.