Digital asset infrastructure provider Taurus said August 26 Wednesday that it has connected its tokenization and custody platforms to Swift’s blockchain-based shared ledger. 

The integration gives financial institutions a route to use bank-issued tokenized deposits for round-the-clock cross-border payments.

The first client connections are expected within days. Initial distributed ledger transactions are planned within weeks.

How Taurus Wires Into Swift’s Ledger

Taurus-PROTECT handles programmable wallet and key management, including governance rules, approval workflows, and API-based automation. Taurus-CAPITAL manages the issuance of bank-issued tokenized money while keeping deposits on the issuing bank’s own balance sheet.

Banks without existing blockchain infrastructure can use managed Hyperledger Besu environments and Ethereum Virtual Machine connectivity supplied by Taurus. Institutions that already run Besu or another EVM-compatible system can connect Taurus’s tokenization and wallet tools directly to their existing nodes.

Existing Taurus clients can extend infrastructure already in production. That gives Swift member banks a route into tokenized deposits without building the infrastructure themselves.

Deposits Stay on Bank Books, Not Swift’s

Swift’s shared ledger works as an orchestration layer between participating institutions. It coordinates transfers of tokenized deposits before final settlement takes place through existing arrangements like real-time gross settlement systems.

Bank-issued deposits remain on each institution’s own ledger, and Swift coordinates their movement between participants. Payments can run overnight and on weekends, extending availability beyond the overlapping business hours that limit traditional cross-border transfers.

That structure is what separates tokenized deposits from stablecoins. The underlying money stays inside the commercial banking system and under existing banking regulation, rather than moving into a separate token structure. Standard Chartered and HSBC have already completed the ledger’s first live cross-border transaction under this model.

The 40-Bank Network Behind the Rollout

Swift moved its shared ledger into initial deployment in July after roughly nine months of development. Seventeen banks across six continents began testing tokenized deposit payments when the controlled rollout started on July 9, including HSBC, Citi, BNP Paribas, UBS, ANZ, DBS, and Standard Chartered.

More than 40 financial institutions helped design the system. Swift’s existing network already connects more than 11,500 financial institutions and companies across more than 200 markets.

Taurus co-founder and managing partner Lamine Brahimi said financial institutions need digital asset infrastructure that can work securely with systems they already operate. He framed the Swift connectivity as a way for banks to extend into tokenized deposits and cross-border payments while keeping control of their own infrastructure.

Reading This as an Institutional Adoption Signal

Taurus bank access integration is a data point worth weighing alongside other institutional infrastructure moves. Taurus already runs in production for clients including Deutsche Bank, State Street, Santander, and CACEIS, and Deutsche Bank backed the firm in a $65 million funding round.

The Swift ledger itself does not create a new investable asset. It is plumbing that could shape how quickly banks move tokenized deposits and settlement infrastructure into daily use, which matters for anyone assessing the broader thesis that institutional adoption, not retail speculation, drives the next phase of crypto infrastructure demand.

Next Milestones: First Clients, First Transactions

Taurus expects its first Swift-connected clients within days and the first live DLT transactions on the ledger within weeks. Watch for which banks announce transactions first, and whether Swift expands its 17-bank pilot group as the rollout continues.

This is not financial advice. Institutional infrastructure announcements do not guarantee adoption timelines or outcomes, and details can change as pilots progress.

What this means for you: if you’re evaluating how seriously traditional banks are building digital asset infrastructure, this integration shows Swift’s tokenized deposit ledger moving from pilot to active bank onboarding. It is a signal worth tracking alongside your own portfolio exposure to institutional-adoption-linked assets rather than a reason to change your holdings today.