Global Economic Governance Series

Exchange, Currency, and International Payments

A plain-English guide to how cross-border money actually moves: exchange rules, correspondent banks, payment messages, domestic settlement systems, and the public bodies that shape the main rulebooks.

Source note: This article relies on the IMF Articles of Agreement; BIS and CPMI materials on central bank cooperation, payment systems, correspondent banking, and the PFMI; the FSB’s cross-border payments roadmap and targets; the FX Global Code; ECB TARGET and SEPA materials; Federal Reserve Fedwire materials; and Swift’s own oversight and messaging descriptions.

Scope

Cross-border money movement is a chain, not one wire

When a company says it “sent an international payment,” several different systems may already be involved. The invoice may be written in one currency, the payer may fund in another, one or more banks may convert or route the payment, a messaging network may carry the instruction, and a domestic settlement system may finish the last leg. The IMF sets key treaty rules for exchange arrangements and current international payments. The BIS, CPMI, FSB, central banks, and domestic payment infrastructures shape the plumbing that makes the payment possible.

Jurisdiction

Global, using official international and central-bank materials plus domestic payment-system examples.

Lines covered

Foreign exchange, correspondent banking, payment messaging, wholesale settlement, retail simplification, and public cross-border-payment reform work.

Reporting basis

Treaty texts, official committee overviews, official infrastructure pages, and official market-practice standards only.

Period lens

The current operating stack, with only enough history to show why the main payment and exchange layers exist.

Sources

Primary-source docket

The sources below define the legal and infrastructure layers this article describes.

IMF Articles of Agreement — the IMF’s purposes, Article IV exchange-surveillance framework, Article VIII current-payments rules, and Article XXX(d) definition of “payments for current transactions.”
About the IMF — official history note that the IMF was established in 1944.
BIS overview — BIS mission and official note that the BIS was established in 1930.
History of the CPMI and CPMI overview — the payments committee’s history and current role.
Principles for Financial Market Infrastructures — the core international standards for major payment, clearing, and settlement infrastructures.
CPMI correspondent banking report — official description of the correspondent-banking layer used in cross-border payments.
FX Global Code — official good-practice principles for the wholesale foreign exchange market.
FSB cross-border payments work and G20 targets page — official roadmap and end-2027 target structure for improving cross-border payments.
ECB TARGET Services, T2, and SEPA — official examples of settlement in central bank money and regional payment harmonization.
Federal Reserve Fedwire Funds Service — official example of real-time gross settlement with immediate, final, and irrevocable processing.
Swift oversight and Swift corporate overview — official explanation that Swift is a messaging provider, not itself a payment or settlement system.

Money can cross a border without any physical cash crossing a border.

What actually moves is usually a set of claims, messages, FX conversions, and final settlements across ledgers run by banks and payment infrastructures. That is why exchange law, banking rules, and payment-system rules all matter at the same time.

History

The modern payments stack was built in layers

Cross-border money movement did not begin as one finished global design. It was assembled over time: first through central-bank cooperation, then through treaty rules on exchange and current payments, then through payment-system committees, infrastructure standards, conduct codes, and reform programs aimed at speed, cost, transparency, and access.

1930

BIS creates a permanent central-bank forum

The BIS says it was established in 1930 and exists to support central banks in the pursuit of monetary and financial stability through international cooperation.

1944–1945

The IMF builds the treaty layer for exchange and current payments

The IMF was established in 1944. Its Articles say the Fund is meant to promote exchange stability and help create a multilateral system of payments for current transactions.

1990

The payments committee becomes permanent

The BIS says the G10 Governors established the Committee on Payment and Settlement Systems in 1990. That committee was later renamed the CPMI.

2012

The PFMI raises the infrastructure standard

The PFMI set stronger international standards for major payment, clearing, and settlement infrastructures after the financial-crisis era.

2017

The FX Global Code adds a conduct layer

The FX Global Code was published as a set of principles of good practice for the wholesale foreign exchange market.

2020–2027

Cross-border payments become a formal reform program

The FSB and CPMI now coordinate work under the G20 roadmap, with most global performance targets set for end-2027.

Mechanics

Walk one international payment from invoice to final settlement

Use a simple example: a company in one country owes an exporter in another country. The goods may already be shipped. The payment still has to pass through several legal and operating layers before the exporter has final usable funds.

