SWIFT's Shared Ledger Goes Live: Why Tokenized Deposits Are Moving to the Front Office of Institutional Payments

Introduction

In September 2026, the global banking industry completed two representative live transactions involving tokenized deposits in succession. On September 2, First Abu Dhabi Bank (FAB) and Citibank completed a USD transaction through SWIFT's blockchain ledger; on September 10, DBS Bank, OCBC, and UOB completed the Singapore banking industry's first live interbank transactions in Singapore dollars based on tokenized deposits. The two sets of transactions covered cross-border USD and local currency payments respectively, and both connected traditional SWIFT messaging, bank-issued tokenized deposits, and a shared ledger.

This means SWIFT is adding an around-the-clock "value orchestration layer" on top of the traditional payment system: participating banks continue to manage their own customers, deposits, and compliance relationships, while the shared ledger is responsible for synchronizing payment commitments between banks and enabling tokenized deposits to operate collaboratively across different banking systems.

From the announcement of construction in September 2025, to entering initial use in July 2026, to the emergence of live transactions in different currencies in September, SWIFT Ledger completed the progression from conceptual design to production environment validation in less than a year. The change it brings is not simply "putting payments on-chain," but rather traditional bank deposits beginning to acquire a technological form that is programmable, continuously operable, and capable of cross-institutional collaboration. This article will analyze how this change may reshape the institutional digital payments market from the perspectives of technical architecture, financial impact, legal relationships, industry competition, and real-world constraints.

1. From Proof of Concept to Live Transactions

When SWIFT first announced its shared ledger plan in September 2025, more than 30 financial institutions participated in its design. The project initially emphasized real-time, around-the-clock cross-border payments and interoperability between different forms of digital value. In July 2026, SWIFT announced that the ledger was ready to enter the initial use phase, with 17 banks from six continents preparing to conduct live transactions using tokenized deposits. At this point, the project's focus had shifted from "whether it can connect" to "whether it can operate within real bank liabilities and compliance processes."

The two sets of transactions in September further shortened the distance between concept and business. The USD transaction between FAB and Citi validated end-to-end interaction among existing SWIFT payment messages, tokenized deposits, and distributed ledger infrastructure. Subsequently, the three Singapore banks—DBS, OCBC, and UOB—completed local currency interbank transactions, demonstrating that the same architecture not only serves cross-border correspondent banking scenarios but can also handle around-the-clock payment needs within a single country's banking system.

It is worth noting that these transactions did not use public chain tokens aimed at anonymous holders, but rather tokenized deposits issued by banks and connected to customer deposit relationships. So-called tokenized deposits are the digital representation of commercial bank deposit liabilities on a programmable ledger. Simply put, what customers hold is still a deposit claim against the bank, except that this claim can be recorded, transferred, and embedded with automated execution conditions through new ledger technology.

This distinction determines that SWIFT Ledger's primary customers are not retail crypto users, but rather banks and their clients that need to handle corporate funds, trade payments, institutional settlement, and cross-border liquidity. For these entities, whether the technology is novel is not the primary question; whether it can connect to existing account systems, identity standards, risk controls, and regulatory reporting is the key to determining large-scale adoption.

2. What the Shared Ledger Actually Changes

For a long time, SWIFT's core function has been to transmit standardized financial messages. After the paying bank sends instructions, the actual movement of funds occurs within individual bank ledgers, correspondent bank accounts, or central bank settlement systems. Message transmission and fund settlement are interrelated, but they are not the same thing. As a result, cross-border payments often require multiple institutions to separately verify accounts, compliance status, and fund positions, and the operating hours of different systems are not entirely aligned.

SWIFT Ledger does not eliminate individual banks' internal ledgers, but rather adds a commonly visible, verifiable coordination record between banks. Its initial purpose is to treat bank-issued tokenized deposits as interbank liabilities, verify and synchronize payment commitments through smart contracts, and execute value transfers at the customer level only after confirming that participating parties have the corresponding funds.

The core concept here is the "decoupling of payment execution from final settlement." Simply put, customer payments can first be completed around-the-clock within the tokenized deposit network, while the final fund obligations accumulated between banks can still be settled through existing RTGS or correspondent banking channels. This approach reduces the difficulty of a new system directly replacing global settlement infrastructure and enables banks to test new payment capabilities while retaining existing capital, credit, and liquidity control frameworks.

