
Cross-border payments pass through more banks, more rules and, since November 2025, a new message standard. This is how I take a change to SWIFT payments from idea to live, safely.
A cross-border payment travels through several banks in different countries, using SWIFT to pass the instructions along. Clear, complete data and sanctions checks at every bank keep it moving.
New here? Start with How a US Payment Works: 15 Steps Inside a Bank, then come back for the detail.
How a cross-border payment moves
Read from left to right. Each box is one bank or person the payment passes through. There can be more than one correspondent bank in the middle, passing the payment on. The band at the bottom shows what keeps the payment moving: good structured data, sanctions checks at every bank, and a tracking number that follows the payment all the way.
What changed in November 2025
On November 22, 2025, SWIFT stopped accepting the old MT messages (such as MT103 and MT202) for cross-border payments. Everything now uses ISO 20022, a newer and richer format. Every payment carries its own tracking number, the UETR. Each bank can see where the payment is through SWIFT gpi, much like tracking a parcel.
| Topic | What to know |
|---|---|
| Messages | pacs.008 (customer), pacs.009 (bank and cover), pacs.004 (return), camt.056 and camt.029 (cancellation) |
| Data | Addresses split into proper fields (at least town and country), the reason for the payment, and IDs where required |
| Addresses | Addresses typed as free text are being phased out; | SWIFT has extended the original November 2026 deadline, so check the current timeline
| Security | Every bank must confirm each year that it meets SWIFT’s security checklist (the Customer Security Programme, or CSP) |
Why cross-border is harder
A payment can pass through several correspondent banks. Each one has its own sanctions checks, fees and cut-offs. One missing piece of data can stop the payment at any bank in the chain.
Data quality is the product. Clean names, addresses, the reason for the payment and what it’s paying for decide whether a payment flows straight through or sits waiting for someone to fix it by hand. Fix the data where it starts, not just the message.
Building it: short cycles, firm checkpoints
- Plan around SWIFT’s yearly update every November, public holidays in every currency, and the cut-off times of the banks in the middle.
- Test the whole chain with the banks in the middle: returns, rejections, cancellations, tracing a lost payment, and ban-list matches.
- Prove each country route live. Send a small payment, track it by its UETR, check the fees taken along the way, and make sure our accounts at the other banks (nostro accounts) match.
| Gate | Done when |
|---|---|
| E2E exit | Messages pass SWIFT’s format checks (the CBPR+ rules), tests with the middle banks passed for each route, OFAC sanctions checks (the US government’s list of banned people, companies and countries) tested on every field, accounts at other banks match |
| UAT exit | Operations, ban-list and lost-payment scenarios signed; for people sending money home, the cost and timing notices required by Regulation E checked |
| Go-live | Pilot payments checked on each route; sanctions checks, limits, second approver and call-back checks live |
Running it live
Send alerts to Slack or Teams when the SWIFT link drops, rejections rise, messages get stuck, sanctions checks take too long, or our balances at other banks run low. The investigations team uses the tracking number to find lost payments fast. If the main site goes down, the backup SWIFT link and the sanctions checks must both work, and every payment is checked by its tracking number before anything is resent.
Download the full runbook (PDF, 12 pages)
Every phase in detail, with CBPR+ messages, rules, sanctions and FX (currency exchange), exit criteria and sign-off, a pilot plan per corridor, controls, alerts, incident runbooks, disaster recovery and audit checklists.
The files behind this runbook
Every part of this runbook touches the same handful of files. Here is where each one shows up. For what is inside each file, with samples and a step-by-step checklist, see SWIFT cross-border, file by file.
| File or moment | Where it matters in this runbook |
|---|---|
| pain.001 and pacs.008 (CBPR+) | What changed in November 2025 |
| gpi tracker and UETR | How a cross-border payment moves |
| FX, fees and sanctions | Why cross-border is harder |
| pacs.004, camt.056, camt.029, camt.053 | Running it live |
More payment runbooks
- ACH payments
- Wire payments (Fedwire and CHIPS)
- Instant payments (RTP and FedNow)
- Card payments (debit, credit, prepaid)
- Checks and remote deposit capture
- Zelle for banks
- PayPal integration
- Embedded payments
The bottom line
Cross-border delivery succeeds on data quality, sanctions discipline and testing the whole chain. Prove each corridor live and track every payment by its UETR.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help