Factsheets: 📈 Markets 🎯 Mandates 📋 Case Studies 📘 SOPs 🏛 Trade Bodies 🏙 Cities 🌍 Countries 🇮🇳 Indian States ⚓ Ports 🏛️ SEZs 🤝 Blocs 📜 FTAs 🛤 Corridors ⚙ Verticals 📦 Commodities 🧮 Tools ⚖️ Compare 🌐 Bilateral Hubs 📚 Library 🎓 Academy ✍️ Essays 📰 Blog 🔤 Lexicon ❓ FAQ 📡 Authority Sources ⚡ Daily Pulse 📰 Topic Briefs 📡 Google Signals 🧭 Scope Scape cron-refreshed
Live factsheets · cron-refreshed

All factsheets at a glance

Command center →
📈 Markets
554
global + India · commodities + indices + shares + crypto + FX
minute
🎯 Mandates
69
sell + buy · live
daily
📋 Case Studies
37
closed · anonymised
weekly
📘 SOPs
42
step-by-step playbooks
weekly
🏛 Trade Bodies
1,350
291 baseline + 1059 hand-curated
monthly
🏙 Cities
1,584
global atlas
daily
🌍 Countries
184
multilateral
weekly
🇮🇳 Indian States
37
state trade profiles
monthly
⚓ Ports
52
global maritime gateways
monthly
🏛️ SEZs
31
global SEZ profiles
monthly
🤝 Blocs
28
tracked
monthly
📜 FTAs
526
active or signed
monthly
🛤 Corridors
37
tracked
monthly
⚙ Verticals
50
sectoral
weekly
📦 Commodities
51
HS-coded intelligence
monthly
🧮 Tools
105
free utilities
monthly
⚖️ Compare
pairwise combinations
monthly
🌐 Bilateral Hubs
184
India × every country
weekly
📚 Library
140
interconnected
monthly
🎓 Academy
25
trade education
monthly
✍️ Essays
30
long-form analysis
monthly
📰 Blog
34
editorial
weekly
🔤 Lexicon
312
glossary terms
monthly
❓ FAQ
155
curated Q&A
monthly
📡 Authority Sources
140
curated · vetted
hourly
⚡ Daily Pulse
145
rolling 5,000 cap
hourly
📰 Topic Briefs
29
permanent archive
hourly
📡 Google Signals
Trends·News·Alerts
hourly
🧭 Scope Scape
61
11 scopes
hourly

Cross-border payment rails

Trade does not move until the payment moves. The cross-border payment-rail system is fragmenting from SWIFT-as-default into a multi-rail world — and the trader needs to know which rail their bank will accept which counterparty on.

For most of the last fifty years, cross-border trade payment in major currencies was operationally synonymous with one combination: a SWIFT message coordinating settlement that, for dollar-denominated obligations, cleared through CHIPS or Fedwire on the US side. The other major-currency systems — CHAPS in the UK, TARGET2 in the Eurozone, BoJ-Net in Japan — handled their respective currency legs but the international interbank messaging layer was overwhelmingly SWIFT. A trader, financier, or treasurer arranging cross-border payment did not need to think about which messaging rail because there was effectively one choice.

That has changed. Since approximately 2022, the cross-border payment-rail landscape has fragmented along geopolitical, currency, and technological lines. SWIFT remains the dominant messaging rail by volume but its market share is declining at the margin, with growing volumes routing via the renminbi-denominated CIPS, the Russian rouble-denominated SPFS, the Indian-rupee bilateral UPI cross-border integrations, the SEPA-area Wero, and various stablecoin and CBDC pilots. The 2022 sanctioning of Russian banks from SWIFT, in particular, demonstrated to a wide range of governments and corporates that the SWIFT-as-monopoly assumption was not safe to plan on. The result is that trade payments now flow over a multi-rail system, and the trader, the corporate treasurer, and the trade-finance bank have to know which rail will be accepted by which counterparty for which purpose.

The page below treats each major rail in turn: what it actually does, what its operational reach is (not what its press releases claim), and the practical question of which rail a particular consignment's payment leg should run on.

The dollar rail (SWIFT + CHIPS / Fedwire)

SWIFT — the dominant interbank messaging system

