Ripple adds Privy wallets as XRPL agent payments top 14m

Ripple is adding Stripe-owned Privy’s embedded wallets to the XRP Ledger, giving app developers a way to create accounts and authorize payments in XRP, RLUSD and other ledger assets without building wallet infrastructure themselves. The integration, reported by The Block on Oct. 13, also supports wallets managed by software and AI agents, extending a payments push that is drawing attention as reported agent transactions climb past 14 million.

Privy’s infrastructure lets wallets sit inside an app, so a user need not connect a separate crypto wallet. Developers can create and manage wallets and sign transactions through the service. Privy users can also export private keys or seed phrases to move wallets elsewhere, The Block reported. The service is part of Stripe, which acquired Privy in 2025; it continues to operate separately.

What changes for apps and AI agents?

The integration lowers the amount of wallet plumbing a developer must build to offer XRPL payments inside an existing product. For AI agents, a wallet managed by an app can hold funds and pay for online services, including through x402, a standard for software payments. A service can request payment for data or another digital resource, and an agent can authorize the transaction as part of completing a task.

This builds on Ripple’s earlier work: its June launch of the XRP Ledger AI Starter Kit included x402 support for payments in XRP and RLUSD. Privy adds embedded wallet infrastructure to that effort. The companies say policy controls and tools for covering network fees are planned as the integration develops, according to The Block. Those features could affect how much control developers retain over agent spending and how easily users can start transacting.

Do 14 million transactions show meaningful payment use?

The count signals activity, but it does not by itself show the scale of economic demand. The XRPL AI Hub, operated by t54, showed 14,392,359 cumulative transactions across 169 registered merchants when checked. The same dashboard listed 6,991.77 XRP and 12,834.48 RLUSD settled. These are cumulative totals from the hub, not a measure of the value of every transaction across the ledger.

The gap between transaction count and token totals is consistent with many small payments, such as charges for individual service requests. It also means the headline count should be read as a measure of recorded payment events, rather than a proxy for large transfers or broad commercial adoption. The hub describes itself as an index of agentic payments; the figures depend on activity it tracks and do not establish how much of the ledger’s overall use comes from AI agents.

What could slow adoption?

Embedding wallet creation may remove a setup step, but it does not remove the need to fund an account. New XRP Ledger accounts need the network’s minimum reserve of 1 XRP to activate, according to Privy documentation cited by CoinDesk. That applies even when the intended payment asset is RLUSD, so users or developers still need to supply XRP at the outset.

The trade-off is between convenience and account control: an embedded wallet can simplify the user experience, while making clear recovery options, spending limits and fee arrangements important. The next signals are whether the promised policy controls and fee sponsorship arrive, whether developers put the integration into live products, and whether the hub’s transaction totals are accompanied by sustained growth in settled value and identifiable merchant use.

Sources and documents

• The Block — theblock.co
• XRPL AI Hub, operated by t54 — xrpl-ai.org