Step 1

The contract sets the payment currency

The first question is not “which bank?” It is “which currency?” The sales contract or invoice sets the unit of account. If the payer funds in another currency, an FX leg appears before the payment reaches the seller.

What can go wrong: people treat currency choice as a small pricing detail when it also changes funding, hedging, and payment risk.

Step 2

The legal filter asks what kind of payment it is

The IMF Articles distinguish “payments for current transactions” from capital transfers. Current payments include payments tied to foreign trade, services, interest, and similar current activity.

Why it matters: exchange restrictions and currency practices are not judged in exactly the same way for every kind of cross-border movement.

Step 3

The banks decide how to route the money

Most banks do not hold accounts in every currency and every country. Cross-border payments often depend on correspondent banking, where one bank provides payment services to another.

What can go wrong: more banks in the chain usually means more fees, more data checks, more timing risk, and more places for a payment to pause.

Step 4

The payment instruction moves through a messaging layer

Swift says it is a secure financial messaging provider and is not itself a payment or settlement system. In plain English, a message is the instruction. It is not the same thing as final settlement.

Why it matters: people often mistake the message network for the entire payment system.

Step 5

The final leg settles inside a payment system

The last step usually happens in a domestic or regional payment system. The Federal Reserve says Fedwire is a real-time gross settlement system and that transfers are immediate, final, and irrevocable once processed. The ECB says T2 settles payments one by one on a continuous basis in central bank money with immediate finality.

Why it matters: “sent” is not the same thing as “final.” Finality depends on the settlement system that closes the transfer.

Step 6

Controls and data standards shape speed and friction

The FSB says cross-border payments still face high cost, low speed, limited access, and insufficient transparency. CPMI work on ISO 20022 data harmonization is meant to make data travel more cleanly through the chain.

What can go wrong: messy data, repeated checks, and inconsistent formats create delay even when the payer and payee are both legitimate.

Step 7

Some regions reduce friction by redesigning the local layer

The ECB says SEPA has eliminated differences between domestic and cross-border euro payments across SEPA countries. That does not eliminate all global payment friction, but it shows what harmonized rules and common standards can do inside one currency area.

Ledger

One payment changes legal and operational form several times

The same payment may begin as an invoice obligation, turn into an FX need, become a chain of interbank claims, move as a message, and end as settled funds inside a payment system.

Stage	Main body or actor	What happens	Why it matters
Contract and invoice	Commercial parties	The parties set the amount due and the currency of account.	The currency choice affects pricing, hedging, and the rest of the payment chain.
Exchange-law layer	IMF treaty framework plus domestic authorities	The payment is classified inside the country’s exchange regime and current-payments rules.	A trade payment is not governed exactly like every capital movement.
Customer-bank layer	Commercial bank	The sending bank debits the payer, checks data, and decides how to fund and route the transfer.	The bank’s funding, cut-off, screening, and correspondent access all shape speed and cost.
Correspondent layer	Correspondent banks	One bank uses another bank’s account and network to move value across currency or jurisdiction lines.	This is where many cross-border payments gain extra handoffs and extra friction.
Messaging layer	Swift or another messaging arrangement	The payment instruction and related data are transmitted across the network.	A message tells systems and banks what to do. It is not the final transfer itself.
Settlement layer	Fedwire, T2, or another domestic/regional infrastructure	The final transfer is completed inside a system with its own legal and operational finality rules.	This is where “payment sent” becomes “payment settled.”
Reform and oversight layer	CPMI, FSB, central banks, and domestic supervisors	Standards, targets, oversight, and operating reforms are used to improve safety, speed, transparency, and access.	The global system is not static. It is still being redesigned.

Misreads

What people often get wrong

Most confusion comes from treating payment, exchange, and settlement as if they were one machine with one switch.

Common mistake

“Swift moves the money.”

Swift says it is a messaging provider, not a payment or settlement system. It carries instructions and related data.

Common mistake

“The IMF clears international payments.”

No. The IMF provides treaty rules, surveillance, and policy discipline. It is not the operator of the world’s payment rails.

Common mistake

“One click means one transfer.”

In many cases the payment is really a series of debits, credits, messages, conversions, and settlements across several balance sheets.

Common mistake

“A traded currency is the same thing as a freely usable payment currency.”

