Definition
ISO 20022 is the ISO standard (2004) that defines a common language for financial messages: payments, securities, FX, trade finance and reporting.
It is gradually replacing the legacy standards — SWIFT MT (international interbank), ISO 8583 (cards), proprietary national formats — relying on a standardized data dictionary, a primarily XML syntax (also JSON) and a business model structured into business areas: pacs (interbank), pain (customer-to-bank), camt (cash management), etc. It has become established since March 2023: SWIFT (CBPR+), TARGET2, TIPS, EBA Clearing, Fedwire, CHAPS.
Message structure
The naming convention is xxxx.NNN.NN: the business area (4 letters), the message identifier (3 digits) and the version (2 digits). A few examples:
pain.001.001.09— initiation of a credit transfer (customer → bank).pain.008.001.08— initiation of a direct debit (SDD mandate).pacs.008.001.08— interbank credit transfer (execution).pacs.002.001.10— payment status (ACK / NACK).camt.054.001.08— debit/credit notification (bank → customer).
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08">
<FIToFICstmrCdtTrf>
<GrpHdr>
<MsgId>MSG-2025-001</MsgId>
<CreDtTm>2025-04-19T10:30:00</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<SttlmInf><SttlmMtd>CLRG</SttlmMtd></SttlmInf>
</GrpHdr>
<CdtTrfTxInf>
<PmtId><EndToEndId>E2E-12345</EndToEndId></PmtId>
<Amt><InstdAmt Ccy="EUR">200.00</InstdAmt></Amt>
<Dbtr><Nm>Alice Martin</Nm></Dbtr>
<DbtrAcct><Id><IBAN>FR76...</IBAN></Id></DbtrAcct>
<Cdtr><Nm>Bob Dupont</Nm></Cdtr>
<CdtrAcct><Id><IBAN>DE89...</IBAN></Id></CdtrAcct>
</CdtTrfTxInf>
</FIToFICstmrCdtTrf>
</Document>Advantages vs SWIFT MT / ISO 8583
| Aspect | SWIFT MT (1973) | ISO 8583 (1987) | ISO 20022 (2004) |
|---|---|---|---|
| Format | Fixed text | Binary bitmap | XML (or JSON) |
| Richness | Limited | Limited | Rich (structured entities) |
| Readability | Cryptic | Very technical | Understandable |
| Charset | ASCII | Variable | UTF-8 (multilingual) |
| End-to-end reference | Weak | Weak | Native (E2E ID) |
| Regulatory data | Difficult | Limited | Native (LEI, BIC, Purpose) |
The gains: structured data rather than free text, complete identifiers (LEI, BIC, IBAN), a native end-to-end reference (automatic reconciliation), multi-currency and multilingual support, and embedded regulatory traceability (Purpose Code, Regulatory Reporting).
SWIFT CBPR+ migration
CBPR+ (Cross-Border Payments and Reporting Plus) is the ISO 20022 profile for SWIFT international payments. MT/MX coexistence started in March 2023, and MT ends for customer payments in November 2025 — forcing every bank to migrate its core systems, APIs and file formats.
Timeline of the major migrations
- 2008 — SCT launched directly in ISO 20022 (SDD in 2009).
- 2017-2018 — SCT Inst then TIPS in ISO 20022.
- March 2023 — CBPR+ start, migration of TARGET2 and EURO1.
- June 2023 — CHAPS (Bank of England).
- July 2025 — Fedwire Funds Service.
- November 2025 — end of MT/MX coexistence for payment instructions.
Sector adoption
- Payments: SEPA (SCT, SCT Inst, SDD), TIPS, RT1, SWIFT (CBPR+), FedNow, RTP — all in ISO 20022.
- Securities: TARGET2-Securities at 100%, DTCC migrating, with ISO 15022 being progressively replaced.
- Cards: ISO 8583 remains dominant; a migration to ISO 20022 is not expected before 2030.
What ISO 20022 is not
- Not a transport protocol: it defines the content of messages, not their routing (HTTP, SWIFT FIN, AS4, MQ).
- Not mandatory for REST APIs: the Berlin Group, STET and OBIE draw on it but in JSON/REST.
- Not a single version: several versions per message, hence an IT compatibility challenge.
- Not universal on the card side: ISO 8583 remains king there, at least until 2030.
- Not only XML: version 3 (in progress) includes JSON, which is more practical for APIs.
In the PSD2 / Open Finance ecosystem
ISO 20022 is the data DNA of European payments:
- SEPA SCT/SDD: natively ISO 20022.
- Open Banking APIs: the Berlin Group, STET and OBIE draw heavily on it (
pain.001→POST /payments). - VoP:
acmt.024 / acmt.025. SRTP:pain.013 / pain.014. - PSR: the April 2026 compromise does not mandate it. It calls for communication standards issued by standardization bodies such as CEN or ISO, or other widely recognized standards (art. 35(3), provisional numbering).
Concrete examples
- BNP Paribas: a multi-year, multi-million-euro project to migrate all payment chains to MX.
- SCT FR: since 2014, all French credit transfers have been in ISO 20022 on the interbank side.
- CBPR+: the 2023-2025 MT/MX transition period requires coexistence and translation — a high cost for banks.
- TIPS: 100% ISO 20022 since 2018, a model for the other rails.
- FedNow: 100% ISO 20022 from 2023, with the US catching up to Europe.
- Tools: Volante, IR Transact, Bottomline for MT ↔ MX translation.
- Migration cost: for a large international bank, several tens of millions of euros over 3 to 5 years.