The messaging cooperative is no longer merely trying to connect blockchains. In 2026 it added a blockchain ledger to its own stack. The strategic question is whether Swift can turn its installed base, standards and trust into a neutral execution layer for tokenised finance — before bank-led networks and new settlement platforms make that role redundant.
Research updated: 11 August 2026
For years, the most common blockchain-era prediction about Swift was that distributed ledgers would make a global financial messaging network obsolete. In July 2026, Swift complicated that story. The cooperative said its blockchain-based ledger was ready for initial use and that 17 banks from six continents were preparing to pilot live transactions using tokenised deposits. The ledger is designed to support 24/7 cross-border payments, including overnight and weekend activity, while banks retain control of their own assets and complete final settlement through existing systems. (Swift, 9 July 2026).
That changes the competitive question. Swift is no longer defending a purely message-based architecture against blockchain networks. It is trying to absorb the useful parts of distributed-ledger technology into an infrastructure that already sits at the centre of regulated international finance. The gamble is that the next generation of money will be plural — tokenised deposits, central-bank money, stablecoins, conventional account balances and tokenised securities — and that the winner will be the layer that can make those forms interoperate safely rather than the chain that replaces everything else.
The timing matters. The Financial Stability Board’s 2025 assessment was blunt: policy work under the G20 cross-border payments roadmap had produced only slight global improvement, and satisfactory progress by the end-2027 target date looked unlikely. In other words, incumbents still have a problem to solve, but new entrants also have room to prove that different infrastructure can solve it better. (FSB, 9 October 2025).
THE CORE ARGUMENTSwift can remain central to global finance if it becomes a trusted interoperability and orchestration layer across ledgers. It is less likely to win by turning itself into just another closed blockchain network.
From financial messenger to transaction orchestrator
Swift’s original strategic asset was standardised communication. Its new ledger adds something more consequential: shared state. The March 2026 design described an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu. Swift operates the orchestration layer, validates funding commitments and coordinates interbank processes; banks operate their own environments and retain authority over keys, assets, funding and settlement. The first use case focuses on interoperating tokenised bank deposits for 24/7 cross-border payments. (Swift shared-ledger design, 30 March 2026).
That distinction matters. Messaging tells two institutions what should happen. A shared ledger can help them agree on what has happened, in what sequence, under what conditions and with what funding commitments. In a programmable market, that shared state can be used to coordinate conditional payments, foreign-exchange legs, securities settlement and automated treasury processes. It shifts Swift from being a carrier of instructions towards being part of the execution fabric.
The move did not appear from nowhere. Swift had already run interoperability experiments across public and private blockchains, CBDC environments and tokenised-asset platforms. In a trial disclosed in January 2026 with BNP Paribas Securities Services, Intesa Sanpaolo and Societe Generale-FORGE, Swift orchestrated tokenised-bond settlement and lifecycle events across traditional and blockchain systems, including settlement with fiat money and SG-FORGE’s EUR CoinVertible digital asset. The important point was not that Swift issued the asset or money; it coordinated the workflow across heterogeneous rails. (Swift digital-asset interoperability trial, 15 January 2026).
Swift’s advantage is not the blockchain
If Swift succeeds, it will not be because Hyperledger Besu is uniquely superior. The technology is open source and replaceable. Swift’s harder-to-replicate advantage is distribution: more than 11,500 banking and securities organisations, market infrastructures and corporate customers across more than 200 countries and territories are connected to its ecosystem. That is an installed base, a governance network and a standards community at the same time. (Swift network profile, July 2026).
The second advantage is data standardisation. The global cross-border payments community completed the main migration to ISO 20022 in November 2025. Swift reported that 97% of payment instructions observed immediately after the final cutover were already using ISO 20022, with a conversion service handling the remainder during transition. Rich, structured payment data are not glamorous, but they are crucial for sanctions screening, exception handling, reconciliation and automation — and those functions become even more important when payments are programmable. (Swift ISO 20022 cutover, 25 November 2025).
This is where the phrase “blockchain era” can be misleading. Financial institutions do not merely need a faster database. They need common identifiers, legal accountability, compliance data, exception processes, dispute resolution, liquidity arrangements and predictable operating rules. A blockchain can change the technical location of records without solving those coordination problems. Swift already occupies many of the coordination layers that sit around the ledger itself.
The third advantage is that the legacy network is not standing still. Swift says 75% of cross-border payments on its network reach the beneficiary bank within 10 minutes; its own analysis also says the international leg accounts for less than 20% of total processing time on average, with roughly 80% of the journey occurring in the final “last mile” after the payment reaches the recipient’s financial institution. Those are Swift’s own network measurements, not an independent industry-wide benchmark, but they underscore a strategic reality: some cross-border pain sits outside the interbank messaging layer. (Swift on G20 goals and last-mile frictions, 2026).
The awkward truth: the new ledger does not yet remove settlement
Swift’s first production-oriented design is deliberately conservative. The July announcement says tokenised deposits can be used to move funds for customers before final settlement is completed through existing systems. The March technical description was similarly explicit: settlement can continue through RTGS systems, correspondent-banking relationships or other agreed mechanisms. That makes the ledger an orchestration and commitment layer rather than a universal settlement asset. (Swift ledger operating model).
This is a sensible way to achieve adoption. It avoids requiring banks to abandon their central-bank accounts, correspondent relationships or existing liquidity frameworks on day one. It also reduces the legal and prudential leap from a familiar bank liability to a novel settlement instrument. But it creates a limit: if the underlying settlement still waits for conventional systems, then some of the liquidity, finality and operating-hour frictions that tokenisation promises to remove remain elsewhere in the chain.
Project Agorá provides a useful benchmark. In May 2026, the BIS and Institute of International Finance said the project’s prototype had demonstrated atomic wholesale cross-border settlement using tokenised commercial-bank deposits and tokenised central-bank reserves. The model preserved jurisdiction-specific control over reserves while allowing multi-currency transactions to settle on an all-or-nothing basis. The project is now intended to progress to real-value testing with certain currencies and participants. (BIS Project Agorá, 27 May 2026).
The implication is not that Agorá will “beat” Swift; Swift itself has participated in the broader Agorá ecosystem. The implication is that the industry’s technical benchmark is moving toward atomic settlement, not merely faster coordination. Swift’s ledger therefore needs a credible path from off-ledger final settlement to interoperable settlement assets — including central-bank money where available — if it is to capture the full economic promise of tokenisation.
Four models now competing for institutional relevance
Model
Current evidence
Strategic implication for Swift
Swift shared ledger
17 banks preparing pilots; tokenised deposits coordinated 24/7; final settlement initially remains in existing systems.
Fast adoption path and broad reach, but Swift must prove that orchestration can evolve toward stronger on-chain finality.
Bank-led token networks
J.P. Morgan’s Kinexys and Citi Token Services already support live or near-real-time 24/7 institutional flows inside regulated bank frameworks.
Large banks can solve important corridors without waiting for a universal industry layer.
Multi-bank DLT infrastructure
Partior markets live 24/7 multi-currency clearing and settlement with atomic capabilities and has expanded to institutions across regions.
A narrower network can still compete if it offers stronger settlement functionality and attractive liquidity economics.
Public-private tokenised settlement
Project Agorá demonstrated atomic settlement using tokenised deposits and central-bank reserves and is advancing toward real-value testing.
Central-bank money could become the anchor that defines the strongest institutional settlement architecture.
The competition is already live
Swift does not have the luxury of defining this market alone. J.P. Morgan said in June 2026 that its Kinexys blockchain business had processed more than $4 trillion in transaction volume since inception, with average daily transactions exceeding $7 billion. Kinexys Digital Payments is bank-led and permissioned, but it demonstrates that tokenised commercial-bank money can support production-scale treasury and payment use cases inside a large banking franchise. (J.P. Morgan Kinexys update, 29 June 2026).
Citi is taking a different route. On the same day as Swift’s July ledger announcement, Citi and Siam Commercial Bank said SCB had become the first financial-institution client to go live with Citi’s integrated 24/7 USD Clearing and Citi Token Services solution. Citi said its 24/7 clearing service connected more than 300 financial institutions across over 50 markets, while its token service uses a private permissioned blockchain to represent deposits within Citi’s network. The first disclosed transaction crossed a US holiday weekend from a Citi London account to an SCB beneficiary in Thailand. (Citi and Siam Commercial Bank, 9 July 2026).
Partior pushes further toward a multi-bank settlement-network model. Its current platform describes 24/7 multi-currency real-time clearing and settlement and atomic payment-versus-payment functionality; in July 2026 it announced Emirates NBD was live on the network for real-time blockchain-based cross-border USD payments. Unlike a single-bank token network, Partior’s proposition is explicitly shared infrastructure across institutions. (Partior, accessed 11 August 2026).
These models are not mutually exclusive. A global bank can use its proprietary token network for internal or client flows, a multi-bank DLT network for certain currencies, domestic instant-payment systems for the last mile and Swift for routing, identity, compliance data and connectivity. That is precisely why interoperability may be more valuable than exclusivity. The risk for Swift is not that one blockchain replaces it overnight; it is that enough high-value activity migrates into specialist networks that Swift becomes a secondary bridge rather than the primary coordination layer.
Why interoperability is harder than a connector
The BIS’s 2026 Annual Economic Report gives the strongest reason not to treat interoperability as a simple API problem. It notes that permissionless networks are fragmented across base and secondary chains, while permissioned platforms often use different rules, identities and data policies. Bridges and ad hoc links can introduce operational risks. Even where tokenisation works technically, production systems require resilient governance and clear operating rules. (BIS Annual Economic Report 2026).
For Swift, this raises four hard questions. First, who bears liability when a workflow spans several ledgers and one leg fails? Second, which representation of money is final for accounting and legal purposes? Third, how are sanctions, AML, privacy and data-localisation rules applied consistently when information crosses jurisdictions? Fourth, who can change the smart-contract logic, pause a transaction or recover from an operational incident? These are governance questions disguised as technology questions.
Swift’s cooperative model could help because it is familiar to regulated institutions and operates within a framework of central-bank oversight. Yet that same governance model can slow change if members have conflicting commercial interests. A system designed by dozens of global banks may be more legitimate than a proprietary network, but it may also be harder to optimise. Neutrality is an asset only if it does not become indecision.
The 24/7 problem is operational, not just technical
One of the ledger’s headline promises is round-the-clock cross-border payment availability. But a blockchain that runs 24/7 does not make a bank 24/7. Treasury teams, fraud operations, sanctions controls, liquidity desks, central-bank facilities, foreign-exchange markets, customer-service functions and incident-response processes all have to support the same operating model. If the digital rail is always open while liquidity and control functions retain weekday cut-offs, the result may be a faster path to a queue rather than true real-time finance. The FSB’s March 2026 summit similarly emphasised implementation at the jurisdictional and regional level, including domestic payment infrastructure, because the first and last mile of cross-border payments depend on local rails. (FSB Cross-border Payments Summit, 12 March 2026).
This is one reason tokenised deposits are strategically attractive. They allow banks to extend familiar commercial-bank money into programmable environments without asking corporate treasurers to hold volatile crypto-assets. But tokenised deposits do not automatically create shared liquidity across institutions. Each bank liability still carries an issuer, a balance sheet and a legal claim. Interoperability must therefore include conversion and settlement mechanics, not just message compatibility.
What Swift must prove in the next phase
The first test is economic, not technical. Banks will need evidence that the shared ledger reduces funding buffers, reconciliation effort, exception rates or processing cost enough to justify integration and operating changes. A successful pilot that moves a token from A to B is not the same as a business case for shifting material treasury flows.
The second test is neutrality across money. Swift’s stated ambition is to support broader digital-asset ecosystems, not only one bank’s tokenised deposit design. To be credible, the ledger must be able to work with different commercial-bank tokens, conventional balances and eventually central-bank settlement assets without making one institution’s balance sheet the privileged form of money.
The third test is composability without fragmentation. Programmability is useful when a payment can be conditioned on delivery of a security, receipt of goods, an FX leg or a verified business event. But every additional platform creates another potential boundary. Swift’s strategic value rises if one connection can coordinate many networks; it falls if banks still have to build bespoke operational and legal arrangements for each corridor.
The fourth test is whether Swift can preserve the strengths of its existing system while changing its own role. The cooperative’s brand rests on resilience, predictable governance and standardisation. Blockchain-era infrastructure introduces smart-contract risk, cryptographic key management, new node architectures and potentially continuous operations. Reinvention will succeed only if the new layer feels less like a parallel experiment and more like an extension of the operational discipline institutions already expect from Swift.
Implications for banks, fintechs, regulators and investors
For banks, the strategic question is architecture. Building only proprietary token networks may create powerful closed-loop economics, but corporate clients increasingly operate across multiple banks. Joining only shared networks may preserve interoperability but cede product differentiation. The likely answer is a portfolio: proprietary capabilities where a bank has scale, shared rails where network effects dominate, and orchestration layers that prevent those choices from becoming isolated silos.
For fintechs and payment companies, a Swift ledger could lower the cost of institutional connectivity if banks expose access through APIs and standardised services. It could also raise the competitive bar. A fintech whose value proposition is simply “faster cross-border transfer” may find itself competing with upgraded bank infrastructure. The more durable opportunities may sit in treasury automation, compliance intelligence, orchestration, wallet/account abstraction and last-mile distribution.
For regulators and central banks, the central issue is not whether blockchain is allowed to participate in finance; it already does. The harder issue is how tokenised commercial-bank money connects back to the monetary anchor, how legal finality works across borders, and how operational resilience is maintained when critical flows depend on smart contracts and interoperability layers. Project Agorá’s finding that atomic settlement can be structured while preserving domestic control over reserves makes that debate more concrete. (Project Agorá report, May 2026).
For investors in payments infrastructure and bank technology, the most important competitive metric may shift from transaction speed to network utility. A payment rail that is marginally faster but isolated from counterparties, liquidity and regulatory frameworks can be less valuable than a slightly slower layer that connects everything. Swift’s thesis is essentially that trusted connectivity remains scarce even when ledgers become abundant.
The counterargument: perhaps the ledger is a bridge to nowhere
There is a credible bearish case. Cross-border payments could improve substantially through ISO 20022, instant-payment interlinking, better data and upgraded correspondent banking without requiring a new blockchain layer at all. The FSB’s targets are technology-neutral: they focus on cost, speed, transparency and access, including a target for 75% of wholesale and retail cross-border payments to meet one-hour speed thresholds by end-2027. (FSB G20 cross-border payment targets).
If conventional rails become fast enough and tokenised assets remain a niche share of institutional activity, Swift’s ledger could become an expensive compatibility layer for a market that never scales. Conversely, if digital finance concentrates around a few dominant proprietary networks, those networks may build direct interoperability and reduce the need for a neutral central orchestrator. Swift therefore faces risk on both sides: too little tokenisation makes the investment unnecessary; too much platform concentration makes it bypassable.
A second bearish argument is architectural. An orchestration ledger that still relies on off-ledger settlement may inherit the complexity of both worlds. Banks could end up operating token infrastructure while still maintaining legacy accounts, reconciliation and liquidity processes. The transition only creates lasting value if duplicated processes are eventually retired or materially simplified.
Reinvention, not replacement
Swift’s strongest response to blockchain is not to claim that blockchain was unnecessary. It is to recognise that the technology changes where financial state can be shared and executed, then reposition the cooperative around the functions that remain scarce: trusted identity, common data, governance, connectivity and cross-network coordination.
The July 2026 ledger launch is therefore strategically significant, but not decisive. Swift has demonstrated that it can move from experimentation to deployable infrastructure and attract major banks to the first wave. It has not yet demonstrated that the model can deliver atomic multi-bank settlement at scale, produce superior economics to specialist networks, or become the default bridge across tokenised deposits, central-bank money and digital assets.
The most plausible future is not one in which Swift defeats blockchain or blockchain defeats Swift. It is one in which global finance becomes a patchwork of ledgers, instant-payment systems, tokenised bank money and conventional accounts — and the decisive infrastructure is the layer that makes the patchwork behave like a coherent system. Swift can still be that layer. But in the blockchain era, incumbency buys it the right to compete, not the right to remain central.
References
2. Swift — “Swift’s blockchain-based shared ledger progresses to MVP implementation” (30 March 2026)
4. Swift — “Global financial community completes switch to ISO 20022…” (25 November 2025)
5. Swift — “G20 goals for enhancing cross-border payments” (accessed 11 August 2026)
11. Bank for International Settlements — Annual Economic Report 2026 (June 2026)
12. J.P. Morgan — “Kinexys Expands Blockchain Deposit Accounts in Asia-Pacific” (29 June 2026)
14. Partior — live network and latest institutional developments (accessed 11 August 2026)