Every time a company pays a supplier in another country, there's invisible infrastructure working behind the scenes: messages hopping from bank to bank, correspondent accounts being debited and credited, and waiting periods we take for granted without asking why they exist. That infrastructure is called SWIFT, it has more than 50 years of history, and in 2025 it completed the biggest update to its message format since it was born. At almost the same time, blockchain built a completely different architecture for the same problem: moving value between countries.
In this piece we walk through both stories side by side — where SWIFT comes from, why it had to modernize with ISO 20022, how blockchain evolved since 2008, and why the security model of each is structurally different.
The problem before SWIFT: banks speaking different languages
Until the early 1970s, banks communicated across borders using telex, a technology inherited from the mid-20th century. The problem wasn't just speed: each bank described its operations in free-form text, with no common standard. An international payment depended on an employee, working in another language and another internal format, correctly interpreting what someone had typed on the other side of the world — with no automation and no real security layer.
1973: SWIFT is born, the first common language of money
That year, 239 banks from 15 countries came together in Brussels to solve exactly that problem, founding SWIFT (Society for Worldwide Interbank Financial Telecommunication). Belgium was chosen as headquarters deliberately: neutral territory, so as not to favor either London or New York as the dominant financial hub.
In 1975, operating rules and liability procedures were defined among participating banks, and in 1977 the first real message was sent over the network, replacing telex free text with coded, standardized messages — the "MT" (Message Type) formats. For the first time, any bank in the world could automatically understand what another bank was telling it, with no ambiguity.
The fact almost nobody explains well about SWIFT
SWIFT does not move money. It's a messaging system — the equivalent of certified mail between banks. Money moves afterward, through a chain of correspondent banks that hold accounts with one another. SWIFT only instructs: "bank A asks bank B to pay bank C," but it never executes that payment itself.
That distinction between messaging and settlement is the root of almost all the friction we know today in cross-border payments: the intermediaries, the wait, the cost that accumulates at every hop in the chain. Today the network connects more than 11,000 financial institutions in over 200 countries, and for years it covered close to half of the world's high-value cross-border payments.
The limit of a 1970s design
The MT format was designed for telex more than fifty years ago, and it carries that limitation to this day: unstructured free-text fields, with no real room for compliance metadata, payment purpose, or detailed regulatory information. That's not a minor detail: it generated very high rates of false positives in sanctions and anti-money-laundering screening, simply because the system couldn't precisely "read" who each party to a transaction was.
Traditional banking modernizes: the migration to ISO 20022
Faced with these limitations, the global banking industry undertook a years-long migration to ISO 20022, a standard built on structured XML, organized into families such as pain (payment initiation), pacs (clearing and settlement), and camt (cash management). In practice: MT103 → pacs.008, MT940 → camt.053.
The timeline shows just how costly it is to modernize a system with fifty years of history:
- 2023: Europe migrates TARGET2, EURO1, and CHAPS.
- 2024: the United States migrates CHIPS.
- July 14, 2025: the Federal Reserve migrates Fedwire in a single-day cutover, after postponing it once due to industry readiness issues.
- November 22, 2025: Swift officially ends MT/MX coexistence for cross-border payments.
- 2026-2027: migration backlogs (certain reporting messages) are still being resolved.
In other words: the global banking system just finished, fifty years later, updating the language its messages travel in. A change of format, not of architecture — correspondent banks, settlement times, and the separation between message and fund movement all remain intact.
The other story of digital money: how blockchain evolved
In 2008, while traditional banking was still running on a 1970s architecture, Satoshi Nakamoto published the Bitcoin whitepaper: a system capable of transferring value directly between two parties, with no correspondent banks, solving the double-spend problem without a central authority.
From there, blockchain's evolution moved fast:
- 2008: Satoshi Nakamoto publishes the Bitcoin whitepaper.
- 2009: the Bitcoin network launches, the first verifiable digital transfer of value with no intermediaries.
- 2015: Ethereum arrives, introducing smart contracts — the blockchain goes from being a ledger of transfers to being able to execute financial logic automatically.
- 2014-2018: the first stablecoins are born: Tether (USDT) in 2014 on the Omni Layer (Bitcoin), and USDC in 2018 from CENTRE (Circle/Coinbase) — solving the practical problem of volatility with a crypto asset pegged 1:1 to a fiat currency.
- 2020-2022: scaling solutions (Layer 2) take off, and Ethereum migrates from Proof of Work to Proof of Stake, drastically cutting energy consumption without losing security guarantees.
- 2023-2025: regulation arrives (MiCA in Europe, stablecoin frameworks in the US), and the ecosystem moves from crypto experiment to regulated financial infrastructure.
- 2025-2026: adoption turns institutional. Banks, fintechs, and governments stop debating whether to use blockchain and start competing over who will lead that infrastructure.
The fundamental difference with SWIFT isn't just a matter of era — it's a matter of design. Blockchain doesn't separate messaging from settlement — the transaction is the movement of money, in the same instant.
Why the security model is structurally different
Blockchain rests on three technical pillars. Cryptography: every transaction is signed with a public/private key pair, and each block is chained to the previous one through hash functions. Distributed consensus: there's no central authority deciding what's valid; thousands of nodes must agree, and attacking the network requires controlling the majority of that distributed power. And immutability: once confirmed, a transaction is practically impossible to alter, and on public networks anyone can audit the full history.
SWIFT, by contrast, is a model of institutional, perimeter-based security: it trusts the identity of whoever sends the message, and trusts that each of its roughly 11,000 member banks keeps its own internal cybersecurity flawless. It doesn't mathematically verify each transaction — it verifies credentials.
The clearest example of this difference is the 2016 Bangladesh Bank heist. Attackers linked to the Lazarus Group got in through phishing, stole the bank's SWIFT terminal access credentials, and sent 35 fraudulent instructions worth $951 million. SWIFT's own CEO publicly acknowledged that the core network was never breached — the attack happened at the periphery, on the poorly protected computers of a member bank. Even so, five instructions went through and $101 million was stolen, of which $81 million was never recovered.
The structural lesson: SWIFT's security is only as strong as the weakest link among thousands of connected institutions. On SWIFT, if someone steals your credentials or compromises your local bank, the system assumes the order is legitimate and executes it. On blockchain, by contrast, self-custody and multi-signature (multisig) smart contracts let you set programmable rules where no single key can move funds on its own — security is built into the protocol itself, without depending on every individual actor behaving well.
| Criterion | SWIFT (ISO 20022) | Blockchain / Stablecoins |
|---|---|---|
| Nature | Messaging network (instruction) | Settlement network (value movement) |
| Speed | Hours to days, depending on correspondents | Seconds to minutes, 24/7/365 |
| Costs | Fees at each intermediary + FX margin | Fixed fee, no intermediary chain |
| Security | Perimeter-based: trusts ~11,000 banks | Cryptographic and distributed across the network |
| Data structure | Structured hierarchical XML | Immutable ledger / smart contracts |
Conclusion
From 1960s telex, to SWIFT's coded messages in 1977, to ISO 20022's structured XML in 2025, traditional banking spent more than fifty years improving the quality of the message that travels alongside the money — without changing the underlying architecture. The Swift GPI initiative, and now ISO 20022, managed to cut settlement times on several corridors down to hours, but they didn't solve the cost problem: every hop in the correspondent chain (sending bank, one or more intermediary banks, receiving bank) adds its own fee, on top of the margin applied on currency conversion. Blockchain, in under twenty years, solved a different problem: eliminating the need for the message and the money to travel separate paths, with fixed fees, no intermediary chain, and a security model that doesn't depend on the good behavior of thousands of institutions.
That's the underlying reason stablecoins and blockchain rails stopped being an experimental alternative and became real payments infrastructure. At Prismapay, we help companies make that leap without friction: if your operation still depends on waiting three to five business days and paying hidden fees at every intermediary in an international transfer, let's talk about changing the rail without changing how you operate.
Prismapay — corporate banking for your company.