Resources
ISO 20022: deadlines, migration and implementation
What ISO 20022 is, the SWIFT and SEPA migration deadlines, the pacs and camt message set, and a practical implementation checklist for banks and payment institutions.
SWIFT CBPR+
MT coexistence ended Nov 2025
TARGET2 / T2
Migrated March 2023
Core set
pacs · pain · camt
What is ISO 20022?
ISO 20022 is the international standard for financial messaging. Instead of the fixed, abbreviated fields of legacy MT messages, it carries structured data: full debtor and creditor identification, structured postal addresses, purpose codes, regulatory reporting and up to 9,000 characters of remittance information. The same business model is reused across payments, cash management, securities, cards and FX, which is why schemes worldwide converged on it.
For a payment institution the practical consequence is simple: richer data in, richer data out — better sanctions screening, better automated reconciliation, fewer manual repairs.
ISO 20022 deadlines and migration timeline
- SEPA (SCT, SCT Inst, SDD) — ISO 20022 since launch; SCT Inst is mandatory for euro-area PSPs under the Instant Payments Regulation.
- TARGET2 / T2 and EURO1 — migrated to ISO 20022 in March 2023.
- SWIFT cross-border (CBPR+) — coexistence with MT began March 2023 and ended in November 2025; cross-border payments and reporting now run on pacs/camt.
- Domestic schemes — CHAPS, Fedwire and other national RTGS systems each publish their own migration and enhanced-data timetables.
Always validate against the current scheme usage guideline: message versions and mandatory fields are refreshed on an annual cycle.
The message set you will actually use
| Message | Purpose |
|---|---|
| pain.001 | Customer initiates a credit transfer (corporate to bank) |
| pain.002 | Status of an initiation request |
| pacs.008 | Interbank customer credit transfer |
| pacs.009 | Financial institution transfer / cover payment |
| pacs.002 | Payment status report (ACSP, ACSC, RJCT) |
| pacs.004 | Payment return |
| camt.053 | End-of-day statement |
| camt.054 | Debit / credit notification |
Implementation checklist
- Map your internal payment object to the scheme's usage guideline, field by field.
- Generate and validate XML against the official XSD plus the scheme's extra rules before submission.
- Adopt structured party data (BIC, LEI, structured addresses) — free-text addresses are being phased out.
- Propagate the end-to-end identifier and UETR across every hop and store them for investigations.
- Consume pacs.002 status reports and camt statements to drive automated reconciliation and a double-entry ledger.
- Secure the channel: mutual TLS, IP allowlisting, signed payloads for APIs, or SFTP with PGP for file exchange.
- Make submissions idempotent and retry-safe, with a circuit breaker per bank connection.
How Amadeus Pay simplifies ISO 20022 compliance
Amadeus Pay is a multi-rail payment platform with a hub-and-spoke bank connectivity layer. Each bank or BaaS partner is a connector adapter behind one common interface, so message construction, validation, status handling and reconciliation are implemented once rather than per institution.
- ISO 20022 message builder and validator for pacs.008 / pacs.009 with pacs.002 status ingestion.
- SEPA, SWIFT and host-to-host (API and SFTP) channels with mutual TLS, IP allowlisting and signature verification.
- Idempotency keys, exponential backoff and circuit breakers on every outbound rail.
- Double-entry ledger with camt-driven reconciliation, plus a full audit log of administrative actions.
- Optional blockchain settlement leg for treasury movements alongside the fiat rails.
Frequently asked questions
What is ISO 20022?
ISO 20022 is an international standard for electronic data interchange between financial institutions. It defines a common XML (and JSON) syntax and a shared business model for payments, cash management, securities and trade messages — replacing the terse legacy MT/flat-file formats with structured, richly annotated data.
What is the ISO 20022 deadline?
For cross-border payments and reporting over SWIFT, the coexistence period with legacy MT messages ended in November 2025, after which CBPR+ institutions exchange ISO 20022 (pacs) messages. In the euro area, TARGET2/T2 and EURO1 migrated in March 2023, and SEPA schemes have used ISO 20022 since inception. Domestic schemes (for example CHAPS in the UK and Fedwire in the US) follow their own published timetables.
Which ISO 20022 messages matter most for payments?
pacs.008 (customer credit transfer), pacs.009 (financial institution transfer), pacs.002 (payment status report), pacs.004 (payment return), pain.001 (customer credit transfer initiation), pain.002 (status report) and camt.052/053/054 (intraday, end-of-day and debit/credit notification statements).
What does ISO 20022 implementation actually require?
Message generation and validation against the scheme's usage guidelines, structured party and address data, richer remittance information, end-to-end reference propagation, reconciliation against camt statements, and secure connectivity — typically mutual TLS APIs or SFTP with PGP-signed files, plus IP allowlisting.
Informational guide. Confirm dates and field rules against the current scheme documentation before go-live.