All Tools
Tools/ISO 20022 Message Reference
🌐
MessagingAvailable
ISO 20022 Message Reference
Searchable reference of the CBPR+ / HVPS+ ISO 20022 payment messages — pacs, pain, camt — with MT equivalents, key elements, and the current structured-address / native-MX migration status per rail. Open any message for a full detail page.
Follows ISO 20022 CBPR+ / HVPS+ usage guidelinesSR2025 message versions·verified Sep 2026— migration dates tracked in the status table on the page
Migration status by railverified 2026-09-04
The single 14 November 2026 cutover — unstructured postal addresses rejected, Business Application Header validation hardened, camt.110 / camt.111 receipt mandatory — has fragmented. The rules are unchanged; the enforcement dates now differ by rail.
| Rail | Change | Status | Note |
|---|---|---|---|
| Swift (MT → MX coexistence) | End of MT/MX coexistence for CBPR+ payment messages | Live since 22 Nov 2025 | More than 98% of payment instructions on the network are now sent as ISO 20022. Swift ↗ |
| Swift CBPR+ (SR2026) | Fully unstructured postal addresses rejected — structured or hybrid only; plus the other SR2026 payments changes | Deferred — new date by Dec 2026 | On 27 Aug 2026 Swift accepted a community request for more time and deferred all SR2026 payments changes; it will consult and announce timing by December. Non-payments SR2026 items (e.g. T+1 support) are decoupled and go live in Q1 2027. Swift notice ↗ |
| Fedwire Funds Service | Structured / hybrid postal address requirement and retirement of fully unstructured addresses | November 2027 | The November 2026 release was rescheduled to November 2027 on 27 Aug 2026; release scope is due in autumn 2026. Fedwire itself has run natively on ISO 20022 since 14 Jul 2025. FRB Services ↗ |
| SEPA — EPC schemes (SCT, SCT Inst) | End-date of the unstructured address format in EPC scheme transactions | 15 Nov 2026 — pending EPC decision of 9 Sep 2026 | The EPC says its timeline stands until further notice and that the Payment Scheme Management Board will decide on 9 September 2026 in light of the Swift extension. EPC notice ↗ |
| CHIPS | ISO 20022 native since April 2024; US-market address structuring | Follow The Clearing House guidance | CHIPS completed its ISO 20022 migration in April 2024. Its structured-address timing was aligned with Fedwire; confirm with The Clearing House now that Fedwire has moved to November 2027. |
Structured or hybrid addresses (at minimum town name + country code) remain the target on every rail — Swift reported over 60% of traffic still unstructured in April 2026. Messages marked "Milestone" below are the ones these rules touch.
15 of 15 messages
| Message | Name | MT equivalent | Purpose | |
|---|---|---|---|---|
| head.001 | Business Application Header (BAH) Milestone | FIN Basic Header / Application Header (blocks 1–3) | Envelope that travels with every business message — sender, receiver, message definition, business service, and creation date. | detail → |
| pacs.008 | FI to FI Customer Credit Transfer Milestone | MT 103 | The workhorse customer payment — moves a credit transfer between financial institutions on behalf of customers. | detail → |
| pacs.009 | FI Credit Transfer | MT 202, MT 202 COV | Bank-to-bank credit transfer — liquidity moves, settlement obligations, and the COV variant covering an underlying customer payment. | detail → |
| pacs.002 | FI to FI Payment Status Report | MT 199 (by convention), ACK/NAK | Positive/negative status of a previously received payment — accepted, rejected, pending — with reason codes. | detail → |
| pacs.004 | Payment Return | MT 103 RETN, MT 202 RETN | Returns previously settled funds to the sender, with a structured return reason. | detail → |
| pain.001 | Customer Credit Transfer Initiation | MT 101 | Corporate-to-bank payment initiation — a customer instructs its bank to execute credit transfers. | detail → |
| pain.002 | Customer Payment Status Report | — | Bank-to-corporate status of an initiated payment file or individual transaction. | detail → |
| pain.008 | Customer Direct Debit Initiation | — | Creditor instructs its bank to collect funds via direct debit (SEPA SDD Core / B2B). | detail → |
| camt.052 | Bank to Customer Account Report | MT 941, MT 942 | Intraday account report — balances and entries since the last statement. | detail → |
| camt.053 | Bank to Customer Statement | MT 940, MT 950 | End-of-day account statement with opening/closing balances and full entry detail. | detail → |
| camt.054 | Bank to Customer Debit/Credit Notification | MT 900, MT 910 | Real-time notification that an account was debited or credited. | detail → |
| camt.056 | FI to FI Payment Cancellation Request | MT 192, MT 292 | Request to cancel or recall a previously sent payment. | detail → |
| camt.029 | Resolution of Investigation | MT 196, MT 296 | Answers a cancellation request or investigation — accepted, rejected, or pending. | detail → |
| camt.110 | Investigation Request Milestone | MT 195, MT 199 (investigations) | Structured enquiry about a payment — request for information, claim of non-receipt, value-date correction, and more. | detail → |
| camt.111 | Investigation Response Milestone | MT 196, MT 199 (investigations) | Structured answer to a camt.110 investigation request. | detail → |
Message areas
pacs — Payments Clearing & Settlement: the interbank leg (pacs.008 ≈ MT 103, pacs.009 ≈ MT 202).
pain — Payment Initiation: corporate ↔ bank instructions (pain.001 ≈ MT 101).
camt — Cash Management: reporting, statements, cancellations, investigations (camt.053 ≈ MT 940).
head — Business Application Header: the envelope on every message.