Not always. Market trading, exchange restrictions, settlement access, and infrastructure reach are different questions.

Common mistake

“Fast front-end experience means instant legal finality everywhere.”

Not necessarily. Finality depends on the rules of the actual payment system that closes the transfer.

Terms

The key terms get easier when they are tied to one payment

These are the minimum terms needed to read a cross-border payment clearly.

IMF term

Current international transactions

Plain English: ordinary cross-border payments tied to trade, services, interest, and similar current activity rather than long-term capital transfers.

Why it matters: this is a core line in the IMF Articles.

IMF term

Exchange arrangement

Plain English: the broad system a country uses to manage its currency and exchange-rate policy.

Why it matters: payment friction can start long before the bank message is sent.

Banking term

Correspondent banking

Plain English: one bank provides payment services and account access to another bank.

Why it matters: this is a core cross-border routing layer when banks do not have direct local access everywhere.

Payments term

Real-time gross settlement

Plain English: payments are settled one by one, in real time, instead of being netted and settled later in a batch.

Why it matters: this is the model used by major wholesale systems like Fedwire and T2.

Settlement term

Central bank money

Plain English: settlement money held as a claim on the central bank, rather than on a private bank.

Why it matters: many key wholesale systems use it because it reduces credit risk in the settlement asset.

Legal term

Finality

Plain English: the point at which a transfer is no longer provisional and cannot be unwound under the ordinary operating rules of the system.

Why it matters: “payment sent” and “payment final” are not always the same moment.

Data term

ISO 20022

Plain English: a common structured language for financial messages.

Why it matters: better data structure can reduce breaks, delays, and repeated manual repair work.

FX term

FX Global Code

Plain English: an internationally used set of good-practice principles for the wholesale foreign exchange market.

Why it matters: cross-border payments often depend on FX markets before the payment ever reaches the settlement system.

Visibility

Most rulebooks are public. Most routing choices are not.

The broad architecture is highly visible. The IMF Articles, CPMI materials, PFMI, FSB roadmap, TARGET, SEPA, Fedwire, and Swift’s role descriptions are all public. That means much of the system is knowable from primary sources.

The less visible layer is operational and firm-specific: which correspondent path a bank chose, what fee logic it applied, how it sequenced screening, what liquidity it used, what internal cut-off it enforced, or why it repaired or rejected a specific message. Those details usually sit inside private contracts, internal controls, or bank operations manuals rather than public rulebooks.

Why this matters: people often imagine a hidden master switch controlling the whole system. In practice, the public architecture is broad and real, while much of the day-to-day friction comes from private operating choices inside that public framework.

The payment chain is only half the story.

This article explains how cross-border money is routed and settled. The next installment explains why banks sit in the middle so often, why they hold capital and liquidity against risk, and why prudential rules matter to trade and payment reliability.

Next article: Banking Rules and Prudential Capital

A cross-border payment is usually not one thing moving through space. It is a handoff between ledgers, rules, and infrastructures.

Payments rule

Exchange, Currency, and International Payments

Exchange, Currency, and International Payments

Cross-border money movement is a chain, not one wire

Primary-source docket

Money can cross a border without any physical cash crossing a border.

The modern payments stack was built in layers

BIS creates a permanent central-bank forum

The IMF builds the treaty layer for exchange and current payments

The payments committee becomes permanent

The PFMI raises the infrastructure standard

The FX Global Code adds a conduct layer

Cross-border payments become a formal reform program

Walk one international payment from invoice to final settlement

The contract sets the payment currency

The legal filter asks what kind of payment it is

The banks decide how to route the money

The payment instruction moves through a messaging layer

The final leg settles inside a payment system

Controls and data standards shape speed and friction

Some regions reduce friction by redesigning the local layer

One payment changes legal and operational form several times

What people often get wrong

“Swift moves the money.”

“The IMF clears international payments.”

“One click means one transfer.”

“A traded currency is the same thing as a freely usable payment currency.”

“Fast front-end experience means instant legal finality everywhere.”

The key terms get easier when they are tied to one payment

Current international transactions

Exchange arrangement

Correspondent banking

Real-time gross settlement

Central bank money

Finality

ISO 20022

FX Global Code

Most rulebooks are public. Most routing choices are not.

The payment chain is only half the story.

PAGES

SOCIAL

Working...