The Complete SWIFT ISO 20022 Migration Timeline

After 22 November 2025, the MT/ISO 20022 coexistence period ended, and all cross-border payment instructions exchanged between financial institutions must be sent in ISO 20022. SWIFT, which went live in 1977, had carried those payments in its legacy MT format for decades. Some MT payment messages are now rejected outright. Others are converted to ISO 20022 by a chargeable contingency service. The details are below.

That date was supposed to be the big one. It wasn't. It was the middle of a longer migration: the ISO 20022 standard dates to 2004, the SWIFT community decided in 2018 to adopt it, and SWIFT's own roadmap, published in November 2025 before the 2026 postponement, runs to November 2028 for statements and reporting. The real timeline is longer, messier, and more consequential for crypto investors than a single cutover date suggests.

We track the 8 coins most often linked to ISO 20022 on WM589. Every milestone in this timeline creates a new integration opportunity, or a new pressure point, for those projects. Here is the roadmap, with specific dates, sources, and what each phase means for the coins in your portfolio. Dates after August 2026 are provisional, because SWIFT is still working out a revised timetable.

The full timeline

2004: ISO 20022 is developed

The International Organization for Standardization published ISO 20022 as a universal financial messaging standard. The Bank of Japan's payments research dates its development to 2004. The idea was simple: replace dozens of incompatible formats with one rich, structured data model that could carry detailed payment information.

Adoption came first in domestic and regional payment systems. The Bank of Japan notes that the standard has been introduced in payment systems in major Western countries since its establishment in 2004. Cross-border payments over SWIFT stayed on the MT format until the community made its decision, described next.

Crypto relevance: None at this point. Bitcoin did not exist yet. But the decision to build a universal financial data standard would later become the on-ramp for blockchain interoperability.

2018: The SWIFT community decides to migrate

According to SWIFT's own FAQ, the SWIFT community decided in 2018 to adopt ISO 20022 for cross-border payments and reporting, and financial institutions gave SWIFT the mandate to facilitate the move. The scope was enormous: the cross-border payment and cash-reporting messages that run over SWIFT's network.

Crypto relevance: Crypto projects that pitch cross-border payments now had a concrete reason to care about ISO 20022, because the messaging format of the network they wanted to complement or compete with was going to change. Whether that helps any token is a separate question. The standard is a messaging format. It does not certify or favor any coin.

March 2023: CBPR+ goes live, coexistence begins

SWIFT's published timeline set March 2023 as general availability for ISO 20022 messages in its Cross-Border Payments and Reporting Plus (CBPR+) service, followed by a coexistence period that ran from March 2023 to November 2025. From March 2023, any bank could send MX (ISO 20022) messages independently of its correspondent's preferred channel, while banks that were not ready could rely on SWIFT's central in-flow translation service.

Crypto relevance: The coexistence period created a two-track system. Banks that modernized early gained access to richer data. Projects like XDC and Quant, which pitch themselves as bridges between legacy and modern financial systems, could point to an active migration as context for that pitch. Ripple has also held a seat on the ISO 20022 Registration Management Group (RMG) since 2020, which is a governance seat on the standard's maintenance body and not a certification of XRP.

July 14, 2025: Fedwire migrates

The Federal Reserve moved the Fedwire Funds Service to the ISO 20022 message format on July 14, 2025, and confirmed on June 18, 2025 that it would proceed on that date as planned. It was a single-day cutover from the legacy FAIM format, not a gradual phase-in (The Paypers).

The Fedwire Funds Service is the backbone of high-value domestic transfers in the United States. According to Federal Reserve Financial Services statistics, it averaged about $4.6 trillion in transfers per day in 2025. The migration had been scheduled for March 10, 2025 and was postponed to July 14 after the Federal Reserve evaluated customer readiness and industry requests (The Paypers).

Crypto relevance: ISO 20022 is now the message format on the highest-value U.S. payment rail. That removed the argument that ISO 20022 was "just a European thing" and lowers one technical barrier for blockchain-to-bank data exchange. It does not by itself connect any blockchain to Fedwire. Check our pillar guide on ISO 20022 for the full technical breakdown.

November 22, 2025: SWIFT CBPR+ coexistence ends

The coexistence period for cross-border payment instructions ended. SWIFT's end-of-coexistence guide sets out what that meant in practice. MT 102, MT 102 STP, MT 103 REMIT, MT 201 and MT 203 are rejected (NAK'd) immediately. MT 103, MT 103 STP, MT 200, MT 202, MT 202 COV, MT 205 and MT 205 COV that pass additional validation are converted to ISO 20022 by SWIFT's contingency service, at additional cost. Banks that had not migrated were not simply cut off, but they pay for the fallback and receive messages in a converted form.

