ISO 20022 Explained: Why Payments Product Managers Should Care
ISO 20022 is a global messaging standard for financial services — a common language for payments systems to communicate with each other. It is replacing the legacy SWIFT MT message format and is being adopted across CHAPS, SEPA, Fedwire, CHIPS and other major payment rails worldwide. For payments product managers, it is one of the most consequential infrastructure changes happening in the industry right now.
What Is ISO 20022?
Every payment instruction sent between banks contains structured data: who is paying, who is receiving, how much, in what currency, with what reference. ISO 20022 defines how that data is formatted, what fields are available, and what they mean.
The existing SWIFT MT format — in use since the 1970s — was designed for a world of limited data bandwidth. It uses terse, coded fields with strict character limits. An MT103 payment message, for example, can carry only 140 characters of remittance information. That is often not enough to describe what a payment is actually for.
ISO 20022 uses XML-based messages that are significantly richer. Where an MT103 has 140 characters for remittance data, the ISO 20022 equivalent — the pacs.008 message — can carry structured, coded remittance information that machines can read and process automatically.
The Migration Timeline
The SWIFT network began its ISO 20022 migration in 2023, running a coexistence period where both MT and MX (ISO 20022) messages are supported. The full MT cutoff is November 2025. CHAPS in the UK migrated in 2023. The US Fedwire and CHIPS systems have their own migration schedules through 2025.
SEPA payments (SCT and SDD) have been on ISO 20022 since their inception. TARGET2 in the EU migrated in 2023.
Why Richer Data Matters
The practical impact of ISO 20022 goes well beyond format. Richer, structured data unlocks capabilities that are genuinely valuable:
Straight-through processing — When remittance data is structured and machine-readable, payments can be reconciled automatically without manual intervention. For corporate treasury teams processing hundreds of payments daily, this is transformational.
Fraud detection — Richer sender and receiver data means fraud models have more signal to work with. Structured LEI (Legal Entity Identifier) data, purpose codes and structured addresses make anomaly detection significantly more effective.
Sanctions screening — The SWIFT MT format’s character limits mean names and addresses are often truncated or abbreviated, creating false positives and negatives in sanctions screening. ISO 20022’s structured fields eliminate ambiguity.
Cross-border transparency — ISO 20022 enables end-to-end tracking of cross-border payments with structured data throughout the correspondent banking chain. This is the foundation of SWIFT’s gpi (Global Payments Innovation) service.
What This Means for Payments Product Managers
If you are building or maintaining payment products that touch high-value or cross-border payment rails, ISO 20022 has direct product implications.
First, your payment initiation flows may need to capture more structured data. If your product initiates wire transfers on behalf of customers, you will need to collect and pass structured remittance information, LEI codes for corporate payers, and structured address fields that were previously optional or free-text.
Second, your reconciliation and reporting infrastructure needs to handle richer incoming data. The opportunity is significant — if you can expose structured ISO 20022 remittance data to your customers through your product interface, you are delivering real value that was previously unavailable.
Third, your compliance and sanctions screening systems may need updating. Systems calibrated for MT message formats will need reconfiguration to handle ISO 20022 structured fields correctly.
Common Misconceptions
ISO 20022 is sometimes described as affecting only large banks. This is not quite right. Any fintech or payments company that initiates or receives high-value payments via CHAPS, Fedwire, CHIPS or SWIFT is affected, either directly or through their banking partner. Understanding what your banking partners are doing — and what data they will accept and pass through — is essential.
It is also worth noting that ISO 20022 adoption does not happen overnight within organisations. The message format migration is the easy part. The harder part is enriching the underlying data — ensuring that payment instructions actually contain the structured information the new format supports, rather than just reformatting old data into new fields.