Ripple and Privy Put XRPL Wallets Inside Everyday Apps

Ripple and Stripe-owned Privy opened XRP Ledger wallets inside ordinary apps on October 13, 2026, so customers never handle keys. Builders can create addresses, sign payments in XRP and RLUSD, and let software agents spend through the same stack.

Ripple said the ledger has already processed 13 million agent payments, about 25% of network activity. Ledger scans of that traffic still find tiny tickets, which is why a wallet that lives inside an app now matters more than another token listing.

Wallets That Never Leave the App

Privy said it is bringing programmable wallets to the XRP Ledger after a deal with Ripple. An app can mint an XRPL wallet as part of login, sign a Payment, and keep the customer inside the product. There is no browser add-on to install, and no seed phrase to copy down unless the user asks to leave.

WHAT BUILDERS GET ON DAY ONE

• Wallet create: Apps can open XRPL wallets in code through Privy instead of shipping their own key vault.
• Signing: The same stack signs XRPL transactions so the app can submit them to the ledger.
• Assets: Builders can work with XRP, RLUSD, and other digital assets issued on XRPL.
• Agents: Server-side wallets can hold funds for software that pays through x402.
• Exit: Users can export a private key or seed phrase if they want the wallet somewhere else.

The developer docs match that pitch. An app calls Privy’s API with chain type xrpl and gets back a standard r-address plus a compressed secp256k1 public key. Signing runs through xrpl_signTransaction, which returns a DER signature and a blob the app then submits with xrpl.js. Keys follow BIP-44 path m/44’/144’/0’/0/{index}.

An XRPL address is not live until it holds the base reserve of 1 XRP. Until that lands, a lookup returns actNotFound, so every new in-app wallet still needs that first XRP before it can pay. That is a small amount, but it is a real on-ledger step that a fintech onboarding flow has to fund.

Stripe Already Owns the Wallet Layer

Privy is not a new shop testing one chain. Stripe agreed to acquire the firm on June 11, 2025, and Ripple now calls it a Stripe company. Privy’s own account puts its reach at 160 million-plus accounts. Henri Stern, cofounder and CEO of Privy, said stablecoins are changing how money moves and that XRPL has been building for payments from the start.

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. pic.twitter.com/vUhKJdfxBT

— Privy (@privy_io) October 13, 2026

Stripe already sells checkout to businesses that do not want to become crypto firms. Privy is how those businesses get a wallet without teaching customers to hold keys, and XRPL is now on that list. The standalone wallet app that expected every XRP user to arrive with a seed phrase is the party that loses distribution. Fintechs that already use Privy for login can add XRP and RLUSD inside the same session.

Stern’s line is about stablecoins and agent commerce, not about a retail token float. That is the point of putting a Stripe-owned wallet layer on a payments ledger: the customer never has to know which chain settled the charge. RLUSD is the dollar asset in that pitch; XRP is the reserve and fee asset that still has to move when a new account wakes up.

Those 13 Million Payments Are Micropayments

Ripple put agent payments at the center of the announcement, and the figure is a count, not a treasury. On-chain trackers that watch the t54 facilitator’s fingerprint treat the flow as machine traffic: an agent pays for an API call, a scrap of data, or a slice of compute, then does it again. Dollar volume is the wrong lens.

XRPL SCALE AROUND THE DEAL

• Funded accounts: Privy said the ledger has grown to more than 8 million funded accounts over more than 14 years.
• Value moved: The same post put lifetime value moved on XRPL at $1 trillion.
• Activation: A new wallet needs 1 XRP before it exists on-ledger.
• Speed: An XRPL payment in the agent flow finalizes in three to five seconds.

xrpl.fi counts those agent transfers from SourceTag 804681468 and a t54-xrpl-x402 memo, and it describes them as fractions of a cent micropayments. Most x402 volume still settles in USDC on Base and Solana; XRPL’s slice is younger. A huge count with tiny tickets is what software looks like when it pays per request.

A quarter of ledger traffic can be agent pings and still leave the commercial RLUSD work to banks, custodians, and human payment apps. XRP circles keep reading each partnership as a price event. This one hides the wallet. The permission layer on those agent accounts is the product, because a bot with an open balance and no cap is a bug, not a feature.

How x402 Lets Software Pay Over HTTP

