Ripple has pushed its treasury business deeper into banking infrastructure after its $1 billion acquisition of GTreasury in 2025. The latest step is an expansion of the platform into the SWIFT Certified Partner Program ecosystem, with support for Alliance Lite2, SWIFT messaging, and channels including API, SFTP, and EBICS.
That gives treasury teams a single interface for payments, liquidity, and account operations. The scope goes beyond fiat. The platform also supports digital asset accounts for XRP and RLUSD, along with real-time IBAN and ABA lookup tools for cross-border workflows.
This is treasury software connectivity, not Ripple joining SWIFT
The biggest source of confusion is the SWIFT angle itself. GTreasury had already been part of SWIFT’s Certified Partner Program since 2014, well before Ripple bought the company. What changed now is not SWIFT admitting Ripple into its network as a new participant, but Ripple combining treasury software functions, banking access, and digital asset capabilities under one system.
In practical terms, the integration sits at the treasury software and messaging layer. It is mainly about bank connectivity and message handling. Ripple still runs on its own network, and XRP is still not used directly by SWIFT.
Companies now have two payment rails inside one setup
The upgrade matters because it adds a dual-track model. Firms can keep using traditional SWIFT rails, or switch to blockchain settlement with XRP or RLUSD when near-instant transfer is needed. Existing banking relationships stay in place. The settlement path becomes more flexible.
For institutions, that looks less like a replacement story and more like a transition tool. Traditional banking channels remain available, while on-chain settlement is added as an option inside the same treasury environment.
XRP returns to the adoption debate
The closer Ripple gets to banking infrastructure, the more attention XRP draws in cross-border payments discussions. The source material notes that the XRP Ledger had passed 8.19 million addresses in early 2026. Combined with Ripple’s treasury infrastructure handling large volumes in conventional payments, that has pushed adoption narratives back into focus.
Still, analysts have warned against overstating the news. One view highlighted in the report said that being “SWIFT compatible” only means a system can process SWIFT messages, which many vendors already do. It does not mean Ripple has become part of SWIFT, and it does not mean XRP is now embedded in SWIFT’s own operations.
At this stage, the clearest takeaway is improved connectivity between traditional finance and blockchain systems. Ripple is building tools for institutions that operate across both, but this is still short of full-scale adoption.