SWIFT in 2026: ISO 20022, a Blockchain Ledger and the Last-Mile Gap

For a decade, every fintech pitch deck had a slide that said SWIFT is slow. The network's own data now tells a more awkward story: most payments cross borders in under an hour, and the delay sits at the end of the chain, inside domestic banks. That reframing explains almost everything SWIFT has done since, from retiring its old message formats to experimenting with a shared ledger.

What SWIFT is, and what it is not

SWIFT does not move money. It is a messaging cooperative that more than 11,500 financial institutions use to tell each other where money should go. The money itself moves across correspondent accounts that banks hold with one another. On an average day the network carries over 53 million FIN messages, covering payments, securities and trade instructions.

It is also owned by its members, which shapes its incentives. SWIFT earns fees on messages, so it has every reason to keep banks on its network rather than see them drift to rival systems, and its member banks have a say in how fast change arrives. That cooperative structure helps explain why upgrades take years and why, once agreed, they tend to stick across the whole industry.

That distinction matters because it shapes what SWIFT can fix. It can standardise messages, track payments and set service rules for its members. It cannot force a bank in Lagos to credit a customer's account faster, and it cannot make nostro accounts cheaper to fund. Our guide to correspondent banking covers that plumbing in detail.

The speed numbers, read carefully

In October 2024 SWIFT reported that 90% of cross-border payments on its network reached the destination bank within an hour. Speeds into the euro area hit 92%, the Middle East 88% and Africa 87%. Measured against the G20 goal of settling 75% of cross-border payments within an hour by 2027, SWIFT said it was above target for all but two of its 40 largest country routes.

The catch is in the same release. Only 43% of payments reached the end customer's account within an hour. The bottleneck is the receiving bank: batch processing, manual compliance reviews, cut-off times and weekends. A worker in Riyadh might see the money leave in minutes while the family in Dhaka waits until the next business day.

The Financial Stability Board's own measurement is harsher. Its 2025 progress report found that only about 35% of cross-border payments met the one-hour goal globally and concluded that satisfactory improvement by 2027 was unlikely, as The Paypers summarised. The two figures measure different things, and the gap between them is the last mile.

ISO 20022: the end of MT

On 22 November 2025, the coexistence period for cross-border payments ended and SWIFT retired the old MT103 and MT202 instructions in favour of ISO 20022 messages, according to Payment Expert. Coexistence had begun in March 2023 after an earlier delay. In the United States, the Federal Reserve moved Fedwire Funds to ISO 20022 in July 2025.

Why should anyone outside a bank operations team care? Because the old MT format was a fixed set of short text fields. Names were truncated, addresses were stuffed into free text, and the purpose of a payment often vanished along the way. ISO 20022 carries rich, structured data: full party details, remittance information, purpose codes. That makes sanctions screening more accurate and reduces the false positives that hold payments in compliance queues, which is exactly where the last-mile delay lives.

The migration is not fully done. Translation tools let lagging banks keep running MT internally, and critics argue those converters strip out the structured data that was the point. The next deadline is November 2026, when unstructured postal addresses stop being accepted. Banks have to send structured or hybrid addresses, and the ones that relied on converters will feel it.

SWIFT's speed problem moved from the network to the receiving bank. Its strategy is to chase it there.

A blockchain ledger, from the incumbent

At Sibos in September 2025, SWIFT announced it would add a blockchain-based shared ledger to its infrastructure, starting with real-time, round-the-clock cross-border payments. Consensys built the conceptual prototype, and more than 30 institutions, including Santander, Bank of America, BNP Paribas and HSBC, signed up to give feedback and help implement it, The Block reported.

The ledger is designed to record transactions between banks, enforce rules through smart contracts and handle tokenised value while staying interoperable with existing systems. No go-live date has been published. Read plainly, it is a defensive move. If banks start settling with stablecoins or tokenised deposits on public networks, SWIFT wants to be the trusted layer that connects those networks, rather than the legacy system they route around.

Retail payments get their own rulebook

The other notable 2026 change is aimed at consumers. In March 2026 SWIFT launched a retail framework under which participating banks commit to fees known upfront, full value delivered to the recipient and the fastest available speed. More than 25 banks were scheduled to go live by the end of June across corridors including India, Bangladesh, China, the UK, the US and Canada, with over 50 banks supporting the scheme.

Full value delivery is the quiet headline. For decades, an intermediary bank could deduct a fee in transit, so a student's tuition payment arrived short and nobody could say why. A rule that bans that, if enforced, removes one of the oldest complaints in cross-border payments.

What to watch through 2027

• The customer-credit number. If the 43% figure climbs toward the bank-to-bank 90%, the last-mile problem is being solved. If it stalls, expect regulators to lean on receiving banks.
• Ledger pilots. The first live transactions on the shared ledger, and which tokens it carries, will show whether SWIFT is serious about public-chain interoperability.
• Structured data in practice. November 2026 will reveal how many banks still depend on converters.

SWIFT in 2026 is neither the dinosaur of fintech folklore nor a finished product. It is a network that fixed much of its own core and is now trying to drag its weakest members forward. Whether that is enough against blockchain-native rivals depends less on SWIFT than on the banks at the far end of each payment.

More guidesUK guidesBusiness payments guides

About this researchMuffinPay InsightsIndependent analysis of stablecoins, CBDCs, cross-border payments and digital public infrastructure. Every figure is linked to its source. Read our editorial standards →