DBS and Citi Move Tokenized Dollars Across a Weekend
A Singapore-to-New York payment settled in minutes on Swift’s Digital Ledger, testing regulated bank money outside traditional operating hours.
DBS and Citi have completed the first weekend US-dollar payment between Singapore and the United States using tokenized bank deposits on Swift’s Digital Ledger. The transaction, executed on September 5 between DBS and Citi’s New York office, settled in minutes instead of waiting as long as two business days for traditional cross-border processing.
The result is more than a faster message. Tokenized deposits represent claims on regulated commercial banks, while Swift’s ledger coordinates movement between institutions. That design aims to provide round-the-clock settlement without requiring corporate users to hold a public stablecoin or manage a new issuer relationship.
For treasury teams, weekend and time-zone gaps create real costs. Cash can sit unavailable while supplier obligations, margin requirements and digital commerce continue. Faster movement can reduce precautionary balances and improve control over liquidity and foreign-exchange exposure.
DBS said half of finance leaders in its survey are exploring blockchain capabilities for liquidity and FX management. Asia’s outbound cross-border payments are forecast to rise from $13.5 trillion in 2025 to $24 trillion by 2033, according to a Money20/20 and FXC Intelligence report cited by the bank. Those figures describe potential demand, not adoption of this particular rail.
The payment was the second confirmed live transaction on Swift’s ledger after an earlier HSBC–Standard Chartered transfer. Swift launched the pilot in July with 17 banks across six continents; DBS is the only Asian-headquartered institution in the 12-bank core design group.
Interoperability is the central challenge. Individual banks have built proprietary token systems, but bilateral connections do not scale cleanly across thousands of institutions. Swift’s advantage is its existing network and rule-making relationships. Its ledger must prove that it can coordinate tokenized value while preserving compliance, finality and operational resilience.
The pilot does not yet establish commercial scale. Public disclosures omit the payment amount, pricing, liquidity model and exception-handling process. A successful single transaction says little about throughput, cyber resilience or how the system behaves when sanctions screening, mistaken instructions or a participant outage interrupt the flow.
Tokenized deposits also preserve bank credit exposure. They may be technologically different from conventional account balances while remaining economically dependent on the issuing bank. Corporate users must understand redemption, legal finality and whether tokens move across banks or are extinguished and reissued through coordinated ledgers.
Why it matters
The test brings tokenization into a practical corporate-finance problem: moving regulated dollars when conventional rails are closed. If repeated at scale, it could free working capital and reduce the gap between always-on commerce and limited banking hours.
It also sharpens competition between bank deposits, stablecoins and wholesale central-bank-money projects. Swift is showing that incumbent infrastructure can incorporate distributed ledgers instead of being displaced by them. Banks retain the customer and balance-sheet relationship while gaining programmable settlement.
The next proof points are production volumes, additional currency corridors, transaction costs and common legal standards. Until then, the correct description is a successful live milestone—not a completed replacement for correspondent banking.