News · NEWS
Oracle, IBM and Cosmos outline connections to Swift's tokenized-deposit ledger
The vendors describe different integration routes, including IBM's beta messaging adapter; connectivity announcements should not be counted as universal production access.
Published by
RWA Wire Editorial Desk
Coverage standard
Independent // Source-led
Corrections & tips
Contact the desk →
Oracle and Cosmos announced routes to Swift’s shared ledger on 28 September, following an IBM announcement on 24 September. The proposals connect banks’ existing systems with tokenized-deposit infrastructure rather than requiring all banks to adopt one replacement core ledger.
Oracle describes coordinated payment flows across institution-controlled deposit systems. IBM describes a beta ISO 20022 adapter in Digital Asset Haven and an on-premises beta option. Cosmos describes tools for connecting bank cores to tokenized-deposit ledgers and other networks.
Different announcements, different stages
The vendors are describing integration capabilities. IBM’s beta label is particularly important: it identifies a testing stage, not unconditional production availability for every institution.
For this story, the concrete change is the availability or development of interfaces between existing payment operations and new ledgers. It does not show that the three products have identical functionality or that banks using them have all completed customer-facing deployment.
Sources
Key takeaways
- //Vendor integrations connect existing systems to new rails; beta availability is distinct from a completed bank rollout.
Explore this topic
Continue through RWA Wire's connected research map.
RWA Wire // Intelligence Network
Infrastructure connected to this story
Continue researching
Go from this story to the background, infrastructure and adjacent market developments that explain it.
Explore all topics →