For decades cross-border payments spoke SWIFT MT. ISO 20022 (MX) replaces it with richer, structured data — and the cross-border coexistence period ended on 22 November 2025. This is the plumbing change that quietly touches almost everything.
ISO 20022 is an open international standard for financial messaging — an XML-based, structured, data-rich format meant to replace the terse, ageing message types that have carried payments for decades. In the cross-border world it replaces SWIFT's MT messages with MX (ISO 20022) messages. The point is not novelty for its own sake: structured data means cleaner straight-through processing, better screening, richer remittance information, and fewer truncated-field errors.
This is plumbing, and plumbing changes are easy to under-rate. But because almost every downstream system — sanctions screening, reconciliation, reporting, fraud models — consumes payment messages, switching the message format touches an enormous surface area inside every institution that handles cross-border money.
CBPR+ is the market-practice usage guideline for ISO 20022 on SWIFT — the cross-border rulebook for MX.
MT/MX ran in parallel from March 2023; on 22 November 2025 SWIFT retired general use of in-scope FIN/MT payment messages.
Contingency and in-flow translation became chargeable from 1 January 2026 — an incentive to be natively MX.
T2, CHAPS, Fedwire and peers each moved to ISO 20022 on their own schedules — not one global flip.
For cross-border payments over SWIFT, the migration is governed by CBPR+ (Cross-Border Payments and Reporting Plus) — the market practice guidelines for how ISO 20022 is used on the SWIFT network. The industry transition started in March 2023 with a coexistence period: MT and MX ran in parallel, with translation available, so institutions could migrate at their own pace.
That coexistence period ended on 22 November 2025. From that date, in-scope cross-border payment instructions are exchanged in ISO 20022 MX over SWIFT's FINplus service; general usage of the equivalent FIN/MT payment messages was retired. Institutions still relying on translation or contingency processing face additional cost as of January 2026. In parallel, the major high-value RTGS systems — the Eurosystem's T2, the UK's CHAPS, the US Fedwire and others — have migrated to ISO 20022 on their own timelines.
Sending MX-rich data into a system that still thinks in MT loses structure. "ISO-native" end to end is the goal; partial migration creates fragile seams.
Sanctions and AML screening must be re-tuned to structured party data — otherwise you get more false positives, or worse, miss-hits.
Carrying MX is not the same as using it. Many institutions migrated the message but not the data quality — the value is in structured, complete data.
Every system that reads payment messages — reporting, recon, analytics — inherits the new structure. The migration is never "just messaging".
If you are an institution that sends cross-border payments, the in-scope deadline has passed — the question now is whether you are genuinely ISO-native or quietly leaning on translation and contingency (which now costs money and signals incomplete migration). The honest internal audit is: are we carrying MX, or are we actually using the structured data end to end? Most of the lasting value — better STP, better screening, richer remittance — only lands if the answer is the latter.
If you are a fintech or PSP, ISO 20022 is increasingly the table-stakes interface for the whole ecosystem — instant rails like sarie and Aani were born on it, RTGS systems run on it, cross-border runs on it. Build native; do not architect around translation layers you will pay to keep.
The strategic read: this migration is the data foundation under the G20's cross-border ambitions and under the CPMI's harmonisation work. The institutions that treated it as a compliance checkbox got a more expensive version of the same messages. The ones that treated it as a data upgrade got cleaner processing and a head start on everything built on top.