Swift announced on September 29 that it will add a blockchain-based shared ledger to its infrastructure, starting with a project involving more than 30 financial institutions. The first proposed use is real-time cross-border payments available around the clock.
The Sibos announcement places the work at the design and prototype stage. Consensys will help develop a conceptual prototype, with banks supplying feedback before later implementation decisions. This is not a declaration that Swift’s global network has already moved its payments onto a blockchain.
A common record for regulated value
Swift envisages a ledger that records, orders and validates transactions between financial institutions, with smart contracts enforcing agreed rules. Its focus is the shared infrastructure. Commercial and central banks would determine the regulated tokens that move over it.
That separation leaves room for different forms of digital money without making Swift the issuer of a single new token. The announcement does not identify one stablecoin as the universal settlement asset.
Banks from 16 countries are contributing to the design. Named participants include Citi, HSBC, Deutsche Bank, JPMorgan, BNY and Standard Chartered. Their involvement gives the prototype a set of institutional requirements to work against, but it does not remove the need to prove the design and agree how a production service would operate.
Existing payment systems remain part of the plan
Swift is pursuing the ledger alongside improvements to its existing infrastructure. It also announced work on interoperability between established payment systems and public or private digital networks.
For a bank, the operational question is how a token transfer connects to balances, controls and records elsewhere. A shared ledger could synchronize parts of that process, while connections to existing systems would still be needed wherever money enters or leaves the digital network.
The announcement therefore describes parallel development: improvements to current payment services and a new route for tokenized value. Future phases depend on the prototype and subsequent work with Swift’s member community.
