Payments - Introduction / Learning brief
Domestic versus cross-border payments
Your notes
In simple terms / 01
What this means in plain language
Compares a same-country payment with one that crosses a border, showing how differing currencies, correspondent banks, longer timelines, higher cost, and additional compliance checks turn a single hop into a multi-party chain.
A domestic payment and a cross-border payment answer the same request — move value from a payer to a payee — but the second must cross boundaries the first never meets. A domestic payment stays inside one country: both banks usually share a currency, a clearing system, and a rulebook, so the money often moves in a single hop and settles the same day. A cross-border payment leaves that shared world. The two banks may sit in different currencies, connect to different clearing systems, and answer to different laws, and they often hold no account with each other. To bridge the gap the payment usually passes through one or more correspondent banks — banks that keep accounts for each other and hand the value along. Each extra party and each currency conversion adds time, cost, and compliance checks, which is why a cross-border transfer is slower and more expensive than a domestic one.
Complete lesson / 02
Understand the full idea, step by step
The same instruction — pay this supplier — can be routine on Monday and an expedition on Tuesday. The difference is one line on the invoice: the supplier's bank is in another country. Nothing about the payer's intention changed; everything about the journey did. This lesson is about exactly what the border adds, and why.
What a domestic payment quietly shares
A domestic payment is simple because so much is agreed before it starts. Both banks work in the same currency, so nothing needs converting. Both connect to the same clearing and settlement systems, so one hop carries the payment between them. Both follow one rulebook and one legal regime, so timing, rights, and the meaning of every message are settled in advance. Cross the border and that shared ground disappears — different currency, no common system, different laws. Everything a cross-border payment does differently is the work of rebuilding, link by link, what the domestic payment got without asking.
| Domestic | Cross-border | |
|---|---|---|
| Currency | One — no conversion | Often two — someone converts, at a rate with a margin |
| Route | One hop through a shared system | A chain of correspondent banks, each adding a leg |
| Rules | One scheme rulebook, one legal regime | Different laws and practices at every link |
| Time | Same day, sometimes seconds | Longer — each link checks and forwards, across time zones and calendars |
| Charges | Usually a single, known fee | Fees may be deducted at more than one point in the chain |
| Screening | One jurisdiction's checks | Every bank in the chain screens against the lists binding it |
Correspondent bank
A correspondent bank holds accounts for other banks and makes or receives payments on their behalf. It is how banks reach places they have no presence: Bank Alfa cannot hold dollars at Cassia Bank, but it holds a US-dollar account at Meridian Bank, and Meridian can reach Cassia. From Bank Alfa's perspective, its dollar account at Meridian is its nostro ("ours" — our account, on your books); on Meridian's own books, that same account is a vostro ("yours" — your account, on our books). Same account, two names, depending on whose ledger you are reading.
| Invoice to pay | USD 18,500.00 |
|---|---|
| Bank Alfa's customer rate (INR per USD, sell side) | 84.0000 |
| Debit to Asha Traders' INR account | INR 1,554,000.00 |
Asha Traders holds rupees; the supplier must receive dollars. Bank Alfa sells USD against INR at its customer rate — from Bank Alfa's perspective, quoting INR per one USD — and that rate includes the bank's margin over the interbank market rate. The conversion happens here, at the first link; what travels onward through the chain is a US-dollar payment. Any charges deducted along the chain are a separate matter from the exchange rate, which is why the two must never be lumped together when explaining an arrival amount.
Read the steps as text
- 01MessageThe customer orders a USD transfer abroadOrdering customer → Bank Alfa (ordering bank)
The ordering customer instructs Bank Alfa to pay a supplier banked at Cassia Bank in another country. Bank Alfa has no direct account relationship with Cassia — that is why correspondents exist.
- 02ProcessingBank Alfa validates and screensBank Alfa (ordering bank)
Format and balance checks plus sanctions screening. Cross-border payments face stricter screening because more jurisdictions are involved.
Screening checkpoint: Outbound cross-border screening — Ordering and beneficiary parties, banks, and remittance text are screened before the payment leaves.
- 03PostingThe customer's account is debitedBank Alfa (ordering bank)
Bank Alfa books the debit and, per the charge option, any fees.
- DR Ordering customer's account at Bank Alfa — USD 250,000.00
- 04MessageThe MT103 goes to Bank Alfa's USD correspondentBank Alfa (ordering bank) → Meridian Bank (correspondent) · MT103
In the serial method the payment instruction itself travels through the account chain. Meridian holds Bank Alfa's USD account (Bank Alfa's nostro), so Meridian can debit it.
- 05ProcessingMeridian validates and screens in the middleMeridian Bank (correspondent)
Every bank in the chain screens independently. Meridian also checks that Bank Alfa's account has cover for the debit.
- 06SettlementMoney moves across the books of MeridianMeridian Bank (correspondent)
Both Bank Alfa and Cassia hold USD accounts at Meridian. Settlement here is a book transfer in commercial bank money: Meridian debits one account it holds and credits the other.
No clearing house is involved — the correspondent's ledger is the settlement venue. This is settlement in commercial bank money, not central bank money.
- DR Bank Alfa's USD account at Meridian (vostro) — USD 250,000.00
- CR Cassia's USD account at Meridian (vostro) — USD 250,000.00
- 07MessageCassia is advised its nostro was creditedMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT910
The MT910 credit confirmation lets Cassia's reconciliation match expected funds against its nostro account movement.
- 08MessageThe MT103 continues serially to CassiaMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT103
Meridian forwards the payment instruction to the beneficiary bank with the full ordering and beneficiary details intact.
- 09ProcessingCassia validates the incoming paymentCassia Bank (beneficiary bank)
Account checks and inbound screening. Only when funds are confirmed on the nostro and checks pass is the beneficiary credited.
- 10PostingThe beneficiary is creditedCassia Bank (beneficiary bank)
Cassia credits its customer, net of any beneficiary-side charges the charge option allows.
- CR Beneficiary's account at Cassia — USD 250,000.00
The invoice's journey, link by link
- INSTRUCTION
Asha Traders instructs Bank Alfa: pay USD 18,500.00 to the supplier's account at Cassia Bank, quoting the invoice reference.
- VALIDATION
Bank Alfa validates the instruction and screens the parties against the sanctions lists binding it — the first of several screenings this payment will face.
- LEDGER
Bank Alfa debits Asha Traders INR 1,554,000.00, applies the agreed rate, and now owes USD 18,500.00 onward.
- MESSAGE
A bank-to-bank payment message — an MT103 on the legacy SWIFT rails, a pacs.008 under ISO 20022 — leaves for Meridian Bank, naming the parties, the amount, and the destination. Information travels; the dollars do not ride inside it.
- VALIDATION
Meridian Bank checks and screens the payment under its own jurisdiction's rules. A name that is unremarkable in one country may be listed in another — each link applies its own lists.
- SETTLEMENT
Meridian debits Bank Alfa's vostro account on its books (Bank Alfa's nostro, seen from the other side) and pays Cassia Bank USD 18,500.00 — value moving as book entries across correspondent accounts, not as anything travelling down a wire.
- NOTIFICATION
Cassia Bank screens once more under its own rules, credits the supplier, and confirmations flow back. Depending on the charge option, the supplier may see slightly less than USD 18,500.00 — the next block explains why.
You may be wondering: why might the supplier receive less than Asha Traders sent?
Because a chain has more than one place where a fee can be taken. Payment standards define charge-bearing options that say who pays the banks' charges: in the MT world the options are OUR (the payer bears all charges), SHA (shared), and BEN (the payee bears them); ISO 20022 expresses the same idea with the codes DEBT, SHAR, CRED, and SLEV (the last meaning charges follow a scheme's service-level rules). Under the shared and payee-pays options, banks along the route may deduct their charge from the amount in flight. Which options are actually available depends on the product and the scheme — customers cannot always choose freely.
WHAT IF — Meridian Bank's screening raises an alert: a party name in the message resembles an entry on a sanctions list Meridian is bound by.
What happens: The payment is held — not rejected, not lost. It waits in a review queue while an investigator establishes whether the alert is a true match or a coincidence of names.
How it is handled: Kabir, a sanctions investigator at Meridian Bank, compares the message's party details against the list entry and documents his conclusion. A false match — by far the more common outcome — releases the payment to continue; a true match triggers the actions the law requires. For Asha Traders this looks like a day or two of unexplained delay; in reality it is the control doing exactly what every jurisdiction in the chain requires of its banks.
STRICTLY SPEAKING
Strictly speaking, "cross-border" and "hard" are not the same thing. Within the Single Euro Payments Area (SEPA), a euro payment from one member country to another travels under one shared rulebook and behaves like a domestic payment — a border crossed without correspondent chains or conversion. In the other direction, the classic pain points are shrinking: ISO 20022 messages carry richer, better-structured data through initiatives such as CBPR+ (Cross-Border Payments and Reporting Plus), and SWIFT gpi gives banks end-to-end tracking of a payment's route, fees, and status. The chain still does more work than a single domestic hop — but it is far less of a black box than it used to be.
FOR NOW, REMEMBER
- Domestic payments inherit shared ground — one currency, one system, one rulebook; cross-border payments must rebuild it link by link.
- Correspondent banking is the rebuilding: banks holding accounts for banks, with nostro and vostro naming the same account from each side's books.
- The message hops bank to bank; the value moves as entries across correspondent accounts — two journeys that must agree.
- Time, cost, and screening all scale with the number of links: each bank checks, may charge, and screens against its own jurisdiction's lists.
- A screening hold is the system working, not failing — and schemes like SEPA prove a border alone need not make a payment hard.
TRY IT YOURSELF
The supplier confirms receipt — of USD 18,462.00, not the USD 18,500.00 Asha Traders sent. The payment used a shared charge option. What best explains the difference?
Meridian Bank carried this payment across the border. The next topic opens up how such relationships actually work — nostro and vostro mechanics, serial versus cover payments, and what it costs banks to hold each other's accounts.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A domestic payment shares one currency, clearing system, and rulebook, so it usually settles in a single hop.
- 02
A cross-border payment often crosses currencies and legal regimes, so it travels through correspondent banks that hold accounts for one another.
- 03
Every extra party and currency conversion adds time, cost, and compliance checks.
Practical use cases / 04
Where you would use this
A person paying rent within their own country uses a domestic credit transfer that clears the same day at little or no cost.
An importer paying an overseas supplier sends a cross-border payment that converts currency and routes through a correspondent bank, arriving in one to three business days.
A compliance team screens a cross-border payment against more than one sanctions regime, because each bank in the chain checks the message under its own rules.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional customer, Tomas Herrera, in one country pays a fictional supplier, Lakeside Textiles, in another. A domestic payment of EUR 5,000.00 to a local account would reach the payee the same day for a flat fee of EUR 0.20. The cross-border version converts EUR 5,000.00 into the supplier's currency at a rate that carries a 0.8% margin — costing EUR 40.00 more than the mid-market rate would — and passes through one correspondent bank that deducts a EUR 15.00 handling fee. Herrera's bank sends the instruction on Monday; after currency conversion, correspondent routing, and sanctions checks at two institutions, Lakeside Textiles is credited on Wednesday. The same EUR 5,000.00 therefore arrives smaller and slower across a border than within one, and the difference is made entirely of the extra currency, parties, and checks the crossing requires.
Evidence & review / 07
Evidence & review
Correspondent-banking model applies to cross-border payments generally; MT/ISO 20022 charge codes apply where those standards are used; the SEPA contrast applies to euro payments between SEPA countries.
What this brief simplifies: Shows a single serial chain with one correspondent and one FX conversion at the first link; real routes may involve more intermediaries, cover payments (taught separately), FX at other points, and scheme-specific charge rules. The exchange rate and amounts are synthetic illustrations, not market data.
Sources for this brief7
- Market practice
Correspondent banking (final report) ↗ — CPMI, Bank for International Settlements · Correspondent banking structure and role in cross-border payments
Published in July 2016; its statistics cover 2011-2015 and are dated, but the definitions and arrangement types remain widely used.
- Market practice
Swift Standards MT (annual standards releases) ↗ — Swift · MT 103 and charge-bearing options
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Market practice
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority · ChargeBearerType external code set
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council · SEPA as a cross-border area behaving domestically
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.
- Market practice
Swift gpi (global payments innovation) ↗ — Swift · Cross-border payment tracking
Only public summaries are used here; the full service definition and rulebook sit behind a swift.com account.
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · Screening of payment parties along the chain
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Asha Traders scenario and FX illustration
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.