Reference
ISO 20022 is the standard behind modern payments: a shared data model, structured messages derived from it, and per-scheme usage guidelines that constrain everything. This page is the practitioner's map of it, written from delivery work on SWIFT migrations, ISO 20022 cutovers, and the production incidents in between: the message families, the status and reason codes, the MT migration, the exception flows, and the testing that decides whether any of it works.
Written by Ahmed at Analyst Engineering, a Senior Technical Business Analyst with 10+ years in banking and payments. Maintained as the standard evolves; each article carries its own review date.
Orientation in four sentences
pain messages run between a customer and their bank; pacs messages run between banks; camt messages report and investigate. A payment's progress travels as status codes (ACCP, ACSP, ACSC, RJCT) and its failures are explained by reason codes (AC01, AC04, AM04). The legacy MT formats retired for cross-border payments in November 2025, and fully unstructured addresses retire in November 2026. Everything else is detail, and the detail is what the articles below are for.
What ISO 20022 actually is, how its message families divide the payment world, and how one payment flows across all of them.
The reference tables: what each payment status guarantees, and what each rejection or return code demands.
Moving from MT to ISO 20022, and the structured-address mandate that gives the data model a deadline.
When money must come back, when payments get stuck, and when someone has to find out why.
The field-by-field test discipline that decides whether a migration goes live cleanly or limps through rejections.
New to payments as a domain? The roadmap's payments level sequences these articles, and the skill matrix tells you which to read first.
Newsletter
New ISO 20022 references and payments playbooks as the standard evolves, straight to your inbox.
No spam. Unsubscribe anytime.