This design goes further than merely increasing message speed. Traditional messages can only describe a payment request, whereas a programmable ledger can simultaneously check fund availability, participant identity, transaction conditions, and state changes. In future corporate treasury management scenarios, payments may be connected to invoices, cargo status, securities delivery, or smart device instructions. Funds are no longer merely transferred after receiving instructions, but can be automatically executed when agreed conditions are met.

However, it is important to distinguish that instant execution on the ledger does not necessarily equal instant legal final settlement. If interbank clearing still needs to be completed through existing systems, then there remains a legal and liquidity relationship that must be managed among on-chain records, customer account changes, and final interbank settlement. SWIFT's current approach is closer to gradual transformation rather than a one-time rebuilding of the monetary settlement foundation.

3. Why Tokenized Deposits Have Become Banks' Preferred Entry Point

Tokenized deposits are valued by banks first because they continue the legal and balance sheet structure of existing deposit money. Customer deposits are inherently liabilities of commercial banks; tokenization primarily changes the way they are recorded and transferred, and does not automatically create a new issuing entity independent of the bank. By contrast, fiat stablecoins are typically backed by reserve assets provided by dedicated issuers, and their holder rights, redemption arrangements, bankruptcy isolation, and regulatory frameworks need to be designed separately.

Second, tokenized deposits more easily preserve "singleness of money." Singleness of money means that different forms of money in society can be exchanged at par and are treated as the same unit of account. The reason why one dollar of deposits at Bank A and one dollar of deposits at Bank B are typically equivalent is not only due to bank credit, but also because deposit insurance, central bank reserves, clearing arrangements, and prudential regulation together maintain par-value convertibility. Some stablecoins, by contrast, may deviate from par due to issuer credit, reserve quality, or liquidity differences.

SWIFT's approach attempts to bring this institutional foundation into a programmable environment. Banks remain responsible for customer due diligence, sanctions screening, transaction monitoring, and account management; tokenized deposits remain within the regulated banking system; and the shared ledger provides cross-bank coordination without requiring every institution to join a completely unfamiliar public chain economic system.

Third, tokenized deposits can connect with banks' existing funding sources and credit creation mechanisms. Stablecoin issuers typically support circulating tokens with highly liquid reserves, and their business logic is closer to a payment instrument or narrow reserve arrangement; commercial banks, meanwhile, serve the real economy by absorbing deposits, extending loans, and managing maturity transformation. For large corporate clients, if programmable payments still originate from existing bank accounts and credit relationships, there is no need to transfer large amounts of funds outside the system into stablecoins on a long-term basis just to use digital settlement.

However, tokenized deposits will not automatically replace stablecoins as a result. Stablecoins still have advantages in public blockchains, global accessibility, on-chain transactions, and developer ecosystems. What is more likely to emerge is market stratification: stablecoins continue to serve public chain-native scenarios and some cross-border payments, while tokenized deposits prioritize institutional funds, trade, securities settlement, and regulated digital asset markets. The focus of competition will shift from "which token is faster" to who can simultaneously provide compliance usability, cross-platform interoperability, and a sufficiently broad acceptance network.

4. Financial Efficiency and Liquidity Constraints Rise Simultaneously

For corporate clients, the most intuitive change is that payment time boundaries are weakened. Cross-border group fund transfers, margin replenishment, supply chain payments, and weekend transactions need not be entirely constrained by bank business days. DBS emphasized in a public statement that corporate businesses operate around the clock, and their funds also need corresponding continuous availability; OCBC and UOB linked their live transaction results to programmable, interoperable, and cross-time-zone payment capabilities.

Around-the-clock payments may also reduce precautionary funds that companies hold to cope with delays. The more transparent the cross-border payment status, the easier it is for companies to determine when funds will arrive and whether they are available, and to adjust cash pools and short-term financing accordingly. For banks, shared state also helps reduce duplicate reconciliation and exception investigations, shifting some operational costs from manual coordination to unified standards and automated controls.

However, faster settlement does not mean lower liquidity requirements. Traditional payment systems often smooth funding needs through batch processing, net settlement, or end-of-day windows; when transactions shift to real-time and 7×24 operation, banks need to continuously monitor positions at night, on weekends, and during holidays. If customer-level payments have already been completed while final interbank settlement still occurs in subsequent windows, participating banks must also manage the credit exposures and collateral arrangements formed during the interim period.

