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.
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.
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.
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.
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.
[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
Most finance teams can recite their processing rate to the basis point. Almost none can state their FX markup, and that is not a coincidence. The processing fee is itemized because it is competitive and quotable. The FX markup is buried inside the exchange rate because it is neither. When your gateway converts a customer's payment from their currency into your settlement currency, it applies a rate, and the gap between that rate and the true mid-market rate is pure margin that never appears as a fee on any statement.
The scale is easy to underestimate. A markup of one to three percent on the converted amount routinely exceeds the entire processing fee for a cross-border transaction. On a business moving tens of millions across borders, that is a seven-figure cost line that no one has ever benchmarked, because it does not look like a cost. It looks like the exchange rate.
This is not a problem with one provider. It is a structural transparency gap that regulators are still trying to close. The G20's cross-border payments roadmap lists disclosure of FX rates and conversion charges among its explicit transparency targets, and its own 2025 progress report concedes that improvement has been slow and uneven, with the end-2027 targets unlikely to be met on current trends [1]. Where rules do exist they are inconsistent: the UK mandates fuller FX markup disclosure, while other markets leave it voluntary, which means hidden spreads persist by default [2]. Until disclosure is mandatory everywhere, the work of finding the markup falls to you.
To benchmark a cost you have to know where it lives. In a cross-border card transaction the spread can be applied at more than one point, and providers differ on which one they use.
The first place is at authorization and settlement, when the acquirer or gateway converts the transaction amount into your settlement currency. This is the most common location and the hardest to see, because the converted figure simply appears in your settlement report as a number. The second place is at payout, when you disburse funds in a currency other than the one you hold, and a second conversion happens on the way out. A business that collects in one currency and pays suppliers in several can be charged a markup on the way in and again on the way out, which is why the FX exposure on the payout side deserves its own scrutiny rather than being lumped into a single rate.
The third place is dynamic currency conversion at checkout, where the customer is offered to pay in their home currency and the conversion margin is shared between parties in the chain. This one is visible to the customer but rarely analyzed by the merchant as a cost to the business relationship.
Benchmarking the markup is methodical, not difficult. The reference point is the mid-market rate, the midpoint between the buy and sell rates in the wholesale FX market, which is what services like a central bank reference or a neutral market feed publish. Everything is measured against that.
Start by exporting a sample of cross-border transactions for a single corridor over a defined period, with the original currency amount, the converted amount, and the timestamp. For each transaction, pull the mid-market rate at that timestamp and compute what the converted amount should have been. The difference, expressed as a percentage of the transaction, is your effective FX markup for that corridor. Repeat per corridor, because the markup is rarely uniform: high-volume corridors may be tighter and thin corridors much wider. Weight by volume to get a blended cost, but keep the per-corridor numbers, because that is where the negotiation lives.
Once you have the number, you have leverage. The benchmark conversation with a provider should be specific: here is the effective markup we measured on this corridor, here is the mid-market reference, show us how you price it. The strongest providers treat this as a normal request and quote the mid-market rate alongside a transparent margin. The weakest treat your settlement export as the only source of truth, which is exactly the opacity the G20 roadmap is trying to legislate away.
Three demands are reasonable to put in writing during any review of payment gateway pricing. First, the mid-market reference rate shown next to the rate actually applied, per transaction or at least per corridor. Second, a single transparent FX margin rather than a spread that moves without explanation. Third, the same transparency on the payout leg as on acceptance, so a second hidden conversion is not reintroduced when you disburse. If a provider cannot or will not meet these, the markup is almost certainly a profit center they would rather you not measure.
There is also a structural fix beyond negotiation. Settling part of the flow over stablecoin rails collapses the conversion economics, because the all-in cost of moving regulated digital dollars runs an estimated 0.1 to 0.5 percent against the 2 to 7 percent true cost of traditional cross-border transfers [3], and the World Bank's Q3 2025 data still puts the global average for cross-border transfers at 6.36 percent [4]. For corridors where the markup is widest, a stablecoin payout leg through Tazapay Canada Corp. can remove the spread you have been paying twice.
The point of benchmarking the markup once is to never not know it again. Make the effective FX markup a standing line in your payments reporting, refreshed each quarter, broken out by corridor. The first time you run it, the number will likely surprise the finance team, because a cost that has been invisible for years tends to be larger than anyone guessed. After that, it becomes a managed cost like any other, with a target, an owner, and a trend.
This is the discipline that separates teams who control their cross-border economics from teams who are controlled by them. The processing rate gets all the attention because it is visible. The FX markup deserves more, because it is usually larger and almost always unmeasured. For teams running a full provider review, this benchmark belongs alongside the broader work of evaluating an international payment gateway, where FX transparency is one of the six questions that actually separate providers.
[1] Financial Stability Board. "G20 Roadmap for Cross-border Payments: Consolidated progress report for 2025." October 2025. https://www.fsb.org/2025/10/g20-roadmap-for-cross-border-payments-consolidated-progress-report-for-2025/
[2] Wise. "G20 Roadmap for Enhancing Cross-border Payments, One Year On." 2025. https://wise.com/p/g20-report-2025
[3] EY. "Cost savings and speed drive stablecoin adoption." 2025. https://www.ey.com/en_us/insights/financial-services/cost-savings-and-speed-drive-stablecoin-adoption
[4] World Bank. "Remittance Prices Worldwide, Issue 54." September 2025. https://remittanceprices.worldbank.org/sites/default/files/2026-04/RPW_main_report_and_annex_Q325.pdf
