Cross-Border Payments: A Complete Business Guide

Cross-border payments are how value moves between parties in different countries. For a finance team in Dubai paying a supplier in Vietnam, an e-commerce platform in São Paulo paying creators in twelve countries, or a multinational reconciling subsidiary flows across four continents — the experience is shaped by an infrastructure layer that most people never see and that has changed surprisingly little since the 1970s.

This guide walks through how that infrastructure works today, why it produces the cost and friction it does, what is changing through stablecoin rails and payment orchestration, and what businesses should evaluate when choosing a partner. It is intended as a working reference, not a sales document.

What is a cross-border payment?

A cross-border payment is any transfer of value between a sender in one country and a recipient in another. In practice that simple definition covers a wide range of flows with very different requirements:

• Wholesale interbank — large-value settlement between financial institutions, often via real-time gross settlement (RTGS) systems and SWIFT messaging. The largest category by dollar value.
• Business-to-business (B2B) — supplier payments, intercompany transfers, marketplace payouts, royalty and licensing payments. The most operationally complex category for most readers of this guide.
• Consumer remittance — individuals sending money across borders, typically smaller values but high volume. The most studied category because of its development implications.
• Card-on-foreign-rail — a consumer using a card issued in country A at a merchant in country B. Settlement happens through card networks rather than correspondent banking.

For this guide, "cross-border payments" primarily refers to B2B flows where the sender and recipient are businesses, and where the underlying transaction has documentation, compliance, and reconciliation requirements that consumer remittance does not.

The scale of the market

Cross-border payments are one of the largest financial activities in the world. The Bank for International Settlements (BIS) tracks cross-border payment flows through its Committee on Payments and Market Infrastructures, and industry analysts (including McKinsey in its annual Global Payments Report) place the combined B2B and consumer cross-border flow in the range of $150 trillion or more per year.

The G20 has identified cross-border payments as a priority area, and in 2020 the Financial Stability Board (FSB) published its Roadmap for Enhancing Cross-Border Payments with four explicit improvement targets: cost, speed, access, and transparency. Progress against these targets is now measured publicly through the FSB's annual monitoring report.

How cross-border payments work today

The dominant infrastructure remains correspondent banking — a model where banks settle cross-border payments through chains of intermediary banks holding accounts with each other.

Correspondent banking

When a business in country A sends a payment to a recipient in country B, its bank rarely has a direct relationship with the recipient's bank. Instead, the sender's bank uses an intermediary bank that holds accounts in country B's currency. That intermediary credits the recipient's bank, which credits the recipient. For many corridors the chain involves three or four banks before the payment lands.

Each hop introduces:

• Its own compliance review (sanctions, AML, transaction monitoring).
• Its own operating hours and cut-off times.
• Its own fee.
• Its own books to be reconciled.

The cumulative effect is the friction that businesses experience as "the wire is taking three days."

SWIFT messaging

The Society for Worldwide Interbank Financial Telecommunication (SWIFT) is the messaging network that coordinates instructions between banks. SWIFT does not move money itself — it carries the message ("Bank A instructs Bank B to credit Account X with USD 50,000"). Actual settlement happens through correspondent relationships in the background.

SWIFT GPI (Global Payments Innovation), introduced in 2017, improved end-to-end visibility on cross-border payments and made tracking more reliable. SWIFT's migration to the ISO 20022 messaging standard, completing through 2025, brings richer payment data (including structured beneficiary information, purpose codes, and remittance data) that downstream systems can use.

FX intermediaries

Cross-border payments almost always involve foreign exchange. The FX conversion can happen at the sender's bank, an intermediary, or the recipient's bank — and the rate spread (the difference between the customer rate and the wholesale mid-market rate) is often the largest single cost component for B2B cross-border payments.

Specialist FX providers (Convera, Ebury, Wise Business, AFEX, etc.) offer tighter spreads than most banks for SMB and mid-market volumes by aggregating flow and competing on transparency.

Settlement systems

For the largest interbank flows, settlement happens via systems like CLS (Continuous Linked Settlement) which mitigates principal risk in FX transactions. Domestic RTGS systems (Fedwire in the US, TARGET2 in the eurozone, RTGS-NDS in Saudi Arabia) handle the local settlement leg.

Traditional rails vs stablecoin rails: a comparison

