Did SWIFT Give Enough Time? Yes. So Why Are Banks Still Hybrid?

With the impending changes, many institutions are exploring hybrid MT-MX systems to ensure a smooth transition. SWIFT announced the ISO20022 migration years ago. In fact, banks received one of the longest notice periods in the history of financial messaging:

2018: Early migration roadmap
2019–2021: Release of CBPR+ rulebooks
2022: Coexistence phase begins
2023–2025: Gradual implementation
2025–2026: Expected decommissioning of MT messages

On paper, this looked like a generous runway. Yet most banks in Asia, Africa, the Middle East, and even the United States still operate hybrid MT-MX systems today.

Hybrid MT-MX systems converting MT messages to ISO20022 MX format using an automated translation layer

There are reasons for this slow transition, and none of them are laziness. The reality is more complicated.

Legacy Core Systems Cannot Absorb ISO20022 Overnight

Many banks still run decades-old core systems built on COBOL or similarly rigid languages. These systems cannot store, parse, or use the massively expanded MX message structures — especially fields such as:

ultimate creditor/ultimate debtor
structured addresses
compliance-related attributes
purpose codes
LEI details
extended remittance information

Upgrading the core is like replacing a jet engine mid-flight; one small change affects:

posting
reconciliation
compliance
fraud systems
liquidity management tools

A hybrid MT-MX layer is simply safer.

Correspondent Banks Are Not Synchronized

SWIFT’s global network includes thousands of institutions, each at different stages of readiness.
If Bank A sends pacs.008 but Bank B still expects MT103, the payment stalls or is rejected.

Hybrid MT-MX systems ensure:

MT for partners still on legacy rails
MX for banks that already migrated

This avoids cross-border payment failures and ensures operational continuity.

ISO20022 Carries Far More Data — And That Creates Problems

Compared to MT messages, MX structures are far larger and far more structured.
Banks struggle with:

mandatory structured postal addresses
purpose-of-payment consistency
huge remittance blocks
stricter field validation
CBPR+ semantic rules

Many legacy AML tools and screening engines cannot handle this new level of detail, leading to false positives and processing delays.

Compliance Pressure Forces a Conservative Approach

CBPR+ is strict. Very strict.
Incorrect formatting can trigger:

message rejection
compliance flags
sanctions screening failures
delayed settlements
high repair queue volumes

Running a hybrid MT-MX model lets banks protect their internal processes while sending fully compliant MX messages externally through a conversion engine.

Vendors Themselves Were Not Ready

Payment hubs, AML tools, screening systems, and even some core banking providers underestimated the complexity of ISO20022.

Many vendors struggled to deliver:

end-to-end pacs.008/pacs.009 flows
structured data parsing
reconciliation via camt.053/camt.054
migration of RMA+
UETR lifecycle management

Banks had to wait for updates, patches, and certified releases before going fully MX.

Budget Constraints and Operational Priorities Slowed the Shift

ISO20022 migration is expensive.
Banks in South Asia, Africa, and the Middle East often prioritize:

cybersecurity upgrades
digital apps
regulatory reporting
branch network modernization

Payments transformation becomes “Phase 2”, not “Phase 1”.
Hybrid MT-MX systems deliver compliance without deep internal restructuring.

So Why Are Hybrid MT-MX Systems Still Used?

Because they work.
Because they reduce risk.
Because multinational banks and small local banks are migrating at different speeds.

Hybrid systems allow:

MT internally
MX externally
seamless conversion
compliance protection
lower operational disruption

Even in 2025–2026, hybrid coexistence will remain common across global correspondent corridors.

(All are authoritative sources for ISO20022 & CBPR+.)

Tag: payment compliance

Why Banks Still Use Hybrid MT–MX Systems Despite SWIFT’s Long Migration Timeline