Taurus says banks must bring three systems of their own to join Swift's tokenized-deposit ledger

"If you want to connect today to the Swift ledger, you need three things," Lamine Brahimi, co-founder and managing partner of Taurus, said in an interview with CoinDesk ^[6][10]. "You need your own permissioned ledger that interacts with that of Swift, you need wallet capabilities, and you also need tokenization and smart-contract capabilities to be able to integrate the Swift smart contracts." ^[6] Taurus sells all three layers through one platform, and Brahimi said competing vendors may make a bank use several firms to cover the same ground ^[11]. In this reporting, the most detailed list of what a bank must acquire to join comes from a firm that sells it ^[6][11].

Swift has built the coordination piece: a ledger that moves tokenized deposits across borders at any hour, while final settlement keeps running through existing arrangements ^[1]. The tokens, wallets and contracts stay with each bank ^[7]. The cost of joining is therefore paid once per participant, or rather once per participant without a digital-asset operation, since Brahimi said the extra technology is not necessarily a major hurdle for banks already issuing or managing digital assets ^[2]. According to CoinDesk, Swift's messaging network still dominates money movements of up to $1.5 quadrillion a year, and the ledger is its first move to modernize a system that has led bank messaging since the 1970s ^[15].

Swift said in July that 17 banks were preparing live tokenized-deposit transactions ^[8]. Four have since been reported live. HSBC and Standard Chartered ran the first interbank transaction in August, and DBS and Citi then sent a weekend dollar payment that settled in minutes, against up to two business days on the old route ^[9]. That leaves at least 13 of the 17, or at least three banks in four, with no live transaction reported ^[16][17].

The 13 can go one of three ways. If they already run digital assets, the three layers cost them little and the vendor market the requirement opens is small ^[2]. If they lack the stack and buy it, Taurus's one-platform offer competes with assembling several vendors ^[11]. If they build in-house at their own pace, the live count stays near four. I'd expect the second, partly on Brahimi's own evidence. "Tokenized deposits until Swift's announcement were barely used," he said. "They were mostly used by huge banks like JPMorgan, because they had such a big global scale." ^[14]

The counter-case is that banks have run internal tokenized-deposit systems for years ^[12]. Some of the stack may already sit inside banks that had no compatible counterparty, since moving money between institutions needs shared standards and compatible systems on both ends ^[12]. If the remaining banks go live within months without announcing vendor integrations, the counter-case is right and most of the build was done before Swift asked for it.

Swift's model keeps deposits on bank balance sheets, distinguishing them from stablecoins issued outside the banking system ^[13]. A bank that pays for the three layers gets weekend cross-border dollar transfers without moving money off its own books, and, as Brahimi described it, without abandoning its existing infrastructure ^[9][13][4]. He called the ledger an early-stage product and said the extra infrastructure should not be read as a weakness in Swift's design ^[5]. "I think it's a good move," he said. "That provides the choice." ^[3]