In its August 2026 postponement notice, SWIFT said that more than 98% of payment instructions are now sent in the ISO 20022 format. For comparison, SWIFT's data for the week of November 3 to 9, 2025, ten days before the cutover, showed 75.8% of payment instruction traffic already on ISO 20022, with 200+ countries sending and 220+ countries receiving ISO 20022 messages on the FINplus service.

One important nuance: the cutover applied to payment instructions. SWIFT said in 2024 that other message types in scope, including reporting and statements, would not be withdrawn from the FIN service in November 2025. They are deprecated, and disincentives would come later. Messages outside the payments scope, such as securities and trade, were not part of this cutover either. SWIFT's deferred Standards Release 2026 still covers changes to all MT messages other than Category 1 payments, per J.P. Morgan's ISO 20022 guide.

Crypto relevance: Cross-border bank payments are now overwhelmingly in a format that crypto projects describing ISO 20022 support can map to. That lowers one technical barrier between traditional finance messaging and blockchain messaging. It does not create demand for any particular coin, and no bank is required to use one.

January 1, 2026: SWIFT starts charging for legacy MT usage

Contingency processing and in-flow translation became chargeable from January 1, 2026. Banks still sending MT payment instructions through those services pay additional charges. According to SWIFT's guide, the charges are not included in Fixed Fee or Swift Essentials tariffs and will be reviewed at regular intervals.

Crypto relevance: This is an adoption incentive. Banks that dragged their feet through 2025 now face direct fees. Every bank that upgrades is another institution speaking the data language that ISO 20022 crypto infrastructure targets. The shrinking pool of legacy holdouts reduces friction for blockchain-to-bank integration, though we have no measure of how much.

August 27, 2026: SWIFT postpones the structured address mandate

The structured-address mandate was originally set to take effect in November 2026. SWIFT's guidance said that after 14 November 2026 unstructured postal addresses would be removed and only fully structured or hybrid addresses accepted, ending the one-year grace period that opened with the November 2025 cutover. That did not happen on schedule. The Bank of England confirmed that on 27 August 2026 SWIFT announced its decision to delay the November 2026 Standards Release. In that notice, SWIFT accepted a community request to extend the timeline and deferred all payments changes. The MT 101 retirement, also planned for November 2026, was extended too.

The readiness data explains why. SWIFT's own April 2026 data showed that 61.2% of payments included unstructured debtor postal addresses. A RedCompass Labs survey found 44% of banks behind schedule, and RedCompass attributes the postponement to the volume of work: too many addresses to convert, too many defects to clear and not enough capacity.

This matters because the work does not go away. Banks still must cleanse customer data, upgrade core systems, and fix AML/sanctions screening workflows before whatever new deadline lands.

What is known about the new timing comes from SWIFT and the banks that publish its guidance. SWIFT said it would provide an update by December on the structured-address requirement. J.P. Morgan's guide says the payments changes move to a future Standards Release, and that unstructured addresses and MT 101 may continue to be used until at least November 2027. Separately, SWIFT decoupled the non-payments part of Standards Release 2026 (securities, trade, funds, tracker and exceptions and investigations messages, including the mandate to receive camt.110 investigation requests). SWIFT's notice originally gave Q1 2027, and the go-live date for that separate release has since been set at June 12, 2027. For the full breakdown of what changed and why, see our dedicated analysis of the postponement.

The postponement rippled outward. The Bank of England deferred its November 2026 RTGS standards release in its entirety. RedCompass reports that Federal Reserve Financial Services said it would reschedule its November 2026 Fedwire release to November 2027.

Crypto relevance: The structured data mandate is about data quality, which can benefit blockchain projects, but the enforcement wave that would have tested it has moved out with no new date. Richer, more structured payment data makes it easier to build automated compliance, smart contract triggers, and cross-system reconciliation. Projects like Quant (Overledger) and XDC (trade finance) that pitch themselves at the interoperability layer may benefit from higher-quality data, whenever that mandate lands.

Late 2026: J.P. Morgan rolls out camt.052/053/054

J.P. Morgan says that by late 2026 it will gradually start offering ISO 20022 (MX) reporting and cash management messages. The commonly used reporting messages are moving from MT to camt formats: MT941/MT942 to camt.052 (account report), MT940/MT950 to camt.053 (statement), and MT900/MT910 to camt.054 (debit/credit notification).

This matters because reporting messages carry detailed transaction data. The shift from MT9xx statements to camt messages means richer, structured information about every payment. J.P. Morgan's rollout signals that large banks are moving beyond sending ISO 20022 payments to adopting the format for account reporting.

SWIFT's roadmap lists November 2028 as the end-of-life date for MT statement and reporting messages, giving banks more runway. J.P. Morgan's guide says it will keep accepting MT210 messages until 2028.

