What happened
- Specific facts/numbers: Swift’s blockchain-based ledger went live in July 2026 and is in pilot use with 17 first-mover institutions; IBM said its beta adapter lets clients use standard ISO 20022 messages on Swift’s ledger, while Oracle announced an integration on September 28, 2026 to connect banks’ tokenized-deposit infrastructures across institutions.
- Institutions involved: Swift is the core network, with Oracle and IBM publicly announcing integrations; the underlying story also points to Cosmos as another vendor building connectivity around the same ledger.
- Regulatory/technical context: Swift positions the ledger as a shared orchestration layer for bank-issued tokenized deposits, enabling 24/7 cross-border payment flows ahead of final settlement through existing systems; IBM emphasized compatibility with existing payment messaging, and Oracle highlighted a unified operating model spanning traditional and digital-asset payment flows.
- What to watch next: Watch whether more banks and vendors join the 17-bank pilot before year-end and whether Swift or its partners announce production milestones beyond pilot activity; no firmer next milestone was identified in the accessible material.
Why it matters
The cluster of vendor integrations suggests banks may be treating Swift’s tokenized-deposit ledger as emerging payment infrastructure worth connecting to now, which could lower adoption friction by fitting digital-asset workflows into existing bank messaging and operations.
HKMA Relevance
Direct: This is a major cross-border payments initiative led by Swift, a core piece of global financial-market infrastructure on tokenized deposits and settlement orchestration, which is directly relevant to the HKMA’s central-bank agenda on next-generation payments and tokenisation.