ISO 20022

ISO 20022 is the data dictionary and messaging framework that underpins modern payment infrastructure. Where legacy SWIFT MT messages used fixed-length, unstructured text fields, ISO 20022 uses XML with defined data types — structured BIC addresses, ISO country codes, LEI identifiers, and multi-line remittance information that bank systems can parse rather than read. The difference matters operationally: a pacs.008 message can carry all the data a beneficiary bank needs for straight-through processing; an MT103 often cannot.

The Three Message Families Operators Meet

ISO 20022 spans dozens of business domains, but payment operators regularly encounter three families:

pacs — Payments Clearing and Settlement. The interbank layer. pacs.008 is the ISO 20022 equivalent of the MT103 customer credit transfer; pacs.002 carries the status response (accepted or rejected); pacs.004 handles returns. When your bank sends or receives a cross-border payment under CBPR+ or a SEPA instant transfer, it is exchanging pacs messages with counterparty banks.

camt — Cash Management. The reporting and investigation layer. camt.052 (intraday statement), camt.053 (end-of-day statement), and camt.054 (debit/credit notification) replaced MT940/MT950/MT900/MT910 for account reporting. camt.056 initiates a payment recall; camt.029 carries the negative recall response. If your bank API changed the shape of your account statements, it migrated from MT to camt.

pain — Payment Initiation. The corporate-to-bank layer. pain.001 is the customer credit transfer initiation (what your treasury or ERP system sends to your bank); pain.002 is the bank’s status response back to you. The ISO 20022 migration that affected correspondent banking also touched the pain messages your bank’s corporate portal or API exposes.

Where ISO 20022 Is Live

SWIFT cross-border (CBPR+): SWIFT mandated all cross-border payment and cash management messages migrate to ISO 20022 under CBPR+ usage guidelines. MT coexistence ended 22 November 2025; the network is now ISO 20022 for these flows. See the SWIFT payment processing guide for the MT-to-MX transition detail.

SEPA: All SEPA schemes (SCT, SCT Inst, SDD) have used ISO 20022 pacs and camt messages since inception. SEPA is the oldest large-scale ISO 20022 deployment in production.

Modern RTGS and instant rails: TARGET2 (the Eurosystem RTGS) migrated to ISO 20022 in November 2022. CHAPS (UK sterling) migrated in 2023. TIPS and RT1 (European instant payment CSMs) use pacs.008/pacs.002 natively. Fedwire completed its single-day ISO 20022 cutover on 14 July 2025, rescheduled from the original March 2025 date.

What Changed for Operators

Statement shape: If your bank account statements or API webhooks changed field names and structure in 2023–2025, you were on the receiving end of an MT-to-camt migration. Structured creditor/debtor addresses now appear as proper nested objects, not free-text lines.

Richer remittance data: ISO 20022 supports structured remittance information (invoice references, end-to-end IDs, purpose codes) that MT103 truncated or dropped. Operators expecting those references in reconciliation feeds need banks and counterparties that pass the data through without truncating it — which the CBPR+ guidelines constrain further.

UETR tracking: Every ISO 20022 pacs.008 carries a UETR — the end-to-end UUID that enables GPI payment tracking across every correspondent hop. The UETR survived MT coexistence (it was back-ported to block 3 of MT103 during the migration window) and is now native to the MX message structure.

Investigations via camt: The payment investigation workflow — status queries, recalls, returns — is now structured camt messaging rather than free-text SWIFT fin messages. If your treasury sends payment enquiries to your bank, that workflow is camt.028 (status request) and camt.056 (recall request) rather than phone and email.