Cross-border payments cost 2-4x more than domestic transactions. The global cross-border payments market reached $212.55 billion in 2024 and is projected to hit $320.73 billion by 2030 (Grand View Research), but most of that value leaks out through interchange premiums, currency conversion fees, and compliance overhead.
For businesses expanding internationally, cross-border payments compliance isn’t just a regulatory checkbox. It determines whether you can actually sell in a market, what it costs you to process each transaction, and how many of those transactions succeed. The rules vary by region, the costs stack in ways that aren’t always visible, and 72% of merchants report higher failed payment rates for cross-border transactions compared to domestic ones (PYMNTS).
Key takeaways:
- Cross-border processing costs 2-4x domestic rates (interchange + FX + scheme fees)
- 72% of merchants report higher failed payment rates for cross-border transactions
- Local payment methods dominate in key markets: BLIK 70% in Poland, Alipay/WeChat 90% in China
- Local acquiring eliminates cross-border interchange premiums (0.5-1.5%)
The real cost of cross-border payments
Cross-border processing fees accumulate across multiple layers, and each layer takes a cut.
| Fee type | Typical cost | Notes |
|---|---|---|
| Interchange premium | 0.5-1.5% above domestic | UK-EEA jumped to 1.15-1.5% post-Brexit |
| Currency conversion | 2.5-3% | Often embedded in exchange rate, not itemized |
| Scheme fees | 0.1-0.2% additional | Visa/Mastercard cross-border assessments |
| **Combined impact** | **2-4x domestic** | $200-400K extra on $10M international revenue |
Source: Federal Reserve Bank of Kansas City, Gitnux
When the UK left the EU, interchange for UK-EEA ecommerce transactions jumped from the regulated 0.2-0.3% to 1.15% for debit and 1.5% for credit. That’s a 5-7x increase on a single fee line item.
Local acquiring eliminates most of these premiums. When you process through a bank in the customer’s country, the transaction is domestic from the card network’s perspective. No cross-border interchange, no scheme surcharges, minimal FX costs if you settle in local currency. For businesses with meaningful volume in specific markets, the economics of local acquiring are clear. The complexity is accessing it: traditionally, that meant establishing banking relationships in each country.
Compliance requirements by region
Payment regulations have grown at a 15% annualized rate over the last decade (Thunes). Each region layers its own requirements on top of global standards like PCI DSS.
Region Key requirement What it means EEA (PSD2/SCA) Two-factor authentication 3DS 2.0 required; exemptions for United Kingdom SCA + Transfer of Funds Regulation Originator/beneficiary details for all transactions India (RBI) Additional CNP authentication Affects any merchant selling to Indian consumers Indonesia/Vietnam Data localization Payment data must reside on in-country servers Brazil LGPD + Pix dominance GDPR-like rules; Pix is default payment method EU (6AMLD) Expanded AML requirements Effective 2025; AMLA centralized oversight
For detailed PCI requirements, see our guide to ecommerce PCI compliance.
European Economic Area (PSD2/SCA): Strong Customer Authentication requires two-factor authentication for online card payments. The customer must verify using two of three factors: knowledge (password/PIN), possession (device/OTP), or inherence (biometric). 3D Secure 2.0 is the primary compliance mechanism. SCA applies when both the card issuer and acquirer are within the EEA. “One-leg-out” transactions where only one party is in the EEA are exempt.
India (RBI): The Reserve Bank of India mandates additional authentication for all card-not-present transactions. This applies to any merchant accepting cards from Indian consumers, not just those based in India. If you sell to Indian customers, you need a payment flow that supports this additional authentication step.
Global AML/KYC: The 6th Anti-Money Laundering Directive (6AMLD) took effect in 2025 with expanded predicate offenses and the creation of a centralized Anti-Money Laundering Authority (AMLA). New tax-reporting frameworks (DAC8 in the EU, CARF globally) align with AML standards and take effect in 2026.
Currency conversion: where the fees hide
Key point: 94% of cross-border shoppers expect to pay in their local currency, and 99% want to use their preferred payment methods (PYMNTS).
Meeting those expectations means handling currency conversion somewhere in your payment flow. The question is where the conversion happens and who bears the cost.
Conversion method How it works Cost to customer Dynamic Currency Conversion Customer sees home currency at checkout 2-4% (visible) Acquirer conversion Processor converts at settlement 2.5-3% (hidden) Multi-currency pricing Prices set in local currency, settle locally None
Dynamic Currency Conversion (DCC) lets customers see prices in their home currency at checkout. The merchant’s acquirer handles the conversion, and the markup (typically 2-4%) is disclosed to the customer. Customers often decline DCC because the markup is visible.
Acquirer conversion happens when you settle in a currency different from the transaction currency. Your processor converts at their rate, and the markup is embedded in the exchange rate rather than itemized. This is where the 2.5-3% average FX cost comes from.
Multi-currency pricing means setting prices in local currencies and settling in those currencies. This shifts currency risk to you but eliminates conversion costs for customers. It requires local acquiring or a processor that supports local currency settlement.
Real-time settlement is accelerating. EU instant payments regulation now requires euro transfers to settle within 10 seconds (EUR-Lex). RTGS systems have reduced average cross-border settlement times from 3 days to 12 hours (FSB Annual Progress Report). Faster settlement means less currency exposure.
Why local payment methods drive conversion
Digital wallets now account for 66% of global ecommerce value, up from 34% in 2014 (PYMNTS). That’s $15 trillion in wallet-funded transactions. But which wallets matter depends entirely on where you’re selling.
| Market | Dominant method | Market share |
|---|---|---|
| Poland | BLIK | 70% of ecommerce |
| China | Alipay + WeChat Pay | 90% of mobile |
| India | UPI | Dominant for A2A |
| Brazil | Pix | Default method |
Source: Stripe
If you enter these markets offering only Visa and Mastercard, you’re asking customers to use payment methods they rarely touch.
The conversion impact is measurable. Businesses offering Apple Pay saw a 22.3% increase in conversion. WeChat Pay integration showed 13% conversion lift (Stripe). Real-time A2A payments like UPI, BLIK, and Pix are projected to approach $3.8 trillion by 2030 (PPRO).
Not offering local payment methods isn’t a minor optimization miss. It’s a market access problem. Customers abandon carts when their preferred payment method isn’t available. The 72% higher failure rate for cross-border payments compounds this: even customers who try to pay with a card they rarely use for online shopping are more likely to see that transaction decline.
Managing cross-border payments at scale
B2B transactions represent 59.39% of cross-border payment volume (Allied Market Research). Cross-border B2B e-commerce exports from Asia alone reached $1.8 trillion in 2025 (FXC Intelligence). The scale of international payments infrastructure isn’t just a consumer checkout problem.
The traditional approach to multi-market payments means separate acquiring relationships in each country. Each relationship requires its own integration, its own compliance documentation, its own reconciliation process. For a business operating in 10 markets, that’s 10 integrations to build and maintain.
Payment orchestration provides a different architecture. A single integration connects to local acquirers, local payment methods, and regional processors across markets. Compliance requirements like 3D Secure authentication are handled consistently across providers. Transaction data consolidates in one place rather than fragmenting across country-specific systems.
Orchestra connects to 90+ payment providers through a single JavaScript library. When you expand to a new market, you configure local acquiring and payment methods through the same integration you already have. Cross-border compliance, currency handling, and local payment method support come through the same API. For more on how this applies to international payment processing considerations, or how to approach streamlining global payments, we’ve covered those topics in detail.
The underlying shift is from building payment infrastructure per-market to building it once and configuring it per-market. Global payment acceptance becomes a configuration problem rather than an integration problem.
Frequently asked questions
How much do cross-border payments cost compared to domestic?
Cross-border processing typically costs 2-4x domestic rates. This includes interchange premiums (0.5-1.5% higher than domestic), FX conversion (2.5-3% average), and cross-border scheme fees. When the UK left the EU, UK-EEA ecommerce interchange jumped from 0.2-0.3% to 1.15-1.5%, illustrating how quickly these costs can change.
What compliance requirements vary by country for payments?
PSD2/SCA in Europe requires two-factor authentication for online card payments. India’s RBI mandates additional authentication for all card-not-present transactions. Indonesia and Vietnam require data localization. Brazil has LGPD data protection rules similar to GDPR. The 6th Anti-Money Laundering Directive (6AMLD) adds EU-wide requirements effective 2025.
Why do cross-border payments fail more often than domestic?
72% of merchants report higher failed payment rates for cross-border transactions compared to domestic. Causes include authentication requirements that the payment flow doesn’t support, currency or card type mismatches, and processors not optimized for specific regions or card issuers. Local acquiring typically improves approval rates.
What is local acquiring and why does it matter?
Local acquiring processes transactions through a bank in the customer’s country, making the transaction domestic from the card network’s perspective. This eliminates cross-border interchange premiums (0.5-1.5%) and scheme surcharges, and typically improves approval rates. The trade-off is managing relationships in each market, which payment orchestration simplifies.
Do I need to offer local payment methods in each market?
For meaningful conversion, yes. BLIK handles 70% of ecommerce in Poland. Alipay and WeChat Pay account for 90% of mobile payments in China. Not offering local methods means asking customers to use payment methods they rarely use, which directly impacts conversion. Businesses saw 22.3% conversion increases from Apple Pay and 13% from WeChat Pay in markets where those methods are popular.