The International Monetary Fund proposed in its 2026 research on tokenized finance that continuous settlement will change the rhythm of liquidity management, and automated execution may also accelerate margin calls and fund outflows during stress periods. Therefore, new infrastructure needs to simultaneously incorporate limits, suspension mechanisms, manual intervention, failure rollback, and liquidity support mechanisms. For institutional markets, the truly difficult challenge is not making smart contracts execute automatically, but deciding when to allow them to stop executing under extreme circumstances.

The cost structure will also change. Reconciliation, message matching, and intermediary links may decrease, but network access, smart contract auditing, key management, data governance, and around-the-clock operations will become new fixed costs. Large banks may find it easier to bear these investments, while smaller and medium-sized institutions may rely on shared service providers. This will increase the economies of scale in infrastructure while also creating new concentration concerns.

5. Legal Issues Shift from "What Is a Token" to "When Does a Record Take Effect"

Tokenized deposits are built on existing deposit relationships, but this does not mean all legal issues have been resolved. First, it must be clarified which constitutes the legally effective final record between the on-chain record and the bank's core ledger. If differences arise between the two due to system failures, network forks, or manual corrections, which record should govern customer rights needs to be determined jointly by contracts, business rules, and applicable law.

The second is settlement finality. Settlement finality refers to the point in time at which a fund transfer becomes legally irrevocable and cannot be unconditionally reversed. Simply put, it is not enough for the technical system to display "success"; insolvency administrators, courts, and other participating institutions must also recognize that the transfer has been completed. Cross-border transactions simultaneously involve different banks, ledger operating rules, correspondent banks, and settlement systems, and finality may occur at multiple points in time separately.

The third is jurisdiction and conflict of laws. The customer is located in one country, the deposit bank in another, shared ledger nodes are distributed across multiple regions, and final settlement may use a third country's currency. In the event of erroneous execution, asset freezing, or institutional bankruptcy, which country's law determines the nature of tokenized deposits, rights of set-off, and priority ranking cannot be answered by technical protocols alone. Scaled cross-border use requires clearer participation rules and legal opinion support.

The fourth is anti-money laundering, sanctions, and data governance. Permissioned networks can restrict participating institutions, but cannot replace transaction monitoring. Around-the-clock and programmable payments will compress manual review time, placing higher demands on sanctions list updates, beneficial owner identification, suspicious transaction blocking, and false positive correction. At the same time, shared ledgers need to balance verifiability with bank secrecy, personal information, and cross-border data transfer restrictions.

Finally, there is code governance. Once smart contracts participate in fund control, programming errors can become a source of financial risk. Who can upgrade contracts, suspend transactions, correct erroneous records, whether upgrades require joint approval from participating banks, and whether regulators can obtain audit information in a timely manner are all governance issues. The risks of traditional financial institutions are mainly recorded in balance sheets and processes; under a tokenized system, some risks begin to concentrate in platform rules, interfaces, and code.

6. How Stablecoins, Banks, and Financial Infrastructure Will Redivide Roles

The industry significance of SWIFT Ledger lies in the fact that the global banking network has begun to respond to the around-the-clock payment pressure brought by stablecoins using its own liability instruments. In the past, one of the most obvious advantages of stablecoins was the ability to transfer on-chain without being restricted by bank business hours. As tokenized deposits also gain continuous operating capability, institutional clients choosing payment instruments will pay more attention to credit structure, regulatory treatment, balance sheet usage efficiency, and integration with existing banking services.

For commercial banks, this is both defense and a new business entry point. Banks can reduce the incentive for customer funds to leave the deposit system and combine programmable payments with cash management, trade finance, foreign exchange, and securities services. For SWIFT, the shared ledger extends its role from messaging standards and connectivity networks to transaction state coordination. Its competitive advantage is not owning a particular blockchain, but its existing institutional identity, global connectivity, messaging standards, and compliance collaboration network.

Traditional payment infrastructure is also simultaneously studying two forms of digital currency. In September 2026, Nacha, which is responsible for U.S. automated clearing house network rules, announced the formation of a project team specifically to study the impact of stablecoins and tokenized deposits on various types of payments. This indicates that industry discussion is no longer limited to competition between "banks and the crypto industry," but has entered a phase in which clearing organizations, card networks, financial market infrastructure, and software service providers are all adjusting together.

