TL;DR
The Declines You Are Treating As Normal Are Not Normal
Every international merchant has a decline rate they have quietly accepted as the cost of selling across borders. That acceptance is the problem. Domestic card transactions are approved 95 to 99 percent of the time. Cross-border transactions commonly fail 15 to 25 percent of the time [1]. That gap is not fraud, and it is not your customers' fault. It is a structural artifact of how the card networks score risk, and a large part of it is recoverable.
The mechanic is worth stating plainly because it points directly at the fix. When a card issued in one country is charged by a merchant whose acquirer sits in another country, the issuing bank sees a cross-border transaction. Cross-border transactions carry a higher statistical association with fraud, so the issuer applies stricter scoring and declines more aggressively, regardless of whether the specific transaction is fraudulent [1]. A perfectly good customer with a perfectly good card gets declined because the geography of the transaction looked risky to a model. The shopper rarely retries. The sale is gone.
For a business scaling internationally, this is revenue leakage disguised as a technical inevitability. The first step to fixing it is refusing to treat the decline rate as fixed.
Why Local Acquiring Changes The Decision
Local acquiring removes the trigger. Instead of routing a customer's transaction through an acquirer in your home market, the transaction is processed through an acquiring entity in the customer's own region. To the issuer, the transaction now looks domestic, and domestic transactions clear the same fraud models that were declining the foreign version. Same card, same customer, same purchase, different routing, materially higher approval.
The size of the effect is well documented. Research on European flows shows local acquiring can raise approval rates by up to 21 percent compared with cross-border acquiring [1][2]. Beyond the approval lift, local acquiring often improves the economics in other ways: domestic interchange can be lower than cross-border interchange, settlement to the merchant can be faster, and the customer is more likely to see their preferred local payment experience. The approval-rate gain is the headline, but it travels with a cost and experience benefit.
Putting A Number On The Recovered Revenue
The reason local acquiring deserves a place in the boardroom and not just the payments team is that the math is unusually clean. Authorization uplift is recovered revenue, not saved cost, and recovered revenue flows straight to the top line.
The standard worked example: on 200 million dollars of annual cross-border volume, a 2 to 4 percent improvement in authorization recovers 4 to 8 million dollars per year [3]. Scale that to your own volume and the figure is rarely trivial. Critically, this is revenue from customers who already wanted to buy and already had a valid card. There is no acquisition cost, no discount, no campaign. The sale was simply being declined by a risk model that local acquiring defuses. Few growth levers offer that profile.
To estimate your own opportunity, take your cross-border volume, identify the markets where your approval rate sits below your domestic baseline, and model the revenue at even a conservative uplift. The corridors where your declines are worst are usually the ones where local acquiring will move the needle most, which is also where you should pilot it first.
How To Roll It Out Without Boiling The Ocean
Local acquiring does not have to be all-or-nothing. The pragmatic path is to prioritize by pain.
Start by ranking your markets by two factors: cross-border volume and the gap between local and domestic approval rates. A market with high volume and a wide approval gap is your first candidate. Move acquiring for that market to a local entity, hold the rest constant, and measure the approval delta over a defined window against the prior baseline. The clean before-and-after is what proves the case internally and funds the next market. Then extend market by market, always measuring, so each expansion is justified by evidence rather than a vendor promise.
Two cautions keep the rollout honest. First, insist on corridor-level approval data from any provider, not a global blended rate, because a blended number can hide exactly the markets where you are bleeding. Second, treat local acquiring as one part of a broader optimization that includes retry logic, network tokenization, and clean transaction data, since the issuer's decision also depends on the quality of the data it receives. Local acquiring is the largest single lever, but it works best inside a complete approach to local acquiring rather than as an isolated switch.
The Connection To Payout And Settlement
Acceptance optimization and payout are two sides of the same cross-border problem, and the teams that solve one usually need to solve the other. A business lifting its approval rates in Southeast Asia is frequently the same business paying suppliers or sellers in those markets, where settlement speed and cost are the mirror-image challenge. Consolidating acceptance and disbursement with a provider that does both means the approval data and the payout data sit on one ledger, and the corridor economics are visible end to end. For teams whose volume is concentrated in the region, the patterns in Southeast Asia corridors show how the acceptance and payout sides connect in practice. Where beneficiaries prefer digital dollars, payout in stablecoins through Tazapay Canada Corp. closes the loop on the disbursement leg.
Sources
[1] Checkout.com. "Cross-border vs local acquiring: How to optimize global payments." 2025. https://www.checkout.com/blog/cross-border-vs-local-acquiring
[2] Nuvei. "The 2026 Guide to Global Payment Acceptance and Local Acquiring." 2026. https://www.nuvei.com/posts/the-2026-guide-to-global-payment-acceptance-local-acquiring-approval-rates-cross-border-optimization
[3] Stripe. "Global acquiring 101: A guide to cross-border payments." 2025. https://stripe.com/resources/more/global-acquiring-101
