DBS and Citi Complete Weekend USD Payment With Tokenised Deposits on Swift Digital Ledger

DBS and Citi completed a weekend USD payment between Singapore and the U.S. using tokenised deposits through Swift's Digital Ledger.

DBS and Citi Complete Weekend USD Payment With Tokenised Deposits on Swift Digital Ledger — editorial cover artwork
DBS and Citi Complete Weekend USD Payment With Tokenised Deposits on Swift Digital Ledger — editorial cover artwork

DBS and Citi completed a cross-border U.S. dollar payment between Singapore and the United States on Saturday, September 5 using tokenised commercial-bank deposits and Swift's blockchain-based ledger.

DBS announced the transaction on September 7 and said it completed in minutes. The bank contrasted that with a conventional cross-border process that can take up to two business days when time zones and weekends intervene. The test demonstrates a specific weekend payment capability; it does not establish unrestricted 24/7 availability for all DBS or Citi customers. DBS.

The ledger's role also needs a precise boundary. Citi describes it as enabling instant payment commitment through tokenised deposits, with final settlement relying on existing settlement models, including real-time gross settlement systems. The payment was part of a controlled proof-of-concept phase running from July through December 2026, not a finished global service. Citi.

The money remained a bank deposit

The transaction did not use a third-party stablecoin. Tokenised deposits are digital representations of commercial-bank money: the underlying claim remains against a bank rather than against a separate stablecoin issuer.

That distinction affects credit risk, regulation, redemption and balance-sheet treatment. A tokenised deposit can gain some programmability and extended operating hours while keeping the customer inside the commercial banking system.

Swift's ledger provided common infrastructure for payment commitments between banks. It coordinated the tokenised liabilities, but final settlement still used established systems. Calling the complete flow “onchain settlement” would therefore erase an important operational step.

Saturday is the important part

Cross-border bank payments are not slow only because messages move slowly. Operating windows, liquidity availability, correspondent relationships and cut-off times all affect when a payment can complete.

Stablecoins have gained enterprise attention partly because public blockchains continue operating outside normal banking hours. A corporate treasury can move a stablecoin on a Saturday even when a conventional bank transfer would wait for the next business day.

The DBS–Citi transaction shows banks can reproduce part of that availability with tokenised deposits and a shared coordination layer. It does not prove production-scale access, but it narrows the technical gap between commercial-bank money and blockchain-native dollars.

The result also makes the competitive question more specific. Corporates may not always have to choose between deposits with established banking relationships and stablecoins with longer operating hours. Banks could extend the usable hours of deposits while retaining the settlement systems that give transactions legal and operational finality.

Commitment and final settlement are separate

A payment commitment tells participating banks what should move and records the obligations created by the transaction. Matching those commitments on a common ledger can make the interbank state visible and coordinated.

Final settlement is the point at which those obligations are discharged with finality. Citi says the Swift model leverages existing settlement arrangements, including RTGS, for that step. The blockchain ledger is therefore an orchestration and commitment layer within a hybrid flow.

That architecture may be commercially useful. It can preserve existing regulated money and settlement models while improving how banks coordinate outside traditional windows. It also means the system inherits practical constraints from both layers: the ledger must operate continuously, and the final-settlement rails must be available and funded when obligations need to be discharged.

A successful payment is not yet a complete service

Banks still need rules for funding, liquidity, exception handling, reconciliation and legal finality across jurisdictions. Corporate customers need to know which entities can participate, what limits apply, what happens if a transaction fails and when a tokenised balance can be converted back into ordinary account money.

The September 5 payment is stronger evidence than a proposed architecture, but it remains one transaction inside a time-bounded proof of concept. Repeated transactions, disclosed eligibility and a production launch will show whether the model becomes a broad bank payment service.

Clarification, September 13, 2026: This article now distinguishes payment commitment on Swift's ledger from final settlement through existing systems and records Citi's July–December 2026 proof-of-concept window. The canonical slug and original publication date are unchanged.

Sources