Ripple adds Stripe-owned wallets to XRP Ledger as AI payments pass 14 million
The integration will let software pay for online services using XRP and RLUSD, while questions remain about how much real economic activity the transactions represent.
This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.
What happened
Ripple is partnering with Privy, a company owned by Stripe, to bring wallet technology to the XRP Ledger. The integration lets financial applications and AI agents create accounts, hold cryptocurrencies, and make payments without users managing their own wallet software, according to a release shared with CoinDesk. Payments made by AI agents now pass 14 million, and a Ripple executive said such payments account for about 25 percent of XRP Ledger activity.
Reported details
- Developers can create wallets inside their own products and authorize transfers involving XRP, Ripple’s dollar-pegged RLUSD stablecoin, and other assets issued on the network.
- Privy handles the wallet infrastructure, reducing what the app builder needs to develop itself, and it supports exporting keys or a recovery phrase so wallets can be moved elsewhere.
- The framing targets agentic commerce: companies could hand AI agents a set of funded wallets to pay for online services automatically.
- Embedded wallets will still require funding to become active, because every new XRP Ledger account must receive the network’s minimum reserve of 1 XRP, even if it will only be used for stablecoin payments.
- Privy said in its documentation that wallets operated from a company’s server are custodial in nature.
Why it matters
The 14 million figure is the headline, but the 25 percent share is the more consequential number, because it changes what the XRP Ledger looks like as a settlement rail. A quarter of activity attributed to automated agents means a meaningful slice of on-chain throughput is software paying for software rather than people trading or transferring. That has direct implications for anyone reading volume or transaction counts as a proxy for adoption, since automated payments can be high-frequency and low-value at the same time.
The embedded wallet design moves key custody from the user to the application provider. That removes a real friction point, since most people who would pay for a service through an app never want to manage secret keys, but it also means the app operator holds the ability to move funds. Privy’s own documentation describes wallets run from a company’s server as custodial, so the trade-off is explicit rather than hidden. The 1 XRP minimum reserve requirement is a smaller but concrete friction: every agent wallet needs funding before it can act, even when its entire purpose is to hold and spend RLUSD.
The unresolved question, and the one CoinDesk raises in its own summary, is how much real economic activity these transactions represent. Agent payments that are genuine purchases differ substantially from automated transfers with no underlying demand, and the two produce very different volume profiles.
What to verify
The distinction worth chasing is between agent payments that settle a real invoice and those that are test or trial traffic. Ripple’s 25 percent figure is an executive’s statement rather than an audited on-chain breakdown, so the number to check independently is the share of RLUSD-denominated transfers that can be tied to a known merchant or service. Also worth confirming is whether the 1 XRP reserve requirement applies per agent wallet, since that determines how much capital a company must pre-fund to run a fleet of them.
Sources and check time
-
BeInCrypto: https://beincrypto.com/ripple-privy-ai-agent-payments-xrp-ledger/
-
Editorial check time: 2026-10-17T00:26:00.000Z
This information is educational and does not constitute financial, legal, or tax advice.