Swift put a blockchain ledger into its global payments roadmap

On September 29, 2025, Swift announced that it would add a blockchain-based shared ledger to its technology infrastructure, beginning with a conceptual prototype for real-time, round-the-clock cross-border payments. Consensys was supporting the early-stage prototype, while more than 30 financial institutions were contributing to the ledger’s design.

The development mattered because Swift occupied a central position in institutional cross-border finance. Rather than treating blockchain solely as an external network to connect with, Swift proposed placing shared-ledger technology inside its own infrastructure stack. The announcement nevertheless described a development program, not a completed payment network, production launch or endorsement of any cryptocurrency.

A ledger designed with banks

Swift said financial institutions from 16 countries were providing design feedback. Its published roster included Bank of America, BNP Paribas, BNY, Citi, DBS Bank, Deutsche Bank, HSBC, JPMorgan Chase, MUFG, OCBC, Royal Bank of Canada, Santander, Standard Chartered and Wells Fargo, among others.

The first use case was intended to support real-time, 24/7 cross-border payments. Swift envisioned the ledger as a shared transaction record that could record, sequence and validate activity and enforce agreed rules through smart contracts. It also said the system would be designed to interoperate with existing infrastructure and emerging digital networks.

Those descriptions were architectural objectives supplied by Swift and participating institutions. As of September 29, 2025, Swift had not published a final technical design, production timetable, transaction throughput, fee schedule, tested currency pairs or independent security assessment. Reuters reported that the timeline remained undefined.

What Consensys was—and was not—building

Consensys confirmed on September 29 that it was helping Swift with early-stage prototyping and capability exploration. The company described its immediate role as helping Swift make informed design choices during the initiative’s first phases.

That limited description is important. The contemporaneous records did not identify a final production blockchain, consensus mechanism or public-network deployment. They did not say that Ether or another existing cryptocurrency would be required for payments. Claims tying the completed system to a particular public chain, token price or investment outcome would therefore have exceeded the event-day evidence.

Swift also separated the ledger infrastructure from the monetary assets that might move across it. The cooperative said decisions about the forms of regulated tokenized value would belong to commercial and central banks. This left tokenized deposits, regulated stable-value instruments and central-bank money as possible areas of institutional design without confirming that any one instrument had been selected for production use.

From messaging toward shared execution

The project’s conceptual significance lay in the proposed shift from transmitting standardized financial messages toward maintaining shared transaction state. A common ledger could, if successfully implemented, reduce reconciliation among separate institutional systems and enable programmable payment conditions. Those were prospective benefits, not measured results on September 29.

Swift simultaneously said it would add client capabilities for interoperability across existing and emerging systems, including private and public networks. That parallel approach suggested the cooperative was not presenting the new ledger as an immediate replacement for correspondent banking, existing fiat rails or outside blockchain systems. It was developing additional infrastructure intended to coordinate them.

What September 29 established

The verified milestone was the start of a large institutional design effort: Swift, Consensys and more than 30 financial institutions had begun work on a blockchain-based shared ledger, with always-on cross-border payments as the initial use case.

The record did not establish that banks had settled live customer payments through it, that deployment was inevitable, or that the project would outperform stablecoins or existing payment networks. Its importance on September 29, 2025 was strategic rather than operational: a major financial-messaging institution had made shared-ledger technology part of its stated infrastructure roadmap while keeping asset selection, implementation details and commercial performance unresolved.