For fintech companies, opportunities may appear more at the application layer. Enterprises will not change their financial processes merely because the underlying ledger has been updated; they need cross-bank fund visibility, automated accounts receivable and payable, compliance orchestration, on-chain/off-chain reconciliation, and conditional payment tools. Whoever can package new tokenized payment capabilities into the financial, trade, and asset management software that enterprises actually use may be able to generate sustainable revenue.

But infrastructure concentration also warrants caution. If a large number of banks rely on the same orchestration layer, identity service, or smart contract template, the impact of a single point of failure will be amplified. Network effects can reduce fragmentation, but they also increase the importance of platform governance and operational resilience. Future regulatory focus may not only target banks issuing tokens, but may also gradually cover technology and infrastructure providers that play a key role in transaction execution.

7. Boundaries That Still Exist in Current Live Transactions

First, successful transactions at the current stage do not equal global commercial coverage. 17 early participating banks and a small number of currencies can prove that the technical path is feasible, but cannot prove that all time zones, jurisdictions, and long-tail correspondent banks already have access conditions. The complexity of cross-border payments often comes from the last mile, local compliance, and liquidity, rather than the core ledger itself.

Second, the separation of payment execution and final settlement is a pragmatic design and also a constraint that has not yet disappeared. As long as final interbank funds still depend on existing RTGS and correspondent banking channels, transactions occurring on weekends or at night will require credit limits, pre-funding, or deferred settlement arrangements. A shared ledger can improve coordination efficiency, but it will not automatically eliminate currency, maturity, and counterparty risk.

Third, interoperability needs to move from technical connectivity to unified business rules. Different banks may adopt different tokenized deposit platforms, data models, and privacy technologies. Even if interfaces can transmit instructions, all parties still need to unify asset identification, state definitions, error handling, compliance responsibilities, and dispute resolution procedures. Truly scalable interoperability is not just about making systems "understand" each other, but also about enabling institutions to form a consistent understanding of the legal consequences of the same transaction.

Fourth, customer demand still needs verification. How much are enterprises willing to pay for around-the-clock payments, which businesses truly need second-level execution, whether new processes can improve working capital, and whether banks can provide competitive pricing all require more real transaction data. Technology supply has emerged, but the business model is still in its formative stage.

8. What to Watch Next

Corundum believes that what is most worth observing in the coming period is not the speed of individual transactions, but three institutional indicators.

First, whether the scope of participation expands from bilateral or small bank groups to multi-currency, multi-region networks. If new institutions require extensive customized development each time they join, the network effects of the shared ledger will be limited; if existing SWIFT connections and standards can significantly reduce access costs, its expansion could accelerate.

Second, whether the final settlement asset changes. The current path retains existing RTGS and correspondent bank settlement, reducing the risk of initial transformation. If tokenized central bank reserves, wholesale central bank digital currencies, or other regulated on-chain settlement assets are gradually connected in the future, the distance between payment execution and final clearing may be further shortened, but corresponding central bank access and legal issues will also increase.

Third, whether regulators begin to establish dedicated operational, code, and recovery requirements for shared ledgers. As transaction volumes rise, smart contract auditing, key recovery, transaction suspension, data access, and cross-border crisis coordination will shift from project governance issues to financial stability issues. Who is responsible for making exception decisions at machine speed will become a more important institutional arrangement than automatic execution under normal conditions.

From the perspective of industry evolution, SWIFT has not chosen to compete head-on with public blockchains across all scenarios, but rather to gradually add digital capabilities starting from the deposit liabilities, identity networks, and settlement systems most familiar to banks. The advantage of this path is compliance and institutional coverage; the disadvantage is that the pace of progress is constrained by multi-party coordination. Whether it can become the public connectivity layer for institutional-grade tokenized finance depends on whether the project can maintain trust while avoiding the formation of new closed islands.

Conclusion

The USD and Singapore dollar live transactions in September 2026 demonstrate that tokenized deposits have begun to leave pure proof of concept and enter real bank liabilities and production processes. What SWIFT Ledger showcases is not traditional finance suddenly pivoting to