The most discussed alternative to correspondent banking is stablecoin settlement — moving value on a public blockchain in a token pegged to a fiat currency. The comparison is worth making in concrete terms:

The choice is rarely binary. In practice, mature platforms route through whichever rail fits each transaction. Payment orchestration is the layer that makes that routing possible.

Why cross-border payments are still slow

Three structural reasons explain why a payment that could move in seconds takes days:

Intermediary hops

Each correspondent in the chain operates on its own schedule, with its own compliance team and cut-off times. A payment from Dubai to São Paulo may pass through a New York intermediary that's only "open" for that purpose during US East Coast banking hours. Friday afternoon in Dubai means Monday morning in New York.

Compliance reviews

Sanctions screening, AML transaction monitoring, and KYC checks happen at multiple points along the route. Each review can pause the payment for human-in-the-loop review. For higher-risk corridors, jurisdictions, or amounts, a payment may sit in queue for hours per bank. See our compliance guide for what each check actually does.

Local cut-offs, weekends, and time zones

Settlement only happens during business hours in each relevant jurisdiction. A payment that enters the system Friday afternoon in one corridor may not begin to move until the next business day in the destination. Holiday calendars compound the effect — what looks like a "delay" is often the system working as designed.

The cost breakdown

Cost in cross-border payments is rarely a single line item. The total cost of a B2B cross-border payment typically combines five components:

For consumer remittance, the World Bank tracks corridor-level pricing through its Remittance Prices Worldwide database. The global average cost of sending USD 200 was reported around 6.3% in recent years — well above the 3% target set by the United Nations Sustainable Development Goals. B2B payments avoid the worst retail markups but still pay multiple intermediary fees.

What's changing

Stablecoin rails

Stablecoins — digital assets designed to track a fiat currency — can move value across borders in minutes on public blockchains, with settlement happening 24/7. For businesses, this opens the possibility of moving funds outside banking hours, without correspondent chains, and with on-chain audit evidence. Read our stablecoin payments guide for the mechanics and trade-offs, and our stablecoins for cross-border article for worked examples.

Payment orchestration

An orchestration layer sits above multiple payment rails and routes each transaction through the rail that fits best — cost, speed, regulatory exposure, or partner availability. Orchestration can mix traditional fiat rails with stablecoin rails behind a single integration, so a business doesn't have to pick one. See our orchestration guide for how this works.

Documented settlement

Beyond the rail, businesses increasingly want every cross-border payment to carry verifiable documentation — the agreement it relates to, the counterparty checks that were performed, the compliance evidence. Agreement-linked payments are designed to make this part of the transaction itself rather than a separate reconciliation exercise.

Infrastructure modernization

Traditional rails are not standing still. ISO 20022 adoption brings richer payment data. SWIFT GPI now covers the majority of cross-border bank traffic. National instant payment systems (FedNow in the US, PIX in Brazil, UPI in India, Aani in the UAE) are being interlinked through BIS-led projects like Project Nexus. Central bank digital currencies (CBDCs) are in various stages of pilot in over 130 jurisdictions, and the BIS Innovation Hub is running multi-CBDC settlement pilots through Project Agorá and Project Mariana.

Major corridors and their characteristics

Cross-border payment cost, speed, and reliability vary dramatically by corridor. A USD→EUR payment between two major money-center banks is a different operational profile than a USD→PKR payment to a smaller institution in a regulated emerging market.

Cost ranges are illustrative based on publicly reported pricing for B2B mid-market volumes; actual cost depends heavily on volume, relationship, and partner mix.

Regulatory landscape by region

Cross-border payments are among the most heavily regulated financial activities. The regulatory landscape varies significantly by region — and a payment that touches three jurisdictions touches three sets of rules.

United Arab Emirates and MENA

The UAE has emerged as a regulatory leader for fintech and digital assets. Key authorities:

• Central Bank of the UAE — payment service provider regulations and CBDC pilots ("Aani" instant payment system).
• VARA (Virtual Assets Regulatory Authority) — Dubai's dedicated regulator for virtual asset service providers.
• ADGM and DIFC — financial free zones with their own regulators (FSRA and DFSA respectively) and frameworks for payment and crypto activities.

Saudi Arabia's SAMA (Saudi Central Bank) regulates payment institutions and runs the Fintech Saudi program. See our MENA digital payments guide for a deeper regional view.

