01What actually changed

On 22 November 2025, SWIFT's coexistence period for core cross-border interbank payment messages ended. Legacy MT102, MT103, MT201, and MT203 messages — the formats that have carried the bulk of cross-border FI-to-FI payment traffic since the 1970s — are no longer delivered over FIN between financial institutions. That traffic now moves natively as ISO 20022's MX message equivalents. Institutions still sending MT format face automatic conversion to MX by SWIFT, with additional charges from January 2026 — a deliberate incentive to finish migrating rather than lean on the conversion layer indefinitely.

Further deadlines run through November 2026: enforcement of structured (rather than free-text) address fields, and migration of MT101 payment-initiation traffic to its pain.001 MX equivalent via FINplus. But the core cross-border payment migration — the part that touches the largest volume of transactions — is done.

02The timeline

  • 2023–Nov 2025: Coexistence period — MT and MX both accepted for core cross-border FI payments.
  • 22 Nov 2025: Coexistence ends. MT102/103/201/203 no longer delivered over FIN between institutions; core traffic is natively ISO 20022.
  • 1 Jan 2026: Additional charges apply to MT traffic SWIFT auto-converts to MX.
  • Nov 2026: Structured-address enforcement; MT101→pain.001 migration deadline via FINplus.

03What ISO 20022 actually is

ISO 20022 is a messaging standard — a much richer, structured data model for describing a financial transaction than the legacy MT format allowed. It carries fuller remittance information, structured (not free-text) party and address fields, and more precise identifiers. That richer data materially helps compliance screening, reconciliation, and straight-through processing. It is, unambiguously, an upgrade to how a payment is described.

04What it doesn't fix

ISO 20022 is a message format, not a settlement mechanism. A payment message can now carry perfect, structured data end to end and still take three to five days to settle, because the underlying value still moves through the same correspondent chain, the same pre-funded nostro/vostro accounts, and the same intermediary banks it always did. Better data about a slow payment is still a slow payment.

This is also why "we're ISO 20022-native" isn't a meaningful differentiator on its own for interoperability infrastructure by 2026 — the entire correspondent banking network is now ISO 20022-native. It's table stakes, not a solution to the settlement problem.

05The gap this leaves open

What ISO 20022's completed migration actually clarifies is where the real unsolved problem sits: not in how a cross-border payment is described, but in how it settles — and specifically, in whether it can settle natively in a central bank's own digital currency instead of through a correspondent chain denominated in a third currency. That's the settlement-layer gap Recryp is built to close, using the same ISO 20022 standard at the message layer rather than inventing a competing one. See how this plays out for commercial banks and PSPs specifically, who are furthest along in the messaging migration and most exposed to the settlement gap it leaves behind.

Recryp is not affiliated with SWIFT. This explainer draws on SWIFT's public ISO 20022 migration documentation, cited as market context.