ISO 20022
What is ISO 20022?
ISO 20022 is a global standard that defines how financial institutions structure and exchange electronic messages for payments, securities, cash management, and foreign exchange. Published by the International Organization for Standardization in 2004, it sets out a shared data dictionary, a common modeling approach, and design rules for messages carried in XML and ASN.1 syntax.
The standard is pronounced "ISO twenty-oh-two-two". It doesn't impose one universal message format. Instead it gives the industry a common vocabulary that each payment scheme profiles for its own rails, which is why a credit transfer and a domestic can both be ISO 20022 messages while carrying scheme-specific rules. Real-time and high-value systems adopted it first, and estimates roughly 80% of global high-value payments by volume will be processed using ISO 20022.
Key facts
- Published by: International Organization for Standardization, first released in 2004
- Pronounced: "ISO twenty-oh-two-two"
- Syntax: XML and ASN.1, built on a central data dictionary shared across every message type
- Covers: payments, securities, cards, trade services, cash management, and foreign exchange
- Used by: SEPA, domestic real-time payment schemes, and SWIFT cross-border traffic
Types
ISO 20022 message names follow a fixed pattern: a four-letter business area, then a three-digit message identifier and a version number. Three business areas cover most of what a payments or treasury team handles.
- Pain (payments initiation) – instructions a corporate or customer sends to its own bank, such as pain.001 for a credit transfer initiation and pain.008 for a collection
- Pacs (payments clearing and settlement) – interbank messages that move funds between financial institutions and report their status
- Camt (cash management) – account statements, balance reports, and status or investigation requests
Why it matters
- Structured remittance data travels with the payment. A receiving accounting system can match an incoming credit to the invoice it pays without a human reading a free-text reference field, which removes a large share of manual work.
- Party data sits in discrete fields. Names, addresses, and identifiers are separately tagged rather than packed into one text block, so and sanctions screening engines match against clean fields instead of parsing strings.
- One vocabulary spans multiple rails. A bank or processor that maps its core systems to ISO 20022 once can connect to instant payment schemes, SEPA, and cross-border messaging without maintaining a separate translation layer for each.
- Field length stops truncating detail. Legacy formats capped remittance information at a few short lines, which forced senders to drop invoice references that the beneficiary needed to identify the payment.
How it compares
ISO 20022 sits alongside two older message standards that still run in production. The difference is scope: ISO 20022 covers the full financial message lifecycle, while the others were each built for one job.
| Standard | Structure | Primary use |
| ISO 20022 | XML or ASN.1, shared data dictionary | Bank transfers addressed by , instant payments, securities, cash reporting |
| MT | Fixed tag-and-field text blocks | Legacy cross-border correspondent banking messaging |
| ISO 8583 | Compact binary or ASCII bitmap fields | Card authorization and clearing messages between acquiring and issuing banks |
Card payments have not migrated: ISO 8583 remains the working standard for card authorization traffic, so a handling both card and bank-transfer flows runs the two standards in parallel.
