XRP Ledger Lets AI Agents Pay in XRP and RLUSD
XRP Ledger now works with the Machine Payments Protocol, giving AI agents a way to buy online services with XRP and, for single charges, RLUSD.
Key Takeaways
- XRPL now supports the open MPP standard.
- XRP handles charges and payment sessions.
- RLUSD currently supports single payments only.
- The XRPL MPP software remains in beta.
This is not Stripe Checkout support for XRP
RippleX has added XRP Ledger to the Machine Payments Protocol, or MPP, through version 1.1 of its AI Starter Kit. MPP is an open standard co-developed by Stripe and Tempo for software that needs to pay for services without navigating a conventional checkout.
The RippleX release makes XRPL one of the networks that can settle those payments. It does not mean Stripe Checkout now accepts XRP or that Stripe processes every transaction made through the integration.
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 another route that developers can use without building a payment process specifically for XRP Ledger.
A 402 response replaces the checkout page
An AI agent is software that completes tasks for a user. 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 agent requests a paid resource.
- The service returns the amount and accepted payment methods.
- The agent’s wallet checks its spending rules and signs the payment.
- The provider verifies settlement and releases the resource.
Stripe describes MPP as a way for agents to transact without creating an account, selecting a subscription or manually entering payment details. RippleX says a single XRPL payment generally settles in three to five seconds with a fee below one cent.
XRP 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 through XRP Ledger Payment Channels.
The agent first places XRP in 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.
This 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
RLUSD cannot use Payment Channels yet
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.
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.
The agent can sign without reading the private key
Autonomous payments require controls over what the software can spend. Version 1.1 therefore adds XRP Ledger support to the Open Wallet Standard, or 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 controls 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 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 importance 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.
Kosta has reported on cryptocurrency markets and blockchain infrastructure since 2020, bringing over six years of hands-on experience in the crypto industry built through daily tracking of markets, trends, and emerging blockchain developments. Specializing in Bitcoin on-chain analysis, institutional ETF flows, and digital asset price action, his work at Coindoo has been cited by other news agencies and consistently covers market developments with a focus on data-driven reporting across Bitcoin, Ethereum, Solana, and XRP. Over the years, Kosta has contributed to multiple crypto media outlets in different regions, authoring over 6,000 articles across the sector. His reporting spans cryptocurrency markets and the broader fintech industry, tracking not only price action but also the technological and regulatory forces shaping the ecosystem. To support his analysis, Kosta actively leverages on-chain data and metrics from leading platforms such as Santiment, Glassnode, and CryptoQuant, enabling deeper, evidence-based market insights. He believes in the power of transparency and the data that underpins the blockchain ecosystem. His academic background in Marketing Management from Denmark further complements his analytical approach, adding a strong understanding of communication strategy and content positioning to his work.
