DBS, OCBC and UOB Complete Live SGD Tokenised-Deposit Transactions on Swift Ledger
Singapore's three local banks used Swift's ledger to match and net tokenised-deposit obligations before final settlement through existing systems.
DBS, OCBC and UOB said on September 10 that they had completed live domestic Singapore-dollar transactions using tokenised deposits and Swift's blockchain-based ledger. The three banks described them as Singapore's first live interbank transactions using tokenised deposits.
The important qualification sits in the transaction mechanics. Swift carried payment messages, matched and netted the resulting obligations, while final settlement took place through existing systems. The trial therefore demonstrates coordination between three bank-issued forms of digital money; it does not establish that Singapore's domestic settlement system has moved onto a blockchain or that the service is generally available to customers. DBS, OCBC and UOB.
Three bank liabilities met on one coordination layer
A tokenised deposit remains a claim on the bank that issued it. When customers at different banks transact, the institutions still need a common way to recognise what each bank owes and settle the net positions between them.
According to the joint release, UOB, DBS and OCBC exchanged payment messages through Swift's ledger. The resulting obligations were recorded on each bank's own tokenised-deposit infrastructure. Swift then acted as the orchestration layer that matched and netted those obligations before final settlement through existing systems.
That division of work matters. The shared ledger did not turn three separate deposits into one common stablecoin. Each bank continued to maintain its own liability, while Swift supplied the interbank coordination needed to make those liabilities interoperable.
It is also narrower than an all-onchain settlement claim. Matching and netting can shorten the path to settlement and provide a shared record of payment commitments, but legal finality still depends on the existing settlement layer described by the banks.
Domestic SGD adds a different test from the USD pilots
The Singapore-dollar transactions follow earlier work on the same Swift ledger in U.S. dollars. Those cross-border tests examined whether banks could move tokenised deposits across jurisdictions and outside traditional operating windows.
This event is domestic and same-currency. There is no foreign-exchange conversion in the reported flow. Its value is in connecting the tokenised-deposit systems of Singapore's three local banks rather than in proving a new SGD trading or cross-border corridor.
The distinction helps show where interoperability becomes operationally important. A corporate balance at DBS, OCBC or UOB may remain a deposit at that bank, but a payment to another institution creates an obligation that has to be recognised, matched and settled. A shared ledger can coordinate that process without requiring the banks to issue a single jointly backed token.
“Live” does not mean general customer availability
The banks said the transactions were live, which is stronger evidence than a simulation or design paper. The release does not disclose the transaction amounts, exact execution date, fees, participating customers, production scale or a date for commercial availability.
It says the technology could support round-the-clock interbank payments and future services in corporate treasury, trade and digital commerce. Those are potential use cases, not announced products.
The banks also attribute a first to the transactions. That description should remain attached to their announcement because the release is the only inspected evidence for the claimed market first.
The next test is repeatable settlement
The trial has demonstrated that three banks can exchange and reconcile tokenised-deposit obligations through a common ledger. The next evidence needs to show how the model behaves repeatedly: how liquidity is funded outside normal windows, how exceptions are handled, what operational limits apply and when eligible corporate customers can use it.
The boundary between orchestration and settlement will remain central. A shared ledger can make obligations visible and coordinated around the clock, but the commercial service is not complete until banks can fund and settle those obligations reliably through the systems that confer finality.