How Cross-Border Payments Work
Cross-border payments move money between a payer and a payee in different countries through a chain of financial institutions, messaging networks, and compliance checks. Understanding each step helps merchants identify where costs and authorization failures originate.
Payment Initiation
The customer initiates payment in their local currency using a card, bank transfer, or local payment method. The merchant's checkout presents the transaction, often after detecting the customer's location to display the appropriate currency and methods.
Authorization Request
The payment is sent to the acquiring bank, which forwards the authorization request via the card network (Visa, Mastercard) or payment rail to the customer's issuing bank. If the acquirer is located in a different country than the issuer, the network applies cross-border assessment fees and the issuer runs stricter fraud scoring.
Currency Conversion
If the transaction currency differs from the cardholder's billing currency, foreign exchange conversion occurs — either at the network level, the acquirer level, or at the point of sale via dynamic currency conversion. The exchange rate applied includes a margin above the mid-market rate, representing a significant hidden cost.
Compliance Screening
The transaction is screened against AML rules, sanctions lists (OFAC, EU, UN), and local regulatory requirements for both the sending and receiving corridor. High-risk corridors trigger additional checks. Payment orchestration platforms typically handle this layer automatically.
Settlement
Funds move through correspondent banking networks or direct settlement arrangements to the merchant's account. Settlement timelines range from same-day on modern rails to 3–5 business days on legacy SWIFT corridors. Settlement currency and timing directly affect the merchant's FX exposure.
Why Cross-Border Payments Matter
Global ecommerce is no longer optional — international buyers now represent the primary growth vector for most scaling merchants. The size of the opportunity makes optimizing cross-border payment performance a strategic priority, not a technical afterthought.
Cross-border ecommerce reached approximately $785 billion in 2023 and is projected to exceed $1.4 trillion by 2028, according to industry research from FXC Intelligence. More telling for merchants: 70% of consumers abandon checkout when their preferred local payment method is unavailable, per J.P. Morgan's Global Payments Trends report. Authorization rate gaps between optimized and unoptimized cross-border setups routinely run 10–20 percentage points, meaning a merchant processing $10M in international volume could be leaving $1–2M in recovered revenue on the table annually by using the wrong acquiring configuration.
The Hidden Cost of Cross-Border Fees
Visa and Mastercard charge cross-border assessment fees of 0.40–1.20% per transaction, on top of standard interchange. Combined with FX margins of 1–3%, merchants accepting international cards without optimized routing can pay 2–5% in fees per transaction — before their payment processor's markup.
Cross-Border Payments vs. Domestic Payments
Understanding how cross-border transactions differ from domestic ones explains why they require a dedicated strategy rather than simply extending an existing domestic payment setup.
| Dimension | Cross-Border Payments | Domestic Payments |
|---|---|---|
| Authorization rate | 75–88% (unoptimized) / 90–96% (with local acquiring) | 92–97% |
| Settlement time | 1–5 business days (card); instant on some rails | Same-day to T+2 |
| Fee structure | Interchange + cross-border assessment + FX margin | Interchange only |
| Compliance overhead | Multi-jurisdiction AML, KYC, sanctions screening | Single-jurisdiction rules |
| Chargeback risk | Higher — cross-border disputes more likely | Lower |
| Currency exposure | FX risk between transaction and settlement | None |
| Payment method availability | Varies by country; local methods often required | Standardized per market |
Types of Cross-Border Payments
Cross-border payments span several use cases and rails, each with distinct economics and optimal routing strategies.
Card-based cross-border payments are the most common for ecommerce. Visa and Mastercard route authorization globally but apply cross-border fees when the acquirer and issuer are in different countries. Local acquiring eliminates this gap by routing through an in-country acquirer.
Bank transfers (SWIFT/SEPA) are used for high-value B2B payments and payouts. SWIFT covers 200+ countries but involves correspondent banks that each take a cut and add delay. SEPA Cross-Border Credit Transfers cover the EU/EEA at near-domestic cost.
Local payment methods — iDEAL (Netherlands), PIX (Brazil), UPI (India), Boleto (Brazil), SEPA Direct Debit — are increasingly preferred by consumers in their home markets. Supporting these requires in-country infrastructure or a payment orchestration layer with multi-currency support.
Remittances are consumer-to-consumer cross-border transfers, dominated by players like Wise, Western Union, and Remitly. For merchants, the relevant analog is cross-border payouts to suppliers, contractors, and marketplace sellers.
Blockchain/stablecoin rails are an emerging category enabling near-instant, low-cost cross-border settlement, particularly for emerging market corridors where traditional banking infrastructure is expensive or slow.
Best Practices
For Merchants
Use local acquiring in your top revenue markets. A single foreign acquirer routing all international transactions is the most common cause of poor authorization rates. Identify your top 3–5 international markets by volume and establish local acquiring relationships or work with an orchestration platform that has them.
Present local currencies at checkout. Displaying prices in the customer's local currency — and being transparent about conversion — reduces abandonment. Dynamic currency conversion at the point of sale can improve conversion but must be priced fairly; predatory DCC margins damage trust.
Offer local payment methods. In Brazil, PIX and Boleto drive the majority of transactions. In the Netherlands, iDEAL dominates. In India, UPI is ubiquitous. Ignoring these in favor of card-only checkout alienates a large share of potential buyers.
Monitor authorization rates by country corridor. Aggregate authorization rates hide corridor-specific failures. Break down declines by issuer country, card type, and bin range to identify where routing optimization will have the highest impact.
Understand your FX exposure. If you settle in USD but sell in EUR, GBP, or BRL, exchange rate movements between transaction date and settlement date affect your realized revenue. Consider settlement currency options or hedging for high-volume corridors.
For Developers
Implement geolocation-based currency detection at checkout. Use IP geolocation or browser locale to pre-select the appropriate currency. Always allow the user to override. Store the selected currency in the session and pass it consistently through the payment flow.
Handle soft declines specific to cross-border transactions. Issuer declines on cross-border transactions often carry specific decline codes (e.g., Visa's 05 Do Not Honor vs. 62 Restricted Card) that indicate whether a retry with a different acquirer or 3DS authentication will improve outcomes. Build retry logic that interprets these codes.
Implement 3DS2 with cross-border awareness. 3DS2 authentication data (device fingerprint, transaction history) helps issuers approve cross-border transactions that would otherwise be declined for perceived fraud. Ensure your 3DS implementation passes the full data set, not just the minimum required fields.
Use webhooks for settlement status tracking. Cross-border settlement is asynchronous and can fail or be delayed at the correspondent banking layer. Implement webhook handlers for settlement events rather than polling, and build reconciliation pipelines that tolerate multi-day settlement windows.
Common Mistakes
Routing all international volume through a single domestic acquirer. This is the single most impactful mistake. A UK acquirer processing a Brazilian Mastercard creates a cross-border transaction at the network level, triggering higher fees and lower approval rates. The fix is local acquiring or smart routing through an orchestration platform.
Ignoring FX margin opacity. Many payment providers apply FX conversion at opaque rates — 2–4% above mid-market — without surfacing this to the merchant. Always benchmark your provider's conversion rates against the ECB or XE mid-market rate on a sample of transactions.
Treating cross-border compliance as a one-time setup. Sanctions lists are updated continuously. Corridor regulations change. AML thresholds shift. Merchants who configure compliance rules at onboarding and never revisit them accumulate regulatory risk over time.
Failing to test checkout in target markets. A checkout that works perfectly for a US card may break for a Brazilian CPF-required form, a German IBAN input, or a Dutch iDEAL redirect flow. Test checkout end-to-end in each target market with local test credentials and local network conditions.
Conflating settlement currency with transaction currency. A transaction in EUR does not mean you will settle in EUR. Many acquirers convert to USD before settlement by default. Understand your settlement currency configuration and its implications for your FX exposure before going live.
Cross-Border Payments and Tagada
Tagada is a payment orchestration platform built to solve exactly the routing, cost, and authorization rate challenges that make cross-border payments complex at scale. Rather than locking merchants into a single acquirer's cross-border capabilities, Tagada routes each transaction to the optimal acquirer based on the customer's location, card type, and transaction context.
How Tagada Optimizes Cross-Border Performance
Tagada's routing engine evaluates acquirer performance data in real time to direct cross-border transactions to the acquirer most likely to approve them at the lowest cost. For merchants expanding into new geographies, Tagada provides access to local acquiring relationships without requiring direct contracts with in-country processors — reducing both time-to-market and per-transaction cost on international volume.
For development teams, Tagada exposes a single unified API that abstracts the complexity of multi-acquirer routing, currency conversion, and compliance screening. Instead of building and maintaining separate integrations for each acquiring bank and local payment method, engineers integrate once and gain access to Tagada's full network of acquirers and payment methods across supported corridors.