Executive summary. The great migration is over; the data era has begun. SWIFT ended MT–MX coexistence for cross-border payment instructions on 22 November 2025, Fedwire went ISO-native on 14 July 2025, and roughly 97% of cross-border payment instructions now travel as ISO 20022. Two hard deadlines dominate the next four months: on 14 November 2026, fully unstructured postal addresses stop being accepted in CBPR+ payments, and the interbank MT101 relay is decommissioned in favour of pain.001 version 9. Beyond that, the roadmap runs through 2028 — investigations, statements, and direct debits — while instant rails, LEIs, and agentic AI reshape what the standard is for. Every claim below carries a primary or corroborated source, verified 26 July 2026.


01. Coexistence is over#

SWIFT's MT/ISO 20022 coexistence period for cross-border payments (CBPR+) ended on 22 November 2025. Payments-scope MT categories 1, 2 and 9 no longer meet CBPR+ requirements between financial institutions: MT103 traffic moved to pacs.008, MT202/202COV to pacs.009. SWIFT confirmed completion on 25 November 2025 (press release).

What did not end in November 2025 matters just as much. Corporate-to-bank traffic (SCORE) may still carry MT101 with no announced decommission date, closed user groups continue, and the FX, securities, and trade categories (3, 5, 7) were never in scope. Statements and direct debits follow later: investigations move to camt-based case management by November 2027, and MT9xx statements plus MT104/107 phase out by November 2028 (Swift CBPR+ roadmap, June 2026 edition).

Coexistence was a courtesy. It is over.

02. 14 November 2026: structured addresses#

From 14 November 2026, CBPR+ payment messages carrying fully unstructured addresses are rejected on the SWIFT network. The accepted forms are structured — or hybrid: town name and country in structured elements (, ), with up to two 70-character address lines for the remainder. Hybrid has been available since November 2025 and is codified in the Payments Market Practice Group's Hybrid Postal Address guideline v1.12 of 5 March 2026 (SWIFT: removal of unstructured address; PMPG v1.12).

Industry analysis in early 2026 still put the share of messages carrying unstructured addresses at roughly two-thirds (NTT DATA). The bottleneck is not message formatting — it is customer master data. Pain001 generates structured and hybrid address elements today; the remediation work lives in your vendor files.

Fix the data, and the format follows.

03. 14 November 2026: MT101 relay becomes pain.001#

The same date retires the interbank MT101 relay — the request-for-transfer flow between banks — replaced by CBPR+ pain.001 version 9. Multi-transaction MT101s will be rejected outright; single-transaction messages get temporary contingency conversion with additional validation (Swift call to action for November 2026).

This is precisely the seam the Pain001 MT101 loader closes: parse the MT101, regenerate as pain.001.001.09, validate against the official XSD, submit with confidence — no dependency on in-network contingency translation you do not control.

04. The rails, region by region#

  • United States. Fedwire completed its single-day ISO 20022 cutover on 14 July 2025 with more than 4,700 participants (Federal Reserve). CHIPS migrated in April 2024. FedNow passed 1,600 participating institutions, raised its transaction limit to $10 million, and settled 2.73 million payments worth $271 billion in Q1 2026 (Digital Transactions).
  • Euro area. T2 has been ISO-native since 2023. The Instant Payments Regulation is fully in force for euro-area PSPs — receive since 9 January 2025, send plus Verification of Payee since 9 October 2025, applying to all SEPA credit transfers, not just instant ones (ECB). TIPS opened cross-currency settlement (EUR/SEK/DKK) on 8 June 2026 (ECB MIP news).
  • United Kingdom. CHAPS has run on ISO 20022 since June 2023; purpose codes and LEIs became mandatory for property and interbank payments in May 2025, and the Bank of England will extend mandatory purpose codes to all CHAPS payments from November 2027 (Bank of England policy statement). The retail NPA programme as procured was cancelled; upgrades now run through the refocused infrastructure-renewal effort under the Payments Vision Delivery Committee.
  • Asia-Pacific and Gulf. Japan's BOJ-NET completed migration in November 2025, joining MEPS+ (2022), RITS (2023), and CHATS (2024). The UAE's ISO-native Aani instant scheme counts 74 participants and 1.5 million users, with cross-border interlinking procurement under way in 2026.

05. Beyond compliance: what the data is for#

  • Identity. The active LEI population passed 3 million in Q1 2026, and the FSB endorses LEI use in cross-border payments (GLEIF).
  • Speed. ACI forecasts 427.7 billion real-time transactions in 2026, rising to 27.1% of all electronic payments by 2028 (ACI Worldwide).
  • Honesty about progress. The FSB's October 2025 review concludes the G20 cross-border targets are unlikely to be met by 2027 — cost, speed, and access KPIs have barely moved (FSB). Structured ISO 20022 data is the prerequisite for fixing that, which is why the CPMI refreshed its harmonised data requirements in February 2026 (BIS CPMI).
  • Fraud. SWIFT and 13 global banks demonstrated that federated-learning models detect cross-border fraud roughly twice as well as siloed models in 2025 trials (SWIFT). Rich, structured payment data is what makes such models possible.
  • Agents. Mastercard's Agent Pay, Visa's Trusted Agent Protocol, Google's AP2, and the Linux Foundation's x402 effort (backed by Visa, Mastercard, and Stripe as of July 2026) are building the authorisation layer for AI-agent commerce. The file layer — where corporate credit transfers are actually initiated — is served by exactly one open MCP implementation: pain001-mcp.

06. What to do this quarter#

  1. Audit address data now. Count beneficiaries with free-text-only addresses; that number is your November exposure.
  2. Regenerate, do not translate. Convert remaining MT101 flows to validated pain.001.001.09 while the contingency window is open — not after it closes.
  3. Validate before the bank does. A --dry-run gate in CI catches schema and rulebook failures at commit time, for nothing.
  4. Watch 2027–2028. Investigations (camt.110/111), statements (camt.05x), and direct debit migration are already scheduled. Teams that treat ISO 20022 as a living standard, not a completed project, will absorb each wave quietly.

There is no soft landing left to wait for. The teams that fixed their data are already collecting the dividend.


References#

  • SWIFT (2025). Global financial community completes switch to ISO 20022. swift.com
  • SWIFT (2026). Removal of unstructured address — November 2026 milestone. swift.com
  • PMPG (2026). Hybrid Postal Address, v1.12. swift.com
  • Federal Reserve Financial Services (2025). Fedwire Funds Service ISO 20022 implementation. frbservices.org
  • European Central Bank (2025–2026). Instant Payments Regulation; TIPS cross-currency settlement. ecb.europa.eu
  • Bank of England (2025). Expanding mandatory ISO 20022 enhanced data in CHAPS from 2027. bankofengland.co.uk
  • CPMI (2026). Harmonised ISO 20022 data requirements for enhancing cross-border payments — updated report. bis.org
  • FSB (2025). G20 Roadmap for Cross-border Payments: consolidated progress report. fsb.org
  • GLEIF (2026). The LEI in numbers, Q1 2026. gleif.org
  • ACI Worldwide (2025). Prime Time for Real-Time. aciworldwide.com