TLDR
- A 2021 SWIFT profile listed GTreasury support for FIN, FileAct, InterAct, MT, and ISO 20022.
- The post claims Ripple inherited GTreasury’s SWIFT-ready setup through its reported $1 billion acquisition deal.
- Corporate payment messages named in the profile include MT101, MT940, pain.001, pain.002, and camt formats.
- The claim centers on whether Ripple Treasury can connect bank messaging with blockchain-based settlement tools.
- Any XRP angle remains unconfirmed unless Ripple shows how GTreasury systems may use ledger rails.
A new XRP-focused post has brought attention to a 2021 SWIFT profile linked to GTreasury. The post says Ripple gained that system through its reported $1 billion purchase. It raises one key question: “Did Ripple just buy the bridge to banks?”
2021 SWIFT Profile Draws Fresh Attention
The post points to a SWIFT-compatible application profile from 2021. It says the document listed GTreasury as a SWIFT-compatible application provider. The profile came years before the reported Ripple deal in October 2025.
According to the post, GTreasury supported both MT and MX message formats. MT is linked with FIN messages, while MX uses ISO 20022 formats. The profile also named BIC Directory and Bank Directory Plus support.
The post says GTreasury worked with SWIFT Alliance Access, Lite2, and Autoclient. It also named FIN, FileAct Real Time, and InterAct Real Time services. These tools help companies send and receive bank messages.
The listed message types included MT101, MT940, MT942, pain.001, and camt formats. These formats support payment orders, account reports, and bank status updates. The post presents this as a ready treasury link to bank messaging.
Ripple Treasury Claim Sparks Bank Bridge Question
The central claim is that Ripple inherited GTreasury’s SWIFT setup after the acquisition. The post says this made Ripple Treasury SWIFT-integrated from day one. However, the claim needs direct company confirmation before wider use.
The post frames the deal as more than a treasury software purchase. It says Ripple may have bought a working connection to bank messaging systems. The author asked, “Did Ripple buy the bridge to banks?”
That question has gained interest among XRP supporters. Many have long debated how Ripple could connect bank rails with blockchain settlement. The post argues the answer may sit inside existing GTreasury infrastructure.
Still, SWIFT messaging and blockchain settlement are not the same process. SWIFT sends payment instructions between banks and firms. Settlement depends on banks, ledgers, stablecoins, or other payment systems.
XRP, RLUSD, And The Wider Treasury Angle
The post links the GTreasury profile to XRP Ledger and RLUSD. It says Ripple could connect treasury workflows with blockchain settlement options. That claim remains unproven without a public technical roadmap.
The post also mentions ISO 20022 as part of the story. SWIFT has moved more payment messaging toward ISO 20022 formats. GTreasury’s listed MX support could help firms handle that newer format.
For corporate users, the possible draw is simple. A company could manage bank messages in a familiar treasury system. Then, it could use other tools for faster settlement where available.
Ripple has built products for payments, stablecoins, and enterprise finance. The GTreasury angle adds a bank messaging layer to that wider story. For now, the market has a question, not a confirmed answer: “Did Ripple buy a SWIFT bridge to banks?”
Get 3 Free Stock Ebooks
Discover top-performing stocks in AI, Crypto, and Technology with expert analysis.
- Top 10 AI Stocks - Leading AI companies
- Top 10 Crypto Stocks - Blockchain leaders
- Top 10 Tech Stocks - Tech giants
