Banks Need Internal Ledgers and Wallets to Connect to Swift's Blockchain Ledger

Banks seeking to link tokenized deposits to Swift's blockchain ledger must have their own permissioned ledgers, digital asset wallets, and tokenization and smart contract capabilities. While Swift's public ledger coordinates bank-to-bank payments, actual transactions require internal infrastructure support. Taurus co-founder and Managing Partner Lamine Brahimi stated in a CoinDesk interview on July 7 that these features are necessary but do not indicate design flaws in Swift's ledger—rather, they provide banks with options.
Brahimi clarified that Swift's ledger does not replace bank internal systems or existing payment processes. Tokenized deposits recorded on bank ledgers enable inter-institutional transfers, with final settlement still occurring through traditional channels. Tokenized deposits differ from stablecoins issued outside banking, as they remain on bank balance sheets.
Swift completed initial preparations for its blockchain-based ledger on July 9 and announced that 17 banks across six continents are preparing tokenized deposit transactions. Initial readiness does not equate to transaction volume; Swift's October update noted most participating banks were using the ledger for 24-hour real-time payments, involving EUR, GBP, HKD, SGD, and USD in interbank settlements, corporate finance, and liquidity management cases.
Brahimi noted that banks already issuing or managing digital assets would find adding required features easier. This aligns with Taurus's August announcement of Swift ledger integration, offering platform capabilities for ledger connection, wallet management, tokenization, and smart contracts. Details on whether multiple vendors are needed or actual implementation costs and timelines remain undisclosed.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: Swift 원장 연결엔 은행 자체 원장·지갑 기능 필요