Stripe-owned Privy said on October 13, 2026, that it is partnering with Ripple to bring its wallets to the XRP Ledger (XRPL). Developers will be able to create XRPL wallets and sign transactions without building that infrastructure themselves.
The Brief
- Privy will support XRP, Ripple’s RLUSD stablecoin and other XRPL assets for wallet creation and transaction signing in developer apps.
- Server-side wallets will let AI agents hold funds and pay for online services through the x402 payment protocol.
- The XRPL has more than 8 million funded accounts and more than $1 trillion in value moved, according to Privy.
- Users will be able to export their private keys and seed phrases if they want to move a wallet elsewhere.
Privy builds embedded wallets that sit inside an app, so users don’t need to connect a separate crypto wallet. In its announcement, the company aimed that model at payments firms and fintechs. Those firms can offer stablecoin payments without asking customers to handle keys. Ramp’s stablecoin accounts, for one, already run on Privy’s infrastructure.
1/ We’re partnering with @Ripple to bring Privy wallets to the XRP Ledger (XRPL). This makes it easier for developers to build stablecoin payments, fintech applications, and agentic commerce on XRPL. https://t.co/vUhKJdfxBT
— Privy (@privy_io) October 13, 2026
Stripe’s wallet arm plugs into Ripple’s network
Payments giant Stripe agreed to buy Privy in June 2025. Privy has kept operating as a separate product since then. Henri Stern, Privy’s co-founder and CEO, also serves as head of crypto and stablecoins at Stripe.
Stern’s dual role puts a Stripe executive at the center of a Ripple integration. Stripe already runs its own stablecoin business through Bridge, the infrastructure firm it bought for $1.1 billion. Its wallet unit will now carry RLUSD, Ripple’s dollar stablecoin, as well. Neither company said whether Bridge-issued tokens will also reach the XRPL through Privy wallets.
Stern framed the move around payments. Stablecoins “are changing how money moves,” he said, adding that the XRPL has focused on payments since its early days. Markus Infanger, SVP of RippleX at Ripple, made a similar case. He said Privy’s tooling makes it easier for fintechs to put the ledger into shipping products, from stablecoin payments to agent-driven commerce.
AI agents get a payment rail on XRPL
The second half of the pitch targets software that spends money on its own. Privy said server-side wallets can give agents a way to hold and move funds, including through x402.
Coinbase developed x402 as an open protocol that revives the HTTP 402 “Payment Required” status code. Clients, whether people or machines, can use it to pay for APIs and online content programmatically. No accounts or sessions are required. A server answers an unpaid request with a 402 response that carries the payment instructions.
The resulting stack pulls pieces from three separate companies: Stripe-owned wallets, Ripple’s ledger and Coinbase’s payment standard. That gives the XRPL a direct line into a standard built outside Ripple’s own product line.
Developers can start from the XRPL guide that Privy linked in its post. People holding funds in apps built this way keep the key-export option described above.
Open Questions
The post explains what developers will be able to do, but it doesn’t say how many apps are already building. It also leaves practical questions open:
- Which payment firms or fintechs will ship XRPL wallets first?
- Will agent payments over x402 settle in RLUSD, XRP or both?
- How will Privy price XRPL wallets against its other supported networks?
- Will Ripple route any of its own payment products through Privy wallets?
Privy’s stated next step is adding policy controls and gas sponsorship, which would let developers set transaction rules and cover users’ network fees. The company gave no date for either feature. Until those arrive, the integration centers on wallet creation, signing and key export. The announcement came three weeks after a September 23 Privy post on new ways to build with TRON.