Crypto relevance: When large banks start producing structured reporting data, the interoperability surface for blockchain projects can expand. Tokenized asset settlement, real-world asset (RWA) tracking, and automated treasury management all become more practical when the underlying bank data is structured. Whether any coin benefits is a separate question that depends on documented integrations. See individual coin pages on our coins hub at /coins for project-specific analysis.

November 2027 and November 2028: more MT messages reach end of life

SWIFT's roadmap, published in November 2025 before the postponement, listed end-of-life (rejection) dates for the messages that follow payment instructions. In November 2027: exceptions and investigations messages (MT 195/295, 196/296, 199/299/999, 198/298/998, 995 and 996, replaced by camt.110 and camt.111) and payment cancellation messages (MT 192/292, replaced by camt.056 and camt.029). In November 2028: statements and reporting messages (camt.052, camt.053 and camt.054 replace MT 900, 910, 940, 941, 942 and 950), direct debits (MT 104, MT 107 and MT 204, replaced by pain.008, pacs.003 and pacs.010), and charges messages (MT 190, 191, 290, 291, 990 and 991, replaced by camt.105 and camt.106).

The same roadmap listed November 2026 for the MT 101 payment-initiation relay: MT 101 (multiple) removed and MT 101 (single) end of life. That is the date the August 2026 postponement moved. Because SWIFT also deferred exceptions-and-investigations changes, treat every date after August 2026 as provisional until SWIFT publishes its revised timetable.

Crypto relevance: Each end-of-life date removes a legacy fallback. For ISO 20022 crypto projects, that shifts "compatible" from a selling point toward a baseline for any project claiming financial infrastructure relevance. It does not guarantee that any bank will pick any specific network.

2028: the end of SWIFT's current roadmap

November 2028 is the last end-of-life date on SWIFT's current roadmap for the messages it covers. Outside SWIFT's network, the Financial Stability Board's 2023 G20 progress report said that more than 100 jurisdictions were already actively using ISO 20022 messages.

Crypto relevance: Even on the current roadmap, the picture in 2028 will be mixed, because the roadmap covers CBPR+ payments and reporting messages and not every message type in every market. Our coin profiles found a sourced ISO 20022 messaging product or membership for only a few of the 8 coins we track, so we do not assume any of them has an integration head start, and ISO 20022 by itself does not create demand for any coin. Use the WM589 forecast engine at /forecasts to model scenarios, and treat adoption timelines as inputs with wide error bars.

Why banks are still dragging their feet

The 98%+ headline (source: swift.com) is a share of payment instructions, not a share of institutions. It obscures a messier reality in the data SWIFT publishes. In the week of November 3 to 9, 2025, SWIFT counted 4,700+ BIC8s sending and 6,300+ BIC8s receiving ISO 20022 messages on FINplus, and by April 2026 more than 61% of payments still carried unstructured debtor addresses.

RedCompass Labs puts the reason for the August 2026 postponement in simple terms: too many addresses to convert, too many defects to clear and not enough capacity to carry out the work. Many banks relied on SWIFT's automatic translation layer during coexistence, which gave them ISO 20022 output without upgrading their internal systems.

That workaround is now expensive. SWIFT charges for contingency translation. And SWIFT itself notes that data can be lost or truncated when a message that originates in ISO 20022 is converted to the less rich MT standard. Banks using translation may be compliant on paper but degraded in practice.

The structured address mandate, now postponed from November 2026 to a future release, will eventually force another wave of actual upgrades. SWIFT's guidance is that there is no SWIFT contingency measure for messages that do not carry structured or hybrid addresses once the requirement applies, so banks cannot fake their way through address data cleansing forever, even if SWIFT just gave them more runway to try.

For crypto investors, the lag matters because blockchain-to-bank integration is only as good as the weakest link. A payments corridor where one side runs genuine ISO 20022 and the other uses a translated shim offers limited benefit. The full value unlocks when both sides are native.

The crypto opportunity in each phase

Phase 1 (2023-2025): Foundation laying. Coexistence period. Banks slowly migrate. Crypto projects build compatibility layers. Ripple sits on the ISO 20022 standards body (the RMG), and other networks build ISO 20022 compatibility layers. The narrative forms but real integration remains limited. This phase is done.

Phase 2 (2025-2026): Pressure builds. Fedwire and SWIFT coexistence end. Legacy fees kick in. The structured data mandate was due in November 2026 and has been postponed. The ECB's T2S change requests add token units to ISO 20022 reporting messages (CR-1374, planned for the June 2026 release). CBDC pilots expand (mBridge, Project Acacia). This is roughly where we are now. The infrastructure for crypto-bank interoperability exists technically. The question is which projects execute on it first.

