In a notable milestone for the financial‑technology sector, two major banks—DBS Group and Citi—successfully completed a United States‑dollar payment over the weekend using Swift’s Digital Ledger (SDL). The transaction, which leveraged tokenised deposits as the underlying settlement instrument, represents the second confirmed live use of Swift’s blockchain‑enabled ledger. It underscores the growing momentum behind distributed‑ledger technology (DLT) in the realm of cross‑border and high‑value payments, and it signals a clear intention by Swift to challenge newer, always‑on digital payment rails that promise instant settlement and 24/7 availability.
## Background and significance Swift, the global messaging network that has long served as the backbone for international bank‑to‑bank communications, introduced the Digital Ledger in 2022 as a collaborative effort with a consortium of banks, technology firms, and regulators. Unlike the traditional Swift messaging system, which merely transmits payment instructions, the Digital Ledger provides a shared, immutable record of transactions that can be used for real‑time settlement. By tokenising fiat currency—converting cash into a digital representation that can be moved on a blockchain—the SDL aims to combine the security and finality of blockchain with the regulatory compliance and risk controls required by banks. The first live deployment of the SDL was demonstrated earlier this year when a consortium of banks executed a multi‑currency settlement using tokenised euros and dollars.
The recent DBS‑Citi transaction builds on that proof‑of‑concept, showing that the platform can handle weekend processing—a period when legacy payment systems such as SWIFT gpi and traditional correspondent banking networks are typically offline. This capability is crucial for businesses that operate across time zones and need to move funds without waiting for the next business day.
## How the transaction worked The payment involved a USD 10 million transfer from a corporate client of DBS in Singapore to a supplier based in New York. Here is a step‑by‑step breakdown of the process: 1. **Initiation**: The corporate client instructed DBS to make the payment.
DBS created a tokenised USD deposit on the SDL, effectively locking the equivalent amount of fiat dollars in a regulated custodial account. 2. **Tokenisation**: The USD deposit was converted into a digital token that represents a claim on the underlying cash.
This token is recorded on the shared ledger, visible to all participants who have permission to view the transaction. 3. **Transmission**: Using Swift’s messaging standards, DBS sent a payment instruction to Citi, attaching the token identifier and the settlement details.
Because the SDL is a distributed ledger, both banks could instantly verify the token’s existence and ownership. 4. **Verification and compliance**: Both institutions ran automated compliance checks, including anti‑money‑laundering (AML) and sanctions screening, directly on the ledger data.
The immutable nature of the record simplifies audit trails and reduces the risk of data manipulation. 5.
**Settlement**: Citi accepted the token, which triggered the release of the corresponding fiat dollars from the custodial account to the New York supplier’s bank account. The token was then burned, ensuring that the digital representation could not be double‑spent.
6. **Confirmation**: Both banks received real‑time confirmation of settlement, and the corporate client received a digital receipt that could be reconciled instantly with its accounting system.
The entire workflow was completed within minutes, despite the transaction occurring on a Saturday when most traditional clearing houses are closed. This demonstrates the SDL’s ability to provide continuous, real‑time settlement, a feature that is increasingly demanded by multinational corporations and fintech platforms. ## Implications for the payments ecosystem The successful weekend settlement has several broader implications: - **Competitive pressure on existing rails**: Legacy systems such as SWIFT gpi, ACH, and SEPA operate on business‑day schedules and often involve multiple intermediaries, leading to longer settlement times and higher fees.
By offering 24/7 settlement with comparable security, SDL positions itself as a viable alternative. - **Regulatory acceptance**: Tokenised deposits must be backed by actual fiat reserves held in regulated custodial accounts. The involvement of major banks like DBS and Citi, both of which are subject to stringent supervisory oversight, signals that regulators are comfortable with this model, provided proper safeguards are in place.
- **Operational efficiency**: The shared ledger eliminates the need for duplicate reconciliations across correspondent banks, reducing operational costs and the potential for errors. Real‑time visibility also enhances liquidity management for corporates, who can better forecast cash flows. - **Scalability and future use cases**: While the current demonstration focused on a single USD payment, the architecture can be extended to multi‑currency settlements, trade finance, and even central bank digital currencies (CBDCs).
The tokenisation framework is agnostic to the underlying asset, meaning that once the infrastructure is in place, banks can issue tokens for euros, pounds, yen, or any other sovereign currency. ## Challenges and next steps Despite the promising results, several challenges remain before SDL can achieve mainstream adoption: - **Interoperability**: For the ledger to become a universal settlement layer, it must interoperate with other DLT platforms and legacy systems.
Ongoing work by Swift’s standards committees aims to define common APIs and data models. - **Network effect**: The value of a shared ledger grows with the number of participants. While major banks have joined the SDL consortium, broader participation from regional banks, fintechs, and corporates is essential.
- **Risk management**: Tokenised deposits rely on the integrity of custodial accounts. Robust governance frameworks and clear legal ownership rights are required to mitigate counterparty risk. - **User experience**: Corporate clients need intuitive interfaces to initiate and monitor tokenised payments. Integration with existing treasury management systems will be a key factor in driving adoption.
Looking ahead, Swift plans to roll out additional pilot projects that will test the ledger’s capacity for high‑volume, low‑value payments, as well as its ability to support cross‑border settlements involving multiple token types. The organization is also engaging with central banks to explore how the SDL could complement emerging CBDC infrastructures, potentially serving as a bridge between fiat‑backed tokens and sovereign digital currencies. ## Conclusion The weekend USD transfer completed by DBS and Citi using Swift’s Digital Ledger and tokenised deposits is more than a technical demonstration; it is a tangible proof that blockchain‑based settlement can operate reliably outside traditional banking hours. By delivering instant, secure, and compliant payments, SDL challenges the status quo of legacy payment rails and paves the way for a more inclusive, efficient global financial network.
As more institutions join the ecosystem and the technology matures, we can expect to see an accelerating shift toward continuous, token‑driven settlement across a wide range of financial services.