Ripple Just Connected XRP to Stripe’s AI Agent Payments. Why the Sessions Run on XRP, Not RLUSD

Ripple has connected XRP to a payment system where the buyer is a piece of software rather than a person. The process involves that software requesting a service, which then quotes a price. The software approves the charge, and the service delivers, all without any human interaction at a keyboard, a checkout page, or a card field. This automated transaction structure is known as an agent payment.

On September 17, 2026, Ripple integrated the XRP Ledger into this flow through a standard co-authored by Stripe and Tempo, a blockchain built for payments that launched its mainnet in March. The streaming component of this flow operates on XRP (CRYPTO:XRP) because RLUSD cannot handle that part yet. So, what exactly has Ripple connected, and what benefits does this bring to holders?

What Ripple Connected to Stripe

Ripple released version 1.1 of the XRPL AI Starter Kit, which now includes support for the Machine Payments Protocol (MPP) and the Open Wallet Standard. MPP is particularly significant for Stripe, which co-authored the protocol with Tempo. The kit initially launched in June, and this update builds on an existing resource available to developers.

The Open Wallet Standard gives wallets a common interface across different blockchains and lets an agent request a transaction without accessing the main private keys, under spending limits and approved destinations set by the account owner.

This functionality is made possible through XRP Ledger 3.3.0’s Permission Delegation feature, which allows another account limited authority to perform specific transaction types rather than having full control. Although granting a wallet access to software may seem risky, it operates within predetermined spending limits.

Ripple has also chosen not to favor one open standard for agent commerce over the other. It added support for x402, a standard backed by Coinbase, Stripe, and Cloudflare, in June, and now backs both.

The x402 protocol has already facilitated between 75 million and 120 million machine-to-machine payments in recent months, amounting to millions of dollars, with each transaction costing a fraction of a cent. Ripple maintains a premier membership in the x402 Foundation alongside Coinbase, Circle, AWS, Google, Mastercard, Stripe, and Visa, and it is also a launch partner for Mastercard’s Agent Pay for Machines.

Why Sessions Run on XRP, Not RLUSD

Jazzi Cooper, head of product at RippleX, articulated the goal clearly. “Our job is to make XRP and RLUSD first-class options wherever developers are building,” she said. One of these options meets the criteria for every type of payment, while the other does not.

A single payment can be processed using either option. An agent calls an API, makes a payment, receives the data, and the entire process concludes in three to five seconds for less than a cent. Both XRP and RLUSD can handle individual payments, as can other tokens issued on the ledger.

However, a session is more complex. In a session, the agent opens a payment channel and signs vouchers off-chain as it consumes the service, at a rate exceeding 100,000 per second. The blockchain does not record these transactions. Instead, the provider settles everything with two on-chain transactions, one to open the channel and another to close it. This setup allows an agent renting compute power by the second to pay without incurring fees at each second mark.

Payment channels are native to the XRP Ledger. In contrast, RLUSD is an issued token, a ledger entry created by Ripple that resides on top of the ledger rather than within its settlement system. Extending channels to issued tokens will require a future XRPL upgrade, which Ripple has not yet scheduled.

Therefore, while Ripple’s stablecoin is designed for straightforward payments, the asset it has been repositioning for years is better suited for continuous transactions.

The Integration Has No Revenue Behind It Yet

The kit is still in beta, and no merchants on Stripe’s platform have yet routed a live commercial session through it. As of September 18, XRP is trading at $1.32, up 16.97% over the past month but down 4.66% over the past week, as the market drifts lower.

Circle (NYSE:CRCL | CRCL Price Prediction) made competitive positioning more challenging the day before Ripple’s announcement, launching Arc, a blockchain designed for payments. By opting to develop its own settlement layer rather than joining Ripple’s, the world’s largest stablecoin issuer has highlighted the competitive landscape of agent payments.

For Ripple to generate revenue, three groups need to take action. Developers must choose XRP Ledger wallets for MPP, merchants on Stripe must accept payment sessions, and Ripple must implement the upgrade that allows RLUSD to handle streaming transactions. Ripple controls only the third element, and it has given that one no date.

Does This Change Anything for XRP Holders?

XRP gained a job it can do and no other asset on its own ledger can, which is new for a coin that has been called a payments asset for a decade while trading almost entirely on regulatory headlines. Streaming micropayments between machines is exactly where a fast native asset with settlement finality beats a token that has to be issued and redeemed.

The integration gives holders no revenue, and it gives RLUSD no seat at the same table until the ledger upgrade arrives. A named merchant routing a live session through MPP on the XRP Ledger would make this commercial, and a date on the public roadmap for payment channels around issued tokens would end the situation where Ripple’s payments stablecoin cannot do the payments Ripple just wired to Stripe.

Contact [email protected] for any questions or corrections.