Phase 3 (2027-2028): Legacy MT messages reach end of life. On SWIFT's roadmap, exceptions and investigations, direct debit, charges, and reporting messages reach end of life, though dates after August 2026 are provisional. CBDC and tokenization pilots mature at their own pace. This is the window where crypto projects linked to ISO 20022 either prove their institutional value or get left behind, but no source can tell us which.

Phase 4 (2029+): Digital assets as native instruments. If token and wallet fields keep being added to ISO 20022's maintenance cycle, digital assets could become first-class citizens in financial messaging. The ECB has said that if the digital euro regulation is adopted in 2026, the Eurosystem should be ready for a potential first issuance during 2029. The distinction between "crypto" and "financial infrastructure" might blur, or it might not.

The mistake many investors make is treating the SWIFT migration as a single event. It is a multi-year infrastructure shift. Each milestone creates a new opportunity window and a new set of winners and losers among the projects building on this standard.

Current adoption by the numbers

Here is where things stand on the latest published figures, each dated in the bullet:

More than 98% of SWIFT payment instructions are now sent in ISO 20022 format (SWIFT, August 2026 notice; source: swift.com)
75.8% of payment instruction traffic on ISO 20022, with 200+ sending and 220+ receiving countries on FINplus (SWIFT, week of November 3 to 9, 2025)
About $4.6 trillion per day average value on the Fedwire Funds Service in 2025, on ISO 20022 since July 14, 2025 (Federal Reserve Financial Services)
More than 100 jurisdictions actively using ISO 20022 messages (Financial Stability Board, October 2023)
61.2% of payments carrying unstructured debtor postal addresses (SWIFT, April 2026 data)
146 countries and currency unions exploring CBDCs, covering over 98% of global GDP (Atlantic Council, May 2026)
41 CBDC pilot projects worldwide (Atlantic Council, May 2026)
13 cross-border wholesale CBDC projects, more than double the number before Russia's 2022 invasion of Ukraine (Atlantic Council, May 2026)

These numbers tell a split story. By volume, the migration of payment instructions is nearly complete. By address quality and by the postponed mandates, there is still substantial work to do. Both realities matter for the ISO 20022 crypto thesis.

FAQ

Is the SWIFT migration actually done?

For payment instructions, yes. Since November 22, 2025, cross-border payment instructions between banks must be in ISO 20022 format, with a chargeable conversion fallback for some legacy messages. But SWIFT's roadmap runs to November 2028 for reporting messages, direct debits, and charges, and the wave planned for November 2026 (structured addresses and MT 101) was postponed with no new date. Message types outside the CBPR+ payments scope, including some in securities and trade, are still in MT format.

Why does the SWIFT migration matter for crypto?

ISO 20022 creates a universal data format for financial messages. Crypto projects that implement this format can map their data to the structured messages banks use. The standard reduces one technical barrier for blockchain-to-bank integration. It does not guarantee adoption, and it does not certify any coin.

Which ISO 20022 coins benefit most from each timeline phase?

No source ties any coin to a specific phase, and the standard is coin-neutral. The projects we track pitch different use cases: cross-border payments (XRP, XLM), interoperability middleware (QNT, XDC), and infrastructure or tokenization platforms (ALGO, HBAR, IOTA, ADA). Each may find some phases more relevant than others, but we do not claim any project will benefit, and none is required for a bank to be ISO 20022 compliant.

What happens to banks that do not migrate by the deadlines?

SWIFT charges additional fees for contingency processing and translation services. Some legacy messages, such as MT 102 and MT 203, are rejected outright. Once the postponed structured-address mandate takes effect, SWIFT says there is no contingency measure for non-compliant messages, so payments that lack structured or hybrid addresses may be rejected or delayed. Banks that rely on translation get converted output but can lose data richness.

Could the timeline slip again?

It already has, repeatedly, and on the largest scale yet in August 2026. Fedwire was postponed from March to July 2025. SWIFT did not withdraw non-instruction messages in November 2025 and later listed November 2027 and November 2028 end-of-life dates. Then, on August 27, 2026, SWIFT itself postponed the structured-address mandate and MT 101 retirement, both originally set for November 2026, after readiness data showed 61.2% of payments still carried unstructured debtor addresses. SWIFT expects to update the timeline by December 2026, and J.P. Morgan says unstructured addresses and MT 101 may keep working until at least November 2027. The core payment instruction migration did hold to its November 2025 deadline. Treat every later date on this page as real but not immune to another slip if industry readiness lags again.

Sources

Disclaimer: This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments carry significant risk, including the potential loss of all invested capital. The mention of specific projects, banks, or timelines does not represent an endorsement or guarantee of future outcomes. Always conduct your own research and consult a qualified financial advisor before making investment decisions. When Moon 589 tracks the coins most often linked to ISO 20022 but makes no guarantees about future performance or adoption.