Three technology vendors — Chainlink, Oracle, and IBM — announced integrations with Swift's blockchain-based shared ledger within a single week at Sibos 2026 in Miami (September 28–October 1). The announcements mark the first vendor competition for middleware access to the ledger, which 17 banks ...
"Financial institutions need a practical, trusted way to connect emerging digital assets, including tokenized deposits, with established payment infrastructure while maintaining control, security, and operational resilience." — Jamie Bullard, VP Application Software Engineering, Oracle Financial Services
Three technology vendors — Chainlink, Oracle, and IBM — announced integrations with Swift's blockchain-based shared ledger within a single week at Sibos 2026 in Miami (September 28–October 1). The announcements mark the first vendor competition for middleware access to the ledger, which 17 banks across six continents are piloting for 24/7 cross-border payments using tokenized deposits.
Swift's ledger, built on Hyperledger Besu (EVM-compatible), went from concept at Sibos 2025 to activation in nine months. It does not move money. It records and validates payment commitments between banks, nets resulting obligations, and lets participants settle through conventional real-time gross settlement (RTGS) systems. Tokenized deposits remain on each bank's own ledger; Swift's layer coordinates movement between them, including overnight and on weekends.
The vendor race signals a structural shift: the question for large banks is no longer whether to tokenize deposits, but which middleware stack to use for connecting to the coordination layer that Swift already operates for 11,500+ institutions across 200+ markets.
Swift announced the blockchain-based shared ledger at Sibos 2025 in September. The minimum viable product was built on open-source foundations using Hyperledger Besu, an EVM-compatible enterprise blockchain framework. Swift operates the ledger itself, handling transaction workflow orchestration, validation of funding commitments, and coordination of interbank processes.
The ledger's design reflects a deliberate architectural choice: it functions as an orchestration layer, not a settlement layer. Banks issue tokenized deposits on their own ledgers — these remain commercial bank liabilities recorded on distributed ledgers. Swift's shared ledger then records and validates interbank payment commitments, nets obligations, and coordinates settlement through existing RTGS infrastructure.
This architecture preserves the regulatory status of bank deposits. Tokenized deposits remain on bank balance sheets, subject to deposit insurance and existing prudential regulation. The shared ledger extends, rather than replaces, existing payment infrastructure. Banks can execute payments using tokenized deposits as the underlying value representation while leveraging existing compliance processes.
The MVP launched for pilot testing in July 2026, nine months after the Sibos 2025 announcement. According to Swift, the design was shaped by a global cohort of more than 40 financial institutions.
The concentration of vendor announcements during Sibos 2026 (September 28–October 1, Miami) was notable. Three separate technology providers each disclosed integrations with Swift's ledger within days of each other.
Chainlink Labs announced the Chainlink Runtime Environment (CRE) as a connectivity layer between bank infrastructure and Swift's ledger. The integration uses a self-signing model: banks retain control of the cryptographic keys used to authorize transactions. CRE orchestrates the workflow — reading from and writing to Swift's ledger — while institutions preserve existing approval procedures, security controls, and operating models.
Sergey Nazarov, CEO of Chainlink Labs, stated: "We are thrilled to be supporting the Swift ledger as more banks seek to join it and need a technology partner."
Chainlink simultaneously launched CCIP 2.0 at Sibos, introducing Cross-Chain Verifiers (independent verification layers operated by issuers or trusted third parties) and an Automated Compliance Engine with built-in eligibility checks, approvals, and transaction limits. The company framed its infrastructure as targeting "$600 trillion in onchain finance."
Oracle disclosed an integration between its Oracle Blockchain Platform and Swift's ledger. The solution hosts Swift commitment contracts and supports the event orchestration required for ledger integration. Oracle's stack includes its EVM-based enterprise blockchain, custodial wallet capabilities, cryptographic signing, and smart contract infrastructure.
The integration links to Oracle Banking Payments, connecting digital asset flows with ISO 20022 payment processing. Oracle achieved Swift Compatible Application certification for payments earlier in 2026.
IBM announced its Digital Asset Haven integration with Swift's ledger within the same week. According to reporting from Ledger Insights, IBM's beta connects banks to Swift's ledger for digital deposits, allowing participants to move assets 24/7.
According to Ledger Insights, the frequency of three major vendor announcements within one week for an infrastructure platform still in pilot phase is unusual. It suggests either confirmed demand from pilot banks or high vendor confidence in expected adoption rates.
The initial cohort spans six continents. Full list: ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand Bank Limited, HSBC, Itaú Unibanco, Lloyds Bank, Mashreq, MUFG Bank, OCBC, Standard Chartered, UBS, UOB, and Wells Fargo.
The geographic distribution is significant. The list includes institutions from the United States (BNY, Citi, Wells Fargo), Europe (BNP Paribas, Lloyds, UBS), Asia-Pacific (ANZ, DBS, MUFG, OCBC, UOB), the Middle East (First Abu Dhabi Bank, Mashreq), Africa (FirstRand Bank), and Latin America (Itaú Unibanco). This breadth matches Swift's positioning as a global coordination layer rather than a regional payments initiative.
The pilot is testing payments that operate overnight and on weekends, with final settlement through existing RTGS systems. These banks collectively manage trillions of dollars in deposits. Swift's broader network processes approximately 15.1 billion messages annually (2025 figure, up 12.1% year-over-year) and connects 11,500+ financial institutions across 200+ markets.
The tokenized deposit model occupies a distinct position in the digital money taxonomy. Unlike stablecoins — which are issuer liabilities backed by reserves — tokenized deposits are direct commercial bank liabilities. Unlike wholesale central bank digital currencies (CBDCs), tokenized deposits leverage existing banking infrastructure and regulatory frameworks.
According to Dataintelo, the global tokenized deposits market was valued at $4.8 billion in 2025 and is projected to reach $38.6 billion by 2034, growing at a 26.2% CAGR. For comparison, stablecoin market capitalization stood at approximately $320 billion as of end-May 2026, according to BIS data — though both figures remain small relative to the trillions held in traditional bank deposits.
The BIS has explicitly backed the tokenized deposit model. Project Agorá, organized by the BIS and the Institute of International Finance, demonstrated that tokenization can address inefficiencies in wholesale cross-border payments. The project showed atomic settlement of wholesale cross-border transactions using tokenized central bank reserves and tokenized commercial bank deposits.
Swift's ledger aligns with this architecture: deposits stay on bank balance sheets; the shared ledger handles coordination. This stands in contrast to the stablecoin model, where value is transferred via bearer instruments on public chains, and the CBDC model, where the central bank operates the ledger directly.
The vendor race reveals the economic value distribution in tokenized deposit infrastructure. Three distinct value-capture layers are emerging:
Coordination layer (Swift): Swift operates the shared ledger and captures value through its existing fee model for message and transaction orchestration. Its 11,500-institution network represents a distribution moat that no blockchain protocol has replicated.
Middleware layer (Chainlink, Oracle, IBM): These vendors capture value by providing the connectivity between bank systems and the shared ledger. The self-signing model (Chainlink's CRE), smart contract hosting (Oracle Blockchain Platform), and asset management infrastructure (IBM Digital Asset Haven) represent competing approaches to the same integration problem. Middleware fees will likely follow enterprise software pricing models rather than per-transaction blockchain fees.
Bank-level infrastructure: Individual banks operate their own tokenized deposit ledgers and retain full control over issuance, redemption, and balance sheet management. The economic value at this layer derives from extending existing deposit services to 24/7 operation and cross-border programmability.
Notably absent from this value chain: public blockchain gas fees, validator rewards, and token-based incentive mechanisms. Swift's Besu-based ledger is permissioned. The pilot banks are not paying gas fees to anonymous validators. Value flows through enterprise contracts, not protocol-level token economics.
The BIS Annual Economic Report (2026) devoted a chapter to "Anchoring trust in money: innovation beyond stablecoins," explicitly contrasting tokenized deposits with stablecoin models. The BIS argues that tokenized deposits preserve the existing trust architecture of the banking system — deposit insurance, prudential supervision, central bank backstops — while gaining the programmability advantages of distributed ledger technology.
The regulatory environment is also shifting in favor of tokenized deposits. The GENIUS Act stablecoin rules in the United States (published by the Federal Reserve in September 2026) create a regulatory framework that distinguishes between stablecoins and bank-issued tokenized deposits. In Europe, MiCA applies primarily to stablecoins and crypto-assets; tokenized deposits, as bank liabilities, fall under existing banking regulation.
This regulatory asymmetry may prove decisive. Banks issuing tokenized deposits operate under established supervisory frameworks. They do not need new licenses. They do not need to convince regulators that a new asset class deserves trust. They are extending an existing product — the deposit — onto new infrastructure.
The Sibos 2026 vendor race around Swift's ledger crystallizes a structural trend: tokenized deposits are becoming the institutional path for bringing 24/7 programmable payments into the existing banking system. The coordination layer already exists (Swift's network of 11,500+ institutions). The middleware vendors are now competing to build the connective tissue. The pilot banks are testing live transactions.
The implications are twofold. First, the infrastructure for tokenized cross-border payments is being built inside the existing financial system, not alongside it or in opposition to it. Second, the economic value of this infrastructure flows through enterprise software and network access fees, not through public blockchain tokenomics.
Whether this approach can scale beyond pilot — and whether 17 banks become 170 or 1,700 — depends on execution, not on technology selection. The Besu-based architecture is proven. The regulatory framework is accommodating. The remaining variable is operational integration across heterogeneous bank technology stacks, which is precisely the problem that Chainlink, Oracle, and IBM are racing to solve.