DBS and Citi complete weekend USD payment via Swift's digital ledger using tokenized deposits

Singapore-based DBS Bank and U.S. Lender Citigroup completed a tokenized U.S. Dollar payment over the weekend using the digital ledger operated by global interbank messaging network Swift. The transfer is the second confirmed live use of Swift's blockchain-based settlement infrastructure, a system the cooperative launched in 2025 to keep cross-border bank payments competitive with always-on alternatives such as stablecoins and central bank digital currencies.

What is Swift's digital ledger and why does it matter now?

Swift's digital ledger is a permissioned, shared infrastructure layer that runs alongside the cooperative's long-standing interbank messaging service. Instead of moving cash through a chain of correspondent banks, participating institutions can settle tokenized claims on a shared ledger, with each transfer synchronized across counterparties in near real time. The launch followed years of pilots, including work with Chainlink, the Ethereum-compatible Linea network, and a string of central banks exploring tokenized interbank settlement.

The weekend test matters because most bank-to-bank payment systems still pause on Saturdays and Sundays. Tokenized deposits on a shared ledger do not require a weekend pause, which is what makes the new rail directly competitive with stablecoin networks and the always-on settlement plans being built around wholesale CBDCs. According to the source, the latest payment is the second confirmed live use of the ledger, a sign that the infrastructure is moving past pilots toward recurring bank-to-bank traffic.

Why is DBS and Citi's weekend test significant?

The pairing of DBS, one of Southeast Asia's largest banks, with Citigroup, one of the most active U.S. Dollar correspondents globally, is significant because it demonstrates that the new ledger can carry flows between institutions on opposite sides of the Pacific and across the weekend FX window. Tokenized deposits, in this setup, represent a digital claim on a commercial bank's reserves that can be moved on-chain without giving up the regulated banking relationship that underlies the deposit.

For treasurers, the implication is that a Friday evening transfer no longer needs to wait until Monday morning to clear at the receiving bank. For the broader financial plumbing, the test shows that a shared, bank-operated ledger can function as an additional rail layered on top of, rather than replacing, the existing correspondent model. That positioning is central to Swift's pitch to its more than 11,000 member institutions.

How does this fit the broader tokenized payments race?

Tokenized deposits sit between two well-known alternatives. On one side are stablecoins, which are issued by private entities, settle continuously, and have grown into a multi-hundred-billion-dollar market used for both crypto trading and cross-border remittances. On the other are wholesale CBDC projects, in which a central bank issues a digital liability that commercial banks can use for settlement; the European Central Bank, the Bank of England, the Federal Reserve, and the Monetary Authority of Singapore have all explored pilots in this area.

Swift's bet is that banks will prefer a shared, cooperative utility that preserves their role as deposit issuers rather than routing more value through stablecoins or central-bank-issued tokens. The bank-owned cooperative has stressed that the digital ledger is designed to interoperate with public chains and with other tokenization initiatives, including those involving central banks. Live weekend traffic gives that vision its first stress test outside business hours.

What did the first live transfer on the ledger look like?

The earlier live use of the ledger, reported prior to this weekend's payment, also used tokenized dollar claims between participating institutions. Together with the DBS and Citi transfer, the two transactions suggest the system is being used for real client flows rather than sandbox demonstrations. Swift has framed each live transaction as a milestone toward a production rollout, with the cooperative's leadership arguing that banks need a common settlement layer before tokenized money fragments across dozens of proprietary platforms.

The progression also reflects the cooperative's response to criticism that legacy interbank rails are slow and opaque. By tying settlement to a shared ledger, Swift is trying to show that bank money can move with the speed and transparency of digital asset transfers while remaining inside the regulatory perimeter that governs commercial bank deposits.

What are the risks and what to watch next?

The biggest near-term risks are operational rather than technological. Banks must reconcile on-chain tokenized balances with their core reserve ledgers, comply with anti-money-laundering rules on every transfer, and resolve legal questions about whether a tokenized deposit has the same legal status as a traditional deposit. Swift and its members also need to confirm that the ledger can scale to the message volumes, currently above 40 million per day, that the cooperative's network already handles.

Catalysts to monitor include further named live transactions by other G-SIBs, technical disclosures on throughput and finality, and any guidance from the Bank for International Settlements on how tokenized commercial bank money should be classified under its unified ledger roadmap. The speed at which DBS, Citi, and their peers move from a second confirmed live payment to daily weekend volume will be the clearest signal of how seriously the banking industry is treating the new rail.

What does this mean for crypto markets?

For crypto traders, the relevant signal is competitive pressure rather than direct exposure. A working tokenized deposit rail on a cooperative network could siphon some cross-border payment volume away from USD-pegged stablecoins, which today dominate that use case. At the same time, the same infrastructure is being designed to interoperate with public chains, which could keep stablecoins and tokenized bank deposits complementary rather than substitutes.

For institutional desks, the broader trend is convergence: regulated banks are now operating the same kind of always-on, programmable settlement that crypto-native firms have used for years. That convergence is likely to keep drawing traditional finance participants into tokenization projects, while keeping the question of which balance sheet ultimately settles the transfer, a bank, a stablecoin issuer, or a central bank, firmly on the regulatory agenda.