In XRP news today, Brad Garlinghouse, CEO of Ripple, stated on CNBC’s Squawk on the Street on June 26, 2026, that the company processes approximately $16 trillion in annual payments and clearing activity across businesses added through acquisitions, and that digital asset transactions currently account for ‘close to zero percent’ of that volume.
The figure is not a confession of underperformance; Garlinghouse framed it explicitly as the core opportunity, describing Ripple’s mission as ‘how do we bring traditional finance into the modern architecture of blockchain’ and adding that through acquisitions, the company now has ‘a tremendous opportunity to bring that in.’
The products Ripple is positioning as the conversion mechanism, On-Demand Liquidity, RLUSD, and Ripple Treasury, each address a distinct layer of that migration path.
The open question the market must now resolve is whether Ripple’s institutional infrastructure can translate $16 trillion in legacy payment flows into measurable on-chain volume for XRP, or whether stablecoins capture the majority of that migration value while XRP remains a secondary settlement layer.
XRP News: What the $16 Trillion Payments Figure and Near-Zero Digital Asset Share Means
Context enhances the $16 trillion in annual payments and clearing activity cited by Garlinghouse, which isn’t organic Ripple volume but rather the combined throughput from acquisitions like Hidden Road and GTreasury.
These are traditional financial firms, not crypto-native, whose operations rely on outdated banking methods. Ripple didn’t build this $16 trillion payments business; it acquired it, which is a crucial distinction.
The ‘close to zero percent’ digital asset share reflects the gap between Ripple’s current infrastructure and the potential on-chain market it could serve.
Garlinghouse’s claim of high demand suggests interest in blockchain alternatives, but the shift from interest to actual volume hasn’t happened at scale.
An analysis estimated that even a 5% migration of GTreasury’s $13 trillion flows to blockchain could mean $650Bn annually for XRP Ledger, though current regulations limit banks’ ability to use XRP directly.
Garlinghouse aims for XRP to capture a significant share of the $156 trillion cross-border payments market by 2031.
Achieving this target depends on regulatory and institutional adoption, as well as RippleNet’s ability to convert existing relationships into active deployments of ODL and RLUSD.
DISCOVER: Best Crypto Presales to Watch Right Now
In other XRP news today, On-Demand Liquidity (ODL) is Ripple’s most developed product for institutional cross-border payments, using XRP as a bridge asset to enable real-time settlement of transactions between fiat currencies. This eliminates the need for pre-funded nostro accounts.
Key partnerships include SBI Remit and Tranglo, with the recent integration of Ripple-Bitso supporting regulated dollar-peso transactions for the high-volume US-Mexico corridor.
Ripple’s RLUSD is a compliance-grade, fiat-backed stablecoin designed for institutional use, minimizing XRP price exposure for banks and corporate treasuries.
The process involves institutions converting dollars to RLUSD on the XRP Ledger, which then facilitates ODL liquidity sourcing for cross-currency transfers, completing transactions more efficiently than SWIFT.
Ripple Treasury streamlines corporate treasury management by integrating XRP and RLUSD with traditional assets, aided by the acquisition of GTreasury.
Ripple Prime expands its institutional offering into derivatives, engaging with CME Group’s crypto futures and options, with XRP emerging as collateral.
The timeline for GTreasury’s clients to adopt RLUSD and ODL payment flows is projected at three to five years, depending on regulations and custody rules in the U.S. and EU.
EXPLORE: Best Crypto Presales to Watch Right Now
This article is not financial advice. Crypto assets are highly volatile. Always conduct your own research before investing.
The post XRP News: The $16 Trillion Gap and Why Near-Zero On-Chain Volume Is the Opportunity appeared first on icobench.com.