x402 is an open payment protocol over HTTP that puts the old 402 Payment Required status back to work. Coinbase published the spec. On XRPL the round trip is a normal Payment, not a new account system.

An agent calls an API. The server answers 402 with a price and an XRPL account to pay. The agent signs a standard Payment for that amount and retries the same request with the signed blob attached. It never hands over a private key. A facilitator checks the presigned payment and submits it to the ledger, then the server returns the resource once the Payment validates. Fees are a fraction of a cent, and the whole loop clears in three to five seconds.

Agents can pay in native XRP or in issued tokens, including RLUSD and USDC. Stablecoin settlement is what makes a per-request price usable, because the quote should not swing between one call and the next. Server-side Privy wallets give those agents a place to hold funds without a person at a checkout screen. That is the agentic-commerce half of the Ripple post, and it only works if someone else enforces where the bot is allowed to send money.

Broadening access to XRPL, from everyday payments to agentic commerce.

We’re partnering with @privy_io, a Stripe company, to bring embedded wallets to the XRP Ledger. Developers will be able to build payment experiences with XRP, RLUSD and other digital assets on XRPL directly… https://t.co/eJXsm5bHIZ pic.twitter.com/rIu4HiN6tc

— Ripple (@Ripple) October 13, 2026

Apps Set Limits, Users Can Still Leave

The default is app-managed keys. Fintechs can offer stablecoin payments without asking customers to store a phrase, which is the whole consumer pitch. Users who want out can export a raw hex secp256k1 private key or a BIP-39 seed. XRPL’s older family seed format is not compatible with that BIP-44 path, so it is not supported.

Privy’s policy engine is the control that makes agent wallets tolerable. On XRPL it can read decoded fields on Payment, OfferCreate, OfferCancel, and TrustSet. If a wallet tries to sign some other transaction type, the request is denied unless a matching system rule, such as a time check, allows it.

WHAT PRIVY CAN RESTRICT ON XRPL

Privy said it will keep deepening the integration, including more policy controls and gas sponsorship, so apps can pay fees on a user’s behalf. Those pieces are not the day-one docs. Day one is create, sign, export, and constrain the four transaction types above.

A Bank Turned On RLUSD Custody First

The wallet deal did not arrive in a vacuum. Standard Chartered said on October 12, 2026, a day before Privy’s post, that it had gone live with institutional custody of Ripple USD issued on XRPL. The service runs through the bank’s DIFC branch, which is regulated by the Dubai Financial Services Authority, and it is for eligible institutional clients.

THE WEEK THE WALLET AND THE BANK ARRIVED

1. June 11, 2025: Privy announces that Stripe is acquiring the company and that it will keep operating as a separate product.
2. October 12, 2026: Standard Chartered turns on XRPL RLUSD custody in Dubai; a planned LMAX collateral-mirroring link stays subject to documents, testing, and approvals.
3. October 13, 2026: Privy and Ripple say XRPL wallets are live in Privy’s stack for XRP, RLUSD, and agent payments, including x402.

Custody and in-app wallets solve different jobs. The bank holds RLUSD for institutions that need a regulated vault. Privy hides the wallet inside consumer and agent apps so those balances can move without a seed phrase. Markus Infanger, SVP of RippleX at Ripple, tied those rails together in Privy’s post.

Privy brings proven wallet infrastructure that makes it easier for fintechs and developers to bring XRPL into real products, from payments and stablecoin experiences to emerging forms of agentic commerce. Paired with XRPL’s fast settlement, low transaction costs and native support for moving and exchanging digital assets, developers have a strong foundation to build financial products that can scale.

Markus Infanger, SVP of RippleX at Ripple, Privy blog

The docs already let an app create an r-address and sign a Payment. Gas sponsorship and extra policy controls are still on the way. The test is whether those in-app wallets start carrying more than machine-sized tickets.

Disclaimer: This article is news reporting and analysis of a software partnership and related ledger activity, and it is for information only. It is not investment advice, a recommendation to buy or sell XRP, RLUSD, or any other digital asset, and it is not legal or tax advice about wallets, custody, or payments. Readers should consult a licensed financial adviser and, where needed, a qualified attorney before using crypto wallets, stablecoins, or agent-payment tools with real funds. Figures and product statuses come from company posts, developer docs, and on-chain trackers as of the dates named above and can change as the integration continues.