European Union

The EU's Payment Services Directive (PSD2, with PSD3 in development) and the Markets in Crypto-Assets Regulation (MiCA, fully applicable from late 2024) together create one of the most comprehensive frameworks globally. PSD3 is expected to further harmonize cross-border payment treatment.

United States

The US operates a layered federal/state framework. The OFAC sanctions regime applies extraterritorially to USD-denominated transactions. FinCEN administers the Bank Secrecy Act and AML obligations. Money transmission is state-licensed (the MTL regime), with stablecoin-specific federal legislation under active development.

Asia-Pacific

Singapore (MAS), Hong Kong (HKMA, SFC), and Japan (FSA) operate sophisticated frameworks for both traditional payments and virtual asset activities. India's Reserve Bank of India (RBI) regulates inbound flows tightly through the Foreign Exchange Management Act (FEMA).

What to evaluate when choosing a partner

Whether you stay on traditional rails, move to stablecoin rails, or use an orchestration layer that combines both, the evaluation criteria are similar:

• Settlement speed and finality. How long until the recipient can use the funds? When is settlement irreversible? These are different questions — a payment can be "delivered" but still reversible for a window.
• Total cost. Look beyond the headline fee to FX spread, intermediary fees, and any settlement-side cash-out cost. Run the math on a representative transaction, not the brochure example.
• Compliance design. What KYC, KYB, AML, and KYT screening is built in? How are alerts handled? Read our compliance guide.
• Documentation. Does each payment carry a record sufficient for audit, dispute, or tax purposes? Can you retrieve a complete trail months later?
• Corridor coverage. Does the partner support the specific countries and currencies you actually use — not just the marquee corridors on their website?
• Reliability. What is the track record on uptime, support response times, and incident handling? Past performance is a meaningful signal.
• Integration cost. What does it take to implement? API quality, sandbox access, and documentation matter more than they look.
• Regulatory posture. What licenses does the partner hold, in which jurisdictions, and how are gaps in coverage handled through partner arrangements?

Common pitfalls to avoid

A short list of mistakes that come up frequently in cross-border payment evaluations:

• Comparing only headline fees. The fee is one component; the FX spread is often larger.
• Ignoring beneficiary-side costs. Some providers settle in fiat at the destination; others settle in stablecoin and leave the off-ramp to the recipient. The total experience matters.
• Underestimating compliance friction. A cheap rail that drops 10% of payments into manual review is not cheap.
• Building for one corridor and assuming others work the same way. Each corridor has its own characteristics.
• Conflating settlement finality with "delivered." Card payments are reversible for months; stablecoin transfers are final on confirmation.
• Treating the rail as the whole picture. Documentation, reconciliation, and reporting often consume more operations time than the payment itself.

A typical AXON-supported flow

To make the above concrete, here is a representative B2B cross-border payment as AXON Transfer is designed to support it:

1. Counterparty onboarding. Both sender and recipient complete KYB. Ultimate beneficial owners verified and screened against sanctions and adverse media lists.
2. Agreement reference. The underlying contract is hashed and the hash is associated with the payment, so the link between agreement and settlement is verifiable later.
3. Routing decision. The orchestration layer evaluates the transaction against available rails — fiat correspondent, stablecoin, or partner network — and picks based on configured priorities (cost, speed, regulatory profile).
4. Compliance checks. Sanctions screening, KYT on any on-chain leg, and risk scoring applied before the payment moves.
5. Settlement. Funds move via the selected rail. For stablecoin legs, settlement is confirmed on-chain in minutes; for fiat legs, through the correspondent or partner.
6. Documentation captured. The full transaction record — counterparty data, agreement hash, route taken, compliance evidence, settlement confirmation — is available to both parties for reconciliation and audit.

(Subject to applicable licensing and partner arrangements.)

Where AXON fits

AXON Transfer is designed to support cross-border B2B payments with documented settlement and compliance-aware routing. AXON Pay is designed as the orchestration layer for accepting fiat and stablecoin payments through a single integration. Together they target the operational reality described above: a single layer that handles the rail, the compliance, and the documentation in one workflow.

AXON's services are subject to applicable licensing and partner arrangements. Nothing on this page constitutes legal, regulatory, tax, or investment advice. Statistical ranges shown are illustrative based on publicly reported industry data and should be validated against your specific corridor and volume profile.