11,000+ member institutions200+ countries~50M messages/dayHeadquartered in Belgium

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is the dominant interbank messaging system, headquartered in La Hulpe, Belgium, and connecting roughly eleven thousand financial institutions in more than two hundred countries. SWIFT itself does not move money — it moves messages. The actual settlement of a SWIFT-coordinated dollar payment occurs on CHIPS (the Clearing House Interbank Payments System) or Fedwire (the Federal Reserve's wire system) within US banking hours; a SWIFT-coordinated euro payment settles on TARGET2 within Eurozone banking hours; a SWIFT-coordinated yen payment settles on BoJ-Net.

For trade purposes, the canonical SWIFT message types are MT103 (single customer credit transfer — the typical commercial payment), MT202 (general financial institution transfer — the bank-to-bank leg), MT700 (issuance of a documentary credit, i.e. a letter of credit), MT760 (issuance of a guarantee), and MT799 (free-format message — used for confirmations and queries). SWIFT is migrating from MT to ISO 20022 message standards under the MX programme; the migration completes in November 2025, and from 2026 onward all interbank correspondent messaging is on the ISO 20022 standard, which carries richer structured data and supports more granular sanctions screening.

CHIPS + Fedwire — the dollar settlement layer

CHIPS: ~$1.8T/dayFedwire: ~$4T/dayUS-basedSanctions-regulated

CHIPS is the privately-operated dollar interbank settlement system run by The Clearing House (a consortium of the largest US banks), settling roughly 1.8 trillion dollars per day. Fedwire is the Federal Reserve's RTGS system for dollar payments, settling roughly 4 trillion dollars per day. The two systems together clear essentially all large-value dollar interbank obligations. For a cross-border trade payment, the dollar leg ends at one of these systems regardless of where the buyer or seller is located.

The systemic implication of this is that any dollar-denominated cross-border transaction is subject to US sanctions law, because the transaction must clear through a US-based system that is bound by OFAC, the Treasury, and the broader US sanctions regime. This is the rail-level mechanism through which US sanctions on third countries become operationally binding on banks in fourth countries: a French bank routing a dollar payment between an Iranian and a Chinese counterparty would clear that payment through CHIPS or Fedwire and would therefore be subject to OFAC enforcement risk.

The renminbi rail (CIPS)

CIPS — Cross-Border Interbank Payment System

~1,500 indirect participants~200 direct participantsOperating since 2015People's Bank of China

CIPS is China's renminbi cross-border interbank payment system, operational since 2015 and headquartered in Shanghai. CIPS combines the messaging and settlement layers (it is a clearing system, not just a messaging system) for renminbi-denominated cross-border transactions. As of 2026 CIPS has approximately 200 direct participants and 1,500 indirect participants, with growing usage among banks in countries that conduct substantial renminbi-denominated trade with China, including Russia, Iran, the GCC states, and a number of African and Latin American economies.

For trade purposes, CIPS is operationally relevant if both sides of a transaction agree to denominate in renminbi. The use cases include: Russian commodity exports invoiced in renminbi (substantial since 2022), Iranian oil-and-gas exports invoiced in renminbi, and a growing share of intra-Belt-and-Road infrastructure financing. CIPS does not yet match SWIFT's global reach — it has limited correspondent coverage in Western Europe and North America — but its share of the segments where it operates is structurally significant.

The rouble rail (SPFS) and SBP

SPFS — System for Transfer of Financial Messages

~580 participantsOperating since 2014Bank of RussiaUsed by EAEU + Russia + Iran banks

SPFS is Russia's domestic interbank messaging system, originally built in 2014 as a contingency for SWIFT disconnection, and brought into much heavier use after the 2022 SWIFT sanctions on major Russian banks. SPFS is messaging-layer only — settlement still occurs through the Bank of Russia's RTGS, similar to TARGET2 or Fedwire — but the messaging layer was the critical missing piece, and SPFS has now connected approximately 580 participants including most Russian banks plus a number of banks in Belarus, Kazakhstan, Armenia, Iran, and a handful of other jurisdictions.

For trade purposes, SPFS is operationally relevant for rouble-denominated trade with Russia and the EAEU. Its reach beyond that is limited and politically contested — banks in Western jurisdictions face sanctions exposure for connecting to SPFS, which has constrained its growth. The system is functional within its addressable market but is not a SWIFT replacement at the global level.

The rupee rail (UPI cross-border) and the Indian payment stack

UPI cross-border — National Payments Corporation of India

Live: UAE, Singapore, France, Mauritius, Sri Lanka, Bhutan, NepalBilateral integrationsNPCI International Payments Limited (NIPL)

UPI (Unified Payments Interface) is India's domestic real-time retail-payments system, in operation since 2016 and processing roughly 18 billion transactions per month as of 2026. The international extension — UPI cross-border — is delivered by NPCI International Payments Limited (NIPL) through bilateral integrations with foreign payment systems. As of 2026 the live integrations include the UAE (where Indian-origin remittance and merchant payment flows are large), Singapore (PayNow integration), France (a partial merchant-acceptance integration), Mauritius, Sri Lanka, Bhutan, Nepal, and a number of others in active rollout.

For trade purposes, UPI cross-border is currently strongest in the smaller-value retail and SME-cross-border space rather than the large-value trade-finance space. The structural relevance to trade is in the SME cross-border merchant-acceptance use case: an Indian SME exporter selling to an Emirati buyer can now receive payment via UPI rails rather than SWIFT for transactions below substantial threshold sizes, which materially reduces the cost and the time of small-ticket cross-border B2B payment. The large-value trade-finance leg still uses SWIFT plus correspondent banking.

The euro rail (TARGET2 + SEPA + Wero)

TARGET2 / TARGET3 / T2 — Eurosystem RTGS

Eurosystem real-time gross settlement20 Eurozone members + non-euro EU~€2.4T/day

TARGET2 (now technically T2 following the 2023 consolidation with T2S) is the Eurosystem's real-time gross settlement system, operated by the European Central Bank with the participation of all Eurozone national central banks. Large-value euro interbank obligations settle on T2, including the euro leg of any SWIFT-coordinated cross-border trade payment. T2 connects to SWIFT and to TIPS (the European instant-payments system) and is the structural anchor of the European interbank settlement layer.

SEPA + SCT Inst — retail and merchant payments

36 SEPA countriesSEPA Credit Transfer Instant since 2017Up to €100,000 per transaction

SEPA (Single Euro Payments Area) covers thirty-six countries — all twenty-seven EU member states plus EEA states and a number of others — and provides standardised euro retail payment, direct debit, and (since 2017) instant credit transfer (SCT Inst) up to €100,000 per transaction. For cross-border trade in the SME segment, SEPA Credit Transfer is operationally a much faster and cheaper rail than the SWIFT-plus-correspondent path that the same payment would have taken outside SEPA.

Wero / EPI — the European pan-merchant scheme

Live since 2024Belgium, Germany, France, Netherlands16 founding banksPan-European wallet

Wero is the European Payments Initiative's pan-European wallet and merchant-payment scheme, in live rollout since 2024 across Belgium, Germany, France, and the Netherlands, with progressive expansion to other SEPA countries through 2026 and beyond. Wero is positioned as a European-controlled alternative to Visa, Mastercard, PayPal, and Apple Pay for euro-denominated retail and merchant payments. Its trade-relevance is currently retail and SME-cross-border within the SEPA area; large-value B2B and wholesale-cross-border are not yet in scope.

CBDC pilots and stablecoin settlement

The central-bank-digital-currency space has moved from research to live pilot in several jurisdictions over 2022–2026. The most operationally significant CBDC pilots from a cross-border trade perspective are the BIS-coordinated multi-CBDC platforms — Project mBridge (China, Hong Kong, Thailand, UAE, Saudi Arabia, with various observer states), Project Mariana (France, Switzerland, Singapore), and Project Agora (a wider central-bank consortium exploring tokenised commercial bank money on a shared ledger). Each of these pilots is testing whether a central-bank-coordinated rail can settle cross-border trade obligations more efficiently than the SWIFT-plus-correspondent stack.

As of 2026, none of these CBDC pilots has graduated to commercial production at scale. mBridge is the closest to operational use, with documented test transactions involving real commercial counterparties for trade-related payments. The expected commercial-readiness timeline for any of these systems to substitute for SWIFT-correspondent on a meaningful share of trade flows is at minimum the late 2020s.

Separately, regulated stablecoins — most prominently Circle's USDC and a growing list of bank-issued and non-bank-issued offerings under the EU's Markets-in-Crypto-Assets (MiCA) regime that came into effect from 2024 — have begun to be used for cross-border settlement at the wholesale level by some firms. The use cases are concentrated in commodity-trading flows, where the speed advantage over SWIFT-correspondent settlement is operationally meaningful, and in certain high-friction corridors where correspondent banking has been thinned by de-risking. Stablecoin trade settlement is operationally working at meaningful volume but remains a small fraction of the overall SWIFT-correspondent stack.

The trader's practical question

The trader, corporate treasurer, or trade-finance banker arranging a particular cross-border payment is asking three connected questions.

First, which currencies are acceptable to both counterparties? If both sides accept dollars or euros, the established SWIFT-plus-correspondent stack is the default. If one side requires renminbi, CIPS becomes operationally relevant. If one side is sanctions-exposed, dollar and euro rails close and renminbi or rouble rails open. The currency choice is the gating decision.

Second, which rails will both banks accept? The bank's compliance posture is decisive. Many Western banks will not connect to SPFS at all; many Indian banks have CIPS connectivity but require enhanced due diligence; some smaller banks have limited correspondent coverage and require the flow to route via a particular money-centre bank. The bank's accept-list is the operational constraint.

Third, what is the time-and-cost profile of the available rails? SWIFT-correspondent dollar payment typically settles in one to three business days at a fee structure of $25–$60 per leg plus FX spread; SEPA Instant is sub-ten-second at minimal fee within Europe; UPI cross-border is sub-minute at minimal fee on the live corridors; CIPS is roughly comparable to SWIFT for renminbi cross-border. The right rail is the cheapest acceptable rail that both banks will accept for the chosen currency.

The fragmentation thesis. The cross-border payment system is moving from a single-rail world (SWIFT-as-default) to a multi-rail world. The operational implication for trade is that the question can the payment leg complete? is no longer answerable by checking only one system. Sophisticated trade-finance operations now maintain a per-counterparty rail map: which counterparties can be paid via which rails, what the time-and-cost profile of each is, and what the contingency rails are if the primary rail closes. The atlas page above is the vocabulary for that map.
PhiloJain Music
Loading…

Explore

Explore the AJG knowledge graph

Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.

All hubs · 80 surfaces · click to expand ↓