The ledger nets, the old rails settle
Singapore's three largest banks paid each other in tokenised deposits for the first time. The shared ledger matched the obligations; the money still moved the old way.
A tokenised deposit has had one practical limitation since banks began issuing them. A corporate client could send one to another client of the same bank, and to nobody else, which made the token a faster internal transfer rather than a new form of money.
Singapore's three largest banks have now closed that gap between themselves. DBS, OCBC and UOB said on 10 September that they had completed live domestic Singapore dollar transactions using tokenised deposits on Swift's blockchain-based ledger, the first time the three have executed interbank payments that way.
The mechanics deserve a careful reading, because they are more modest than the headline and more useful. The banks exchanged payment messages over Swift's ledger. The resulting obligations were recorded as tokenised deposit obligations on each bank's own infrastructure. Swift's platform acted as what the release calls an orchestration layer, matching and netting those obligations between the banks "prior to final settlement through existing systems".
In other words, the ledger did the coordination and the conventional rails did the settlement. Nothing about that is a failure. It is how a new system is introduced into payments that cannot be allowed to break: run the new layer on top, keep finality where the law and the central bank already recognise it, and move settlement across only once the layer has earned it.
It also clarifies what the industry is actually building. The hard problem in tokenised money was never issuing a token; banks have shown repeatedly that they can do that on their own. The hard problem is getting tokens issued by competing banks to mean the same thing to each other, and a neutral message network that every bank already uses is the obvious candidate to solve it.
That is why Swift, rather than a consortium chain, is where this landed. Ledger Insights describes Swift's ledger as Singapore's de facto interoperability layer for tokenised deposits, and the incumbent network's advantage is the one incumbents usually have: the connections already exist.
The banks' own descriptions point to the use case they expect to sell. Rachel Chew, co-head of digital assets in DBS's transaction services business, said clients "can transact USD and SGD payments any time, any day, including over a weekend". UOB's So Lay Hua said the bank had "expanded from Hong Kong dollar to Singapore dollar and US dollar transactions beyond traditional banking hours".
Weekend corporate payments are a real product, and they expose the limit of the current design. Netting can run around the clock; final settlement through existing systems runs when those systems do. A payment matched on Saturday that settles on Monday is an improvement in certainty, not in finality, and treasurers will price the difference.
The regulatory question is less open than it was a week ago. Canada's supervisor confirmed on 10 September that a tokenised deposit is legally a deposit, which is the premise every bank in this kind of arrangement is relying on, and on the same day Singapore's banks demonstrated the plumbing that makes the premise useful.
The live transactions follow Swift's announcement in July that 17 banks across six continents were preparing to transact in tokenised deposits on the ledger. Ledger Insights reports that the three banks had already made cross-border transactions in recent weeks; this is their first domestic one. The test that matters is the second step: the day final settlement moves onto the ledger as well, which is the day this stops being a better message and becomes different money.