Swift has introduced a blockchain-based ledger that enables 24/7, cross-border movement of tokenized deposits. While the system can settle transactions in minutes, even on weekends, it is designed to sit on top of existing banking infrastructure rather than supplant it.
Core requirements for banks
According to Lamine Brahimi, co-founder of custody and tokenization firm Taurus, banks that wish to link to Swift’s ledger must satisfy three prerequisites. First, they need a private, permissioned ledger that can interoperate with Swift’s chain. Second, a digital-asset wallet capable of holding tokenized funds is essential. Third, the ability to tokenize assets and execute smart contracts is required to interact with Swift’s smart-contract layer. Brahimi stresses that these components are not optional; without them a bank cannot participate in the new network.
How the ledger fits into existing workflows
Swift positions the ledger as an orchestration layer that moves tokenized deposits between institutions while final settlement continues through traditional arrangements. Deposits remain on the banks’ balance sheets, differentiating them from stablecoins issued outside the regulated banking system. The design gives banks the option to maintain current payment rails and, simultaneously, offer round-the-clock tokenized payments.
Early adopters and live demonstrations
In August, HSBC and Standard Chartered executed the first interbank transaction on Swift’s ledger. Subsequent tests by DBS and Citi showed a weekend cross-border dollar payment completed in minutes, a stark contrast to the two-day window typical of conventional settlement. Swift reported that 17 banks are preparing to run live tokenized-deposit transactions, signalling the first wave of adoption for the technology.
Industry response and infrastructure providers
Brahimi notes that the need for additional technology should not be seen as a flaw in Swift’s design. He argues that banks already issuing or managing digital assets will find the three-layer requirement manageable. Taurus, which announced its Swift integration in August, offers a single platform that bundles a permissioned ledger, wallet management tools, and tokenization plus smart-contract software. Competitors may force banks to source each capability from separate vendors, potentially increasing complexity.
Why it matters
Swift’s ledger introduces a standardized method for banks to exchange tokenized deposits around the clock, expanding the utility of existing balance-sheet assets without abandoning legacy settlement mechanisms. The requirement for banks to build out permissioned ledgers, wallet capabilities, and tokenization infrastructure creates a new market for technology providers while setting a higher bar for participation. As early adopters demonstrate rapid settlement on weekends, the broader banking sector will need to evaluate whether the operational investment aligns with strategic goals for 24/7 payments.
