If your platform processes payments across multiple countries, you have probably noticed that cross-border transactions cost more and fail more often. The reason is straightforward: when a card payment is routed through an acquirer in a different country from the cardholder, networks treat it as a cross-border transaction and apply higher interchange fees, additional scheme levies, and stricter fraud screening. The result is lower authorisation rates and higher costs.
Local acquiring solves this by routing payments through an acquiring bank in the same country as the cardholder. The transaction looks domestic to the card network, which means lower fees, higher approval rates, and faster settlement. For platforms operating in multiple markets, local acquiring is one of the highest-impact optimisations available.
What Is Local Acquiring?
Local acquiring means processing a card payment through an acquirer that is licensed and domiciled in the same country as the cardholder’s issuing bank. When a customer in Germany pays with a German-issued Visa card and the transaction is routed to a German acquirer, the card networks classify it as a domestic transaction.
This matters because card scheme rules treat domestic and cross-border transactions very differently:
Interchange fees: under the EU Interchange Fee Regulation, consumer card interchange is capped at 0.2% for debit and 0.3% for credit whenever the issuer and the acquirer are both in the EEA, including cross-border within the EEA. Cards issued outside the EEA and used at EEA merchants fall outside those caps and carry interregional rates, which are materially higher.
Scheme fees: Visa and Mastercard apply additional cross-border assessment fees on transactions where the acquirer and issuer are in different countries. The rates vary by scheme, region and card type, so work from your own scheme fee schedule rather than a published range.
Authorisation rates: Issuers are more likely to approve transactions that appear domestic. Cross-border transactions trigger additional fraud screening, soft declines and 3DS challenges. The size of that gap varies by market and card mix.
Settlement speed: domestic transactions typically settle faster than cross-border ones, and cross-border settlement may involve currency conversion. Exact timings vary by acquirer and market, so confirm them in your own agreement.
In short, local acquiring makes international payments behave like domestic ones. The economics improve, the conversion rates improve, and the customer experience improves.
Local Acquiring vs Cross-Border Processing
The distinction between local and cross-border acquiring comes down to where the acquirer sits relative to the cardholder. Here is how the two models compare across the metrics that matter most to platforms:
Cost comparison
Local acquiring: domestic interchange plus acquirer margin, with no cross-border scheme fees.
Cross-border acquiring: interchange at the applicable cross-border or interregional rate, plus cross-border assessment fees, plus acquirer margin, plus any currency conversion markup. The effective rate on your own statements is the number that matters, and your acquirer can break it down for you.
Authorisation rates
Local acquiring: Issuers see an acquirer BIN and merchant country in their own market, which generally means less friction and fewer additional fraud checks.
Cross-border acquiring: Foreign acquirer BINs can trigger additional issuer fraud rules, soft declines and higher 3DS challenge rates. How much that costs you varies by market and card mix, so measure it on your own traffic rather than relying on a published range.
Settlement
Local acquiring: settlement in local currency, typically faster, with no forced FX conversion at the scheme level.
Cross-border acquiring: settlement may involve scheme-level currency conversion, and timing can extend in some corridors. Confirm both the timing and the conversion treatment with your acquirer.
The size of the saving depends on your market mix, your card mix and what you currently pay, so the only reliable number is your own. Take your cross-border volume for a single market, apply the domestic interchange and scheme fees that would apply if the acquirer were local, and compare that against your current effective rate for the same traffic. Your acquirer can give you the fee breakdown you need to work it out.
How Local Acquiring Works
The technical flow for a locally acquired transaction involves several parties, but the key point is where the acquirer sits in the chain:
1. Payment initiation. A customer in France enters their card details on your platform’s checkout. The payment gateway captures the card data and passes it to the payment processor.
2. Intelligent routing. The payment layer identifies the card’s issuing country from the BIN (Bank Identification Number — the first 6–8 digits). Based on this, it routes the transaction to a local acquirer in France rather than sending it cross-border.
3. Local processing. The French acquirer submits the authorisation request to the card scheme (Visa, Mastercard). Because both the acquirer and the issuer are in France, the scheme classifies it as a domestic transaction.
4. Domestic interchange applied. The issuer approves the transaction and domestic interchange rates apply. No cross-border assessment fees are charged. Settlement happens in euros on domestic clearing rails.
5. Funds settlement. The acquirer settles funds to the merchant or platform, on the cycle set out in your acquiring agreement. If the platform needs settlement in a different currency, the FX conversion happens at the platform layer with transparent rates rather than at the scheme level.
The critical enabler here is BIN-based routing logic that sits between the checkout and the acquiring layer. Without it, transactions default to whichever single acquirer the platform has a contract with, regardless of where the cardholder is located.
When You Need Local Acquiring
Not every business needs local acquiring. If you only process payments in one country and your acquirer is in that country, your transactions are already domestic. Local acquiring becomes important when:
You operate across multiple markets. If your platform has merchants or customers in the UK, EU, US, and APAC, a single acquirer cannot provide domestic processing in all of those regions.
Cross-border decline rates are hurting revenue. If your authorisation rates on international traffic are materially below your domestic rates, that gap is worth investigating, and local acquiring is one of the levers. Measure it on your own traffic, segmented by issuing country and card type, before assuming the size of the prize.
Processing costs are eating your margin. Cross-border fees compound quickly. Work out your effective rate on international volume and compare it against what you pay domestically. If the gap is material and the volume is concentrated in one market, local acquiring is worth pricing.
You are expanding into new geographies. Entering a new market without a local acquirer means every transaction in that market will be cross-border. Setting up local acquiring before launch, or as part of launch, gives you the best possible unit economics from day one.
Your merchants expect competitive payment costs. If you are a platform that facilitates payments for sub-merchants, your pricing needs to be competitive. Local acquiring lets you offer lower transaction fees because your underlying costs are lower.
The Multi-PSP Problem
Here is where local acquiring gets complicated for platforms. Achieving true local acquiring across multiple markets usually means working with multiple payment service providers (PSPs) or acquirers. Adyen might give you strong local acquiring in the Netherlands and wider EEA. Stripe might cover the US and UK well. But neither alone covers every market your platform operates in.
This creates what we call the multi-PSP problem:
Separate contracts and integrations. Each acquirer or PSP requires its own commercial agreement, technical integration, and onboarding process. For a platform operating in 10+ markets, this means managing 3–5 separate PSP relationships.
Fragmented reporting. Transaction data, settlement reports, and dispute management are split across multiple dashboards. Reconciliation becomes a significant operational burden.
Routing complexity. Your platform needs to build and maintain the logic that decides which PSP handles which transaction based on the cardholder’s country, card type, currency, and other factors. This is non-trivial engineering work.
Compliance overhead. PCI DSS compliance, SCA requirements, and local regulatory obligations multiply with each PSP relationship. Each market may have its own rules around strong customer authentication, data residency, and payment licensing.
Ongoing maintenance. PSP APIs change, schemes update their rules, and local regulations evolve. Maintaining multiple integrations is a permanent engineering cost, not a one-time effort.
This is why many platforms end up stuck with a single PSP and accept the cross-border cost penalty. The operational complexity of a multi-PSP approach feels too high, even when the economics clearly justify it. But there is a better way. If you are weighing that trade-off now, we cover it in detail in single global PSP vs multiple local acquirers.
How Shuttle Works With Local Acquirers
Shuttle is a PSP-neutral payment layer that sits between your platform and the payment providers you use. It is not an acquirer, it does not issue merchant accounts, and it holds no acquiring relationships of its own. You keep your own provider agreements and your own rates. What Shuttle changes is the integration work: instead of building and maintaining a separate integration for every provider you add, your platform connects once and the connected providers sit behind that connection.
Here is how it works:
Single integration, multiple providers. Your platform connects to Shuttle's API once. Providers Shuttle already connects to sit behind it, so adding one becomes configuration and onboarding rather than a new integration build.
Payment configuration you control. You choose which connected provider handles a given payment type from the portal rather than in code, and payment methods can be filtered by minimum amount, maximum amount and currency. Be clear about the limits, because this is where vendors in this category tend to overpromise: there is no routing by issuing country or BIN, and currency is not a proxy for market, since one currency can span several acquiring markets.
One view of activity. Transaction activity across your connected providers is visible in one place. Settlement still happens provider by provider on each provider’s own cycle, so consolidated reporting is not the same thing as consolidated settlement, and your finance team should plan for that.
Multi-tenant by design. If your platform serves sub-merchants, each tenant runs its own portal and its own payment configuration, so a merchant’s provider relationships and rates stay their own.
No provider lock-in. Because Shuttle is PSP-neutral and has no processing of its own to steer volume into, you are not tied to one provider’s network. Moving a payment type to a different provider is a configuration and onboarding change rather than a rebuild. One caveat worth planning for: Shuttle tokenises with the gateway rather than holding card data itself, so stored credentials stay with the provider that captured them and saved cards and subscriptions do not move as freely as new transactions.
If your platform takes payments across more than one market and you are weighing up how many providers to run, book a discovery call and we will go through your markets, your current providers and what adding another would actually involve.
FAQ
Does local acquiring improve authorisation rates?
Usually yes, though the size of the improvement depends entirely on the markets involved and your transaction profile. The mechanism is straightforward: issuers tend to apply less aggressive fraud screening to transactions that appear domestic, and those transactions are less likely to trigger soft declines or additional 3DS challenges. Be careful with published uplift figures, including any quoted by a provider selling you the service, because approval rates are driven by traffic mix as much as by routing. The only comparison worth trusting is one run on your own traffic, segmented by issuing country and card type.
What markets support local acquiring?
Most major payment markets support local acquiring, including the UK, all EEA countries, the US, Canada, Australia, Singapore, Hong Kong, Japan and Brazil. Coverage depends on which acquirers operate in each market and whether they support the card schemes your customers use. The markets where local acquiring makes the biggest difference are those with the widest gap between domestic and cross-border interchange, particularly where cards issued outside the region are involved.
Do I need separate contracts with each acquirer?
In a direct model, yes. You would need to negotiate and sign separate acquiring agreements in each market, each with its own pricing, compliance requirements and technical integration. That is the complexity that makes multi-market acquiring impractical for many platforms to manage alone. A payment layer changes the integration work rather than the commercial relationship. Shuttle is not an acquirer and does not issue merchant accounts, so you keep your own acquiring agreements and your own rates. What you avoid is building and maintaining a separate integration per provider, because your platform connects once and the connected providers sit behind that connection.