SWIFT Postpones ISO 20022 Address Deadline

November 2026 is no longer the date to watch. On August 27, 2026, SWIFT postponed the structured-address mandate and the MT 101 (an older SWIFT message type banks use to send payment instructions) retirement, both originally scheduled for that month, and no new date has been set for them. If you have been tracking the ISO 20022 story through this site's deadline page or timeline tracker, here is exactly what changed, what did not, and what it actually means for the coins in this basket.

What SWIFT actually announced

The Bank of England's statement dates the announcement: on 27 August 2026, SWIFT announced its decision to delay the November 2026 Standards Release after the industry asked for more time to prepare for the removal of unstructured postal addresses. In its notice, SWIFT accepted the community request for an extension. The reason was readiness, not politics. SWIFT's own April 2026 data showed that 61.2% of payments still included unstructured debtor postal addresses. A RedCompass Labs survey found 44% of banks behind schedule, and one in five of the largest banks (assets of $250 billion or more) called the original deadline unrealistic.

Crowdfund Insider and Projective Group report the same facts.

Two separate things were affected, and they now sit on two separate tracks:

• The payments track: structured addresses and MT 101 retirement. SWIFT deferred all payments changes. RedCompass reports that MT Category 1 (SWIFT's customer-payments message group), CBPR+, SCORE+ and SwiftGo changes, including the removal of unstructured postal addresses, were lifted out of Standards Release 2026 (SWIFT's annual rulebook update) entirely. SWIFT says it will provide an update on the structured-address requirement "by December, at the latest." In the meantime, unstructured addresses and MT 101 may keep working until at least November 2027, per J.P. Morgan's ISO 20022 migration guide.
• The non-payments track: everything else in the deferred release. SWIFT's notice said these changes, which include the move to T+1 settlement in some markets, would be decoupled from the payments changes and go live in Q1 2027, with an exact date to follow. The go-live date for this separate release has since been set at June 12, 2027. According to J.P. Morgan's guide, its scope is all MT messages excluding Category 1 payments, plus ISO 20022 funds, securities, tracker, and exceptions and investigations messages. The exceptions and investigations changes include the mandate to receive camt.110 (an ISO 20022 message banks use to investigate a payment problem), which J.P. Morgan places in this deferred partial release.

It would be easy to mistake that second date for the new ISO 20022 deadline. It is real, but it is not the same deadline this site's countdown used to track.

Confusing the two matters. The structured-address mandate and MT 101 retirement are the changes this site's countdown tracked, and both still have no confirmed date. Catching that distinction takes reading the actual notice, not just a headline about it, which is exactly what you just did. See our full postponement breakdown for the complete timeline, sources, and what each track actually covers.

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

What did NOT change

Two things are easy to lose in the noise:

• The 2025 MX cutover already happened, on schedule. The MT/MX coexistence period ended after 22 November 2025, when SWIFT's end-of-coexistence guide says cross-border payment instructions between financial institutions must be exchanged in ISO 20022. Nothing about the August 2026 postponement touches this. If you have read anywhere that "SWIFT delayed ISO 20022," that is imprecise: SWIFT delayed one later enforcement wave, not the migration itself.
• ISO 20022 does not certify any cryptocurrency, and that has not changed either. ISO 20022 is a messaging standard banks use to format payment instructions to each other. The ISO 20022 site describes it as a methodology, a dictionary of business items and a set of design rules for building messages. It has no mechanism to approve, endorse, or "certify" a blockchain or a token. Ripple has held a seat on the standard's Registration Management Group (RMG) since 2020, which is a governance seat and not a certification of XRP. We could not confirm RMG membership for other networks on our tracker from a primary source, so treat claims that a specific coin is "on the standards body" as unverified unless the ISO 20022 member list shows it. Every listed coin is, at best, ISO 20022-*compatible* or *aligned*: built to carry or map to the same message formats banks use. A SWIFT internal deadline moving does not change that structural fact.

What it means for holders of XRP, XLM, and the rest

Short answer: nothing mechanical. Price is not a lever SWIFT's release calendar pulls. If a coin's thesis depends on "the November 2026 deadline forcing banks to adopt ISO 20022 rails, which somehow requires this token," that thesis was already doing more work than the standard supports. Postponement doesn't change that.

ISO 20022 adoption by banks is a real, ongoing infrastructure shift. SWIFT's own August 2026 notice states that more than 98% of payment instructions are now sent in the ISO 20022 format, but it is a data-formatting standard, not a settlement-asset mandate. No bank is required to use XRP, XLM, HBAR, or any other token to be ISO 20022 compliant. See our price-honesty section for the fuller version of this argument: the causal chain from "bank messaging standard" to "token price" has real breaks in it, deadline or no deadline.

What the delay does change is timing expectations for anyone using "the November 2026 deadline" as a near-term catalyst date. That date no longer applies to the structured-address/MT101 track. If you were holding a position specifically because of a calendar date, the calendar just moved, with no new date confirmed for that specific track.

Watch for: SWIFT's promised timetable update, due by December 2026, which should finally give the structured-address/MT101 track a real date. We will update this page and the deadline tracker the moment SWIFT does.

The IBM-SWIFT tokenized-deposit news, clarified

On September 24, 2026, IBM announced a beta in which IBM Digital Asset Haven clients can connect to Swift's blockchain-based shared ledger, using a new ISO 20022 Messaging Adapter to instruct tokenized deposit transactions with standard ISO 20022 messages. IBM's release also says Swift's ledger is being put to first use by 17 first-mover institutions piloting tokenized deposit transactions. The 17 institutions are piloting Swift's ledger, and IBM's connection is a separate beta offering.

Headlines that tie this to Stellar (XLM) are not supported by the source. We read the IBM release directly: it names Swift's own blockchain-based shared ledger as the network involved, and it does not mention Stellar or XLM anywhere. If a headline told you this was a Stellar partnership, that is the outlet's framing, not IBM's announcement.

Two dates, neither one a reason to trade

SWIFT postponed one enforcement wave (structured addresses, MT 101) and set a real date for a different one (June 12, 2027, non-payments track). Both are genuine facts from the sources below. Neither one is a reason to buy or sell anything.

If you are tracking ISO 20022 coins for the infrastructure story, the plain version is: the migration is real, it is slower than the original schedule, and it has never been a price mechanism by itself. Track the actual dates on our ISO 20022 timeline tool. If you want the deeper dive on why a bank messaging standard doesn't mechanically move token prices, our 589 theory breakdown covers the same honesty check for the most-hyped number in the space.

Sources

• SWIFT: notice accepting the community request to extend structured address migration
• SWIFT: Call-to-action for November 2026 (April 2026 unstructured address data)
• SWIFT: end of coexistence guide for financial institutions (PDF)
• Bank of England: delay to the November 2026 RTGS standards release
• J.P. Morgan: ISO 20022 migration guide
• RedCompass Labs: Swift delays ISO 20022 structured address deadline
• Projective Group: Swift revises the Standards Release 2026 timeline
• Crowdfund Insider: Swift extends deadline for structured addresses
• ISO 20022: about ISO 20022
• The Paypers: Ripple joins ISO 20022 standards body
• IBM newsroom: IBM expands its digital banking infrastructure with Swift integration

Disclaimer: This article is for informational purposes only and is not financial advice. Nothing here is a price prediction. We drew ISO 20022 standing and SWIFT timeline facts from swift.com and the trade-press sources linked above; they may change as SWIFT publishes further updates. Always do your own research before making any investment decision.