Updated September 8, 2026. This was an institutional payment, not a service already available to every retail customer.
Tokenized deposits have moved from design to a live transaction. DBS and Citi completed a Singapore-US dollar payment on September 5 during the weekend, using tokenized deposits and the Swift Digital Ledger. DBS says settlement took minutes rather than waiting for as long as two business days.
The event was not a Bitcoin transfer, a privately issued stablecoin payment or a central bank digital currency. The value remained a dollar-denominated bank liability represented and coordinated through shared digital infrastructure between regulated intermediaries.
What tokenized deposits are
A conventional deposit is a claim by a customer on their bank. A tokenized deposit represents that relationship on a programmable ledger so transfer and verification can follow automated rules. Tokenisation does not turn it into central-bank money.
The identity of the debtor is the defining difference. A tokenized deposit remains tied to the issuing institution and account terms. A stablecoin is issued by a private company under its reserve and redemption structure, while a CBDC would be a direct liability of a central bank.
Two tokens nominally worth one dollar therefore need not carry the same legal rights. Issuer, redemption, protection, access and operating hours may differ, just as real shares and tokenized representations can expose holders to different claims.
How the DBS-Citi payment worked
The official DBS announcement says the transaction took place on Saturday, September 5 between DBS in Singapore and Citi’s New York office. The bank describes it as the first successful weekend dollar payment between the two markets.
Swift’s Digital Ledger supplied the shared infrastructure coordinating the operation. That does not mean dollars moved over a public blockchain or that anyone can inspect the balances. The environment is designed around participating institutions and banking requirements.
The comparison with up to two business days captures the friction created by time zones and operating calendars. It is not a guarantee that every future international payment will settle within minutes. Currency, compliance checks, correspondent arrangements and jurisdictions can alter the path.
Why the weekend matters
Digital markets often remain open while international bank money encounters operating windows and systems that do not always settle in real time. A payment initiated on Saturday may therefore wait until the necessary institutions and rails reopen.
Making tokenized deposits available 24/7 reduces that mismatch. A company could pay a counterparty or fund a position when required rather than waiting until Monday. The benefit only exists when both institutions and the relevant currency are supported by compatible infrastructure.
Continuous availability brings an operational obligation as well. Monitoring, anti-money-laundering controls, exception handling and support need to function outside conventional hours. Always on does not mean controls are removed.
What Swift’s ledger contributes
Swift announced in July that its blockchain ledger was ready for initial use with 17 banks. The aim is to connect tokenized deposit systems without requiring every institution to build an isolated bilateral network.
Swift describes the ledger as validating and synchronising interbank payment commitments while confirming that funds are available before execution. That orchestration goes beyond a basic message because it coordinates the shared state required for value to move.
The design does not remove banks. It attempts to make bank money programmable while retaining institutional identity, compliance and balance sheets. It is an institutional answer to always-open digital rails, not automatic adoption of a permissionless crypto model.
Tokenized deposits versus stablecoins
A stablecoin can circulate between wallets and protocols on a public blockchain, often without a direct relationship between the holder and the issuer’s bank. That accessibility supports composability, but adds contract, issuer, network and redemption-intermediary risks.
A tokenized deposit keeps a more direct link to the holder’s bank. It may integrate better with corporate controls and treasury processes, but remain restricted to authorised participants. The choice is not only about speed; it depends on who sends value, who receives it and what claim remains at completion.
Our tokenized-asset platform checklist applies here: identify issuer, custodian, legally authoritative record and the process for correcting an error. The word token does not make different instruments equivalent.
What changes for companies and crypto markets
Companies may gain payment and liquidity management hours that better match a digital economy. Faster settlement can reduce trapped working capital, but the benefit needs measurement through real volume, total cost and completion rates rather than one successful demonstration.
For crypto markets, the transaction confirms that banks are adopting parts of on-chain architecture without necessarily using public stablecoins. That creates competition in institutional payments and possible interoperability opportunities. It does not prove that bank deposits and crypto assets will merge into one open market.
| Instrument | Liability of | Typical access |
|---|---|---|
| Tokenized deposit | Commercial bank | Authorised clients and institutions |
| Stablecoin | Private issuer | Supported wallets and platforms |
| CBDC | Central bank | Defined by the public programme |
| DBS-Citi payment | USD bank deposits | Institutional Swift transaction |
The next test for tokenized deposits is not another isolated demonstration but expansion across banks, currencies, customers and transaction types. Cost, uptime and exception data will matter. DBS and Citi have shown that bank dollars can cross a weekend in minutes, not that every global payment is already instant.
