DBS and Citi Complete First Weekend Payment via Swift's Tokenized Deposits

DBS and Citi completed the first cross-border weekend dollar payment between Singapore and the United States on September 7, 2026. The money did not travel through the usual network of correspondent accounts. Instead it moved through tokenized deposits on Swift's new digital ledger.

What exactly did DBS and Citi do?

Singapore's DBS Bank and America's Citi carried out an operation that banks typically push to Monday. The payment happened on a weekend, when classic settlement systems sit idle because clearing houses are closed and correspondent banks are off duty.

According to CoinDesk, the transaction marked the second confirmed live use of Swift's blockchain-based ledger, not a test pilot. Earlier experiments were limited to a small circle of participants. This time funds actually crossed the border between two jurisdictions on a weekend rather than a regular business day.

Swift serves more than 11,000 banks and financial institutions worldwide, so even one successful transfer between DBS and Citi matters for the whole network. The company has been testing the digital ledger with a group of partner banks for over a year, but this transaction was the first carried out with real client funds rather than inside a closed test.

The Singapore-US corridor was not picked at random. Billions of dollars in trade finance and corporate settlements flow through it daily, and any weekend delay means frozen liquidity for businesses for two or three days. For companies trading across time zones, that gap is real money.

How do tokenized deposits work?

A tokenized deposit is not a new currency or a stablecoin. By design it is the same dollar sitting in a client's account, only recorded as a digital token on a shared ledger. The issuing bank guarantees the token can always be redeemed for regular funds at a one-to-one rate.

The difference from a classic wire lies in how confirmation works. Instead of waiting for a message to travel through a chain of correspondent banks, each adding its own delay and fee, the token moves directly from one ledger participant to another. The ledger records the movement instantly. That is exactly why the operation could happen on a weekend at all.

Unlike public blockchains, where anyone can settle a transaction, Swift's ledger is permissioned: only vetted banks that connected to the platform get access. That combines blockchain-style speed with the kind of oversight regulators and compliance teams already expect.

Why do payments still stop on weekends?

A classic SWIFT payment between banks in different countries passes through a chain of intermediaries, and each one runs on its own operating schedule. If a payment arrives on Friday evening, it physically cannot move further until the next bank in the chain opens its office on Monday.

The schedule of bank staff is not the only reason. Many internal bank systems still process payments in batches once or twice a day, and anti-money-laundering and sanctions checks are traditionally tied to compliance teams' working shifts. Rebuilding that architecture is harder than simply letting someone work on a Saturday.

This is exactly the gap banks are trying to close. Crypto assets like Bitcoin or stablecoins such as USDT have moved between wallets on any Saturday or Sunday for years, and users got used to it. Traditional banks had to admit the obvious: if customer money waits for the weekend while the crypto market does not, some payments will simply go where it is more convenient.

Why is Swift building its own blockchain ledger?

Swift has remained the standard for interbank messaging for more than forty years. Yet the network itself does not move money. It only carries instructions between banks, while the actual movement of funds always depended on correspondent banks and their working hours. The new digital ledger changes exactly that part of the system.

• Shared ledger: participating banks keep records of tokenized deposits on one platform instead of separate internal systems.
• Each bank issues its own tokens, backed by real funds held in its accounts.
• A transfer between banks looks like a direct token movement rather than a chain of messages through intermediaries.
• The ledger runs without being tied to the working hours of a specific branch or clearing house.

So far only a handful of large banks have joined the project. Scaling it up will take years, since it needs regulatory trust, agreed operating rules, and willingness from other financial institutions to join the shared ledger. At the same time, some large banks are building their own tokenized settlement systems on the side, so Swift is competing not only with crypto rails but with its own members.

Will banks catch up to crypto market speed?

One successful transaction between DBS and Citi does not mean weekend payments will become the norm overnight. But it points to a direction. Banks are willing to build infrastructure that not long ago looked like exclusive crypto territory.

The main obstacle now is organizational rather than technical. A token from one bank has to be just as trustworthy and interchangeable as a token from another, or ledger participants simply will not trust each other's issuances. Regulators in different countries still need to agree on common rules, and that process always moves slower than writing code.

Other players have shown a similar push toward round-the-clock settlement, such as the Kraken and SoFi partnership around the SoFiUSD stablecoin. The faster traditional banks close the weekend gap, the fewer reasons customers will have to look for alternatives outside the familiar banking system.