On November 22, Swift finally pulls the plug on legacy MT payment messages. Two decades after ISO 20022 was born, cross-border payments are being forced to speak its language for real.
When Swift switches off its old MT formats for cross-border payment instructions on November 22, nothing on a consumer banking app will look different. Cards will still tap, salary payments will still land, and merchants will still see settlements arrive.
Behind the interface, though, a generational change in the language of payments reaches a hard deadline. The coexistence period for Swift’s Cross-Border Payments and Reporting Plus (CBPR+) programme ends, and payment instructions such as MT103 and MT202 are formally retired in favour of their ISO 20022 equivalents.
It is a moment that has been two decades in the making.
Twenty years to overnight change
ISO 20022 is not a shiny new innovation. The International Organisation for Standardisation first published the standard in 2004, with the aim of creating a common, data-rich language for financial messaging.Within a few years it had been adopted as the basis for SEPA credit transfers and direct debits, gradually replacing a patchwork of domestic European formats.
Over the 2010s, ISO 20022 moved from theory to infrastructure. Real-time payment schemes, high-value RTGS systems and market infrastructures from Europe to Asia began to converge on the standard. By the time the Swift community launched its CBPR+ programme, ISO 20022 was already embedded in many domestic rails; cross-border payments were late to the party.
The decision to end coexistence in November 2025, reconfirmed by the Swift Board in 2024, was designed to force a final break with the MT era for cross-border payment instructions. After years of “prepare now” messaging, the industry has run out of runway.
The coexistence years and the rise of the quick fix
The path to this weekend’s deadline has not been linear. Coexistence only started in March 2023, following an earlier delay, and Swift offered in-flow translation services precisely because it knew not every institution could modernise core systems at the same pace.
That safety net arguably shaped behaviour. Rather than re-architecting systems around native ISO 20022 messages, many institutions leaned heavily on conversion layers to translate between MT and MX. It kept projects on track and bought time.
For Nick Fernando, Director and Co-founder of Aqua Global, that era is coming to a close. “Many banks have relied on quick-fix translation tools to bridge the gap – but these require constant upkeep and strip out much of the rich, structured data ISO 20022 enables,” he says.
Swift’s roadmap tightens data validation requirements over the next few years, particularly around how parties and addresses are structured in CBPR+ messages, and that creates friction for any institution that still thinks in MT.
“Banks that stick with them risk failed validations and rejected payments,” Fernando warns.
From deadline to data: what the next phase looks like
If the end of coexistence is one line in the sand, the next is already visible. Swift has set out a sequence of milestones that go beyond pure payment instructions, covering reporting and a wide range of non-instruction messages. Retirement dates are now defined for almost all MT categories.
“Coexistence is ending, but this is only the end of the beginning,” says Pratiksha Pathak, Head of Payments at RedCompass Labs. “A new wave of deadlines is approaching. SWIFT has released a comprehensive roadmap that goes beyond payment instructions and E&I, setting retirement dates for nearly all remaining non-instruction message types.”
The most immediate pressure point is the move to structured and hybrid addresses. The clock is already ticking on unstructured address fields, which will no longer be accepted after November 2026.
“Banks now have one year to prepare for structured or hybrid addresses,” Pathak notes. “After November 2026, unstructured addresses will no longer be accepted. This means upgrading core systems, cleansing customer data, addressing AML and sanctions screening, and onboarding systems. You must also ensure your systems can accept and validate hybrid address messages from counterparties—because those will start arriving immediately.”
For institutions serving high-risk sectors such as online gambling, crypto or high-chargeback e-commerce, the consequences land quickly. Richer, structured data is exactly what regulators and scheme operators have been asking for in AML, sanctions and fraud controls. Weaknesses in address data or party information that could previously be glossed over in free-text fields will be much harder to ignore.
“With retirement dates now defined for almost all MT message types, the margin for delay is shrinking,” says Pathak. “Success depends on early engagement with counterparties, as many transitions rely on bilateral agreements rather than enforced network changes. If you haven’t started yet, you’re already behind.”
Barclays and the rulebook approach
If the end of MT feels abstract, Barclays’ migration experience shows how concrete and contractual the work can be.
For corporates, the MT101 message became a central tool for consolidating payment initiation through a single bank. As those flows move to ISO 20022, Barclays has been transitioning clients to pain.001 messages on Swift’s FINplus ISO 20022 service, with the aim that this structural change in plumbing is almost invisible at the front end.
“Our overriding principle for us is that when we switch these flows to pain.001 we do so in a way that is seamless for our clients,” says Barry Trowbridge, VP – Digital Banking, Global Transaction Banking at Barclays.
The real complexity has been in the legal foundations. MT-era bilateral agreements were never designed to cover ISO 20022-based Payment Initiation Relay flows. Re-papering such agreements one by one would be a long and messy job.
In response, Barclays has worked with Swift and other institutions on a new Request for Transfer Rulebook that sets out roles, responsibilities and liabilities for ISO 20022-based flows. Trowbridge describes it as a way to align legal language with the new technical reality.
“Barclays recently became the first institution to sign up to the new rulebook,” he says. “Our motivation for this is very simple—the rulebook facilitates standardisation and efficiency.”
Instead of renegotiating individual MT-era contracts, the rulebook offers a shared framework for exchanging pain.001 messages, reducing complexity and promoting consistency. It also centralises contract management under Swift, moving away from “paper or PDF” agreements towards something closer to digital infrastructure.
For Barclays, that sits comfortably with a broader simplification agenda. “The introduction of ISO 20022 and the new rulebook allows us to reduce complexity whilst also promoting consistency across the industry,” Trowbridge adds.
Monetising a richer language
Underneath the deadlines, ISO 20022 is a data story. Its messages are designed to carry more structured, granular information about each transaction: who is paying whom, for what, and under which conditions.
Fernando frames native adoption as a way to make that promise real. It “unlocks richer, more structured data that drives faster straight-through processing, reduces errors, and strengthens end-to-end controls,” he argues. That combination is attractive in any vertical; in industries such as iGaming, where payment journeys and regulatory obligations are under scrutiny, it becomes critical to the business model.
Rossana Thomas, vice president and head of payment solutions at Fiserv, pushes the point further. For her, the post-ISO landscape is not only about risk and efficiency, but also about product design.
“ISO 20022 is a necessary standard to streamline communication across financial sectors – while some may view this as a compliance obstacle, it ought to be seen as an impactful opportunity for innovation and growth,” she says.
Thomas points to operational gains – “improved automation, reduced manual processing, and better data quality” – and to enhanced reconciliation, reporting and compliance. But she also sees scope for new services built on top of the richer message set, from advanced remittance data to real-time compliance enhancements.
“Financial institutions could also package value-added services like these into subscription- or usage-based offerings, including reconciliation-as-a-service, instant compliance checks or cash forecasting platforms,” she suggests. In that framing, ISO 20022 is less an obligation and more a platform for recurring revenue.
Whether the industry takes that step at scale remains to be seen, but the building blocks are arriving regardless. With the translation crutch removed for cross-border payments, institutions now have to live in the ISO 20022 world they have been talking about for twenty years.
