What is ISO 20022?
ISO 20022 is an open global standard that defines how financial institutions format and exchange payment messages. It sets the structure, data fields, and terminology used when banks, payment networks, and clearing systems communicate about transactions. The standard uses XML, a machine-readable format that supports far richer and more structured data than the older formats it replaced.
The standard was developed by the International Organization for Standardization. Most major payment systems worldwide have now migrated to it, making ISO 20022 the closest thing to a common language for global payments infrastructure that exists today.
Why did ISO 20022 replace the old MT format?
Before ISO 20022, most international payments ran on SWIFT's MT format, a legacy system that originated in the 1970s. MT messages carried payment instructions in relatively unstructured free-text fields. Character limits were tight. Address fields were often a single block of text rather than separate components. Key data like the ultimate creditor or purpose of payment was frequently missing or embedded in a way that required manual interpretation.
This created real operational problems. AML screening was less reliable when key fields were unstructured. Reconciliation required manual effort to parse payment details. Straight-through processing broke down when data was incomplete.
ISO 20022 fixes this by replacing free-text fields with structured, typed data elements. An address is not a single text block but a set of separate fields: street name, town, country code, postal code. A payment purpose is a defined code from a controlled list, not whatever the sending bank chose to write. Every field is clearly labelled and machine-readable from end to end.
What are the main ISO 20022 message types?
ISO 20022 messages are organized by function. The ones most relevant to payments and treasury operations are:
- pacs.008: Customer credit transfer. The primary message type for initiating a payment from one bank to another on behalf of a customer. This replaced the MT103
- pacs.002: Payment status report. Sent to confirm whether a payment was accepted, rejected, or is still pending
- pacs.009: Financial institution credit transfer. Used for bank-to-bank liquidity transfers, not end-customer payments. Replaced the MT202
- pacs.028: Payment status request. Sent to ask about the current status of a previously submitted payment
- pain.013: Request for payment. Used for the request for payment workflow on FedNow and RTP
- camt.053/054: Account statement and debit/credit notification. Used for cash management reporting, the ISO 20022 equivalent of the bank statement files previously sent in MT940 format
The "pacs" prefix stands for payments clearing and settlement. "Pain" stands for payment initiation. "Camt" stands for cash management. Each message type has a defined structure and a version number that tracks updates to the schema.
When did major payment systems migrate to ISO 20022?
The migration happened across major systems over several years. All the significant deadlines have now passed.
From November 2025, SWIFT's legacy MT payment messages are no longer used for cross-border payments. All cross-border SWIFT traffic now runs on ISO 20022 MX format. The next milestone is November 2026, when unstructured address formats will also be discontinued on both SWIFT and Fedwire.
What does ISO 20022 change in practice?
The richer data structure creates improvements that run through the entire payment chain. The most significant are:
- Reconciliation: Structured remittance data means payments arrive with clear references and purpose codes rather than free-text descriptions. This makes automated payment reconciliation more reliable and reduces the volume of exceptions that need manual review.
- Compliance screening: Structured name and address fields make sanctions and AML screening more precise. A screening system can reliably parse a structured address. It often cannot reliably parse an address embedded in a block of free text. This matters for OFAC screening specifically, since a missed match on an unstructured field creates regulatory exposure.
- Straight-through processing: Payments with complete, structured data are more likely to flow through without manual intervention at correspondent banks. This reduces repair costs and settlement delays.
- UETR tracking: ISO 20022 messages carry the UETR natively as a dedicated field rather than embedded in a free-text block, making end-to-end payment tracking cleaner and more consistent.
Why ISO 20022 matters for payment platforms
For fintechs and payment platforms building on top of modern rails, ISO 20022 is no longer optional. FedNow, RTP, SWIFT, SEPA, CHAPS, and CHIPS all use it natively. Any platform connecting to these systems needs to generate and parse ISO 20022 messages correctly.
The richer data also creates product opportunities. Platforms that pass complete, structured remittance data through the payment chain can offer their customers a better reconciliation experience on the receiving end, since the data arrives intact rather than truncated or reformatted by an intermediary that strips unrecognised fields.
