RippleX has added the XRP Ledger to the Machine Payments Protocol (MPP), an open standard co-developed by Stripe and Tempo that lets software pay for digital services without navigating a conventional checkout. The integration ships in version 1.1 of RippleX's AI Starter Kit.

The release makes XRP Ledger one of the settlement networks available to MPP-compatible AI agents, which can now pay in XRP and, for single payments, in Ripple's RLUSD stablecoin. RippleX was careful to note that the addition does not mean Stripe Checkout now accepts XRP, or that Stripe processes every transaction made through the integration.

From x402 to MPP

Ripple introduced the original XRPL AI Starter Kit in June with support for the separate x402 payment standard. Version 1.1 keeps x402 and adds MPP as a second route, giving developers a standard interface they can adopt without building a payment process specifically for XRP Ledger.

Stripe describes MPP as a way for agents to transact without creating an account, selecting a subscription, or manually entering payment details.

An HTTP 402 Response Replaces the Checkout Page

An AI agent is software that completes tasks on a user's behalf. When it requests paid data, computing capacity, or access to an online tool, an MPP-compatible service can respond with an HTTP 402 message containing the price and payment instructions. The flow unfolds in four steps:

1. The agent requests a paid resource.
2. The service returns the amount owed and the payment methods it accepts.
3. The agent's wallet checks its spending rules and signs the payment.
4. The provider verifies settlement and releases the resource.

According to RippleX, a single XRPL payment generally settles in three to five seconds, with a transaction fee below one cent.

Payment Sessions Avoid a Transaction for Every Request

Individual payments suit occasional purchases but become inefficient when an agent pays for every prompt or API call. For repeated usage, the integration supports sessions built on XRP Ledger Payment Channels.

In this model, the agent first places XRP into a channel. It then sends the provider signed vouchers showing a progressively higher amount owed as the service is consumed. These updates happen offchain, while the provider records the final amount on XRP Ledger when the session ends.

The design reduces the process to two onchain transactions: one to open the channel and another to settle it. The provider can claim only the XRP committed to that channel, rather than withdraw an unspecified amount from the agent's wallet.

XRP and RLUSD Do Not Have Identical Support

RippleX lists XRP, issued currencies, and multi-purpose tokens as supported for single MPP charges. That allows RLUSD to pay for an individual resource and gives providers a dollar-denominated alternative to XRP's changing market price. RLUSD cannot yet use Payment Channels.

Session payments currently work with XRP only. Extending Payment Channels to issued currencies and multi-purpose tokens depends on XLS-93d, a proposed XRPL amendment. RippleX plans to support stablecoin sessions but has not announced an activation date.

Agents Can Sign Without Reading the Private Key

Autonomous payments require controls over what software is allowed to spend. Version 1.1 therefore adds XRP Ledger support to the Open Wallet Standard (OWS).

OWS stores wallets inside an encrypted local vault and gives agents access through a policy-controlled signing interface. An agent can request authorization for a payment without reading or storing the raw private key. The wallet owner must still set spending limits, approved assets, and permitted recipients. OWS governs how the agent reaches the wallet; it does not decide whether the agent's payment request is sensible.

The Integration Still Needs to Prove Real Demand

MPP makes it easier for an AI service to add XRP Ledger, but XRPL is only one of the protocol's possible settlement routes. Developers can just as readily support other networks, stablecoins, or conventional payment methods through the same standard.

RippleX says the earlier x402 integration has produced 5.6 million XRPL transactions. The company has not separated testing from production activity, disclosed the value transferred, or identified how many independent services generated that total.

The new MPP package is also in beta, and the announcement does not name a production customer using it. The clearest evidence of adoption would be independent services accepting XRP or RLUSD, sustained payment value, and the eventual launch of RLUSD sessions.

The technical route is now available. Its significance will depend on whether developers choose XRP Ledger when their agents have several ways to pay.

This article is provided for informational purposes only and does not constitute financial or investment advice. The XRPL MPP software remains in beta, and supported features may change as development continues.