Ripple has released version 1.1 of its XRPL AI Starter Kit, adding the Machine Payments Protocol (MPP), an open standard developed by Stripe and Tempo that allows software agents to pay for online services without a conventional checkout. The update also includes Open Wallet Standard support, giving developers a shared interface for managing wallets across different blockchains.
The new toolkit enables AI agents to purchase data, computing resources and other digital services using XRP or RLUSD, Ripple’s dollar-pegged stablecoin. At this point, however, the update represents a technical development rather than confirmed commercial adoption. The software is still in beta, and Ripple has not named a business using the MPP integration or disclosed transaction volumes.
MPP follows an automated process in which a service provides a price after an agent makes a request. The agent authorizes the payment, and the service then delivers the requested resource. This removes the need for a person to interact with a conventional checkout screen.
Ripple is also supporting more than one payment standard. The company introduced x402 support in June, and MPP has now been added alongside it. Rather than choosing one protocol exclusively, the approach gives developers multiple options while standards for AI-driven payments are still developing.
The integration also strengthens the potential utility narrative surrounding XRP. As AI agents become capable of independently interacting with online services, automated payments could become another way to use XRP and RLUSD. However, the current release does not provide evidence of meaningful payment volumes.
Developers already building with Stripe and Tempo’s protocol can add XRP or RLUSD payments through Ripple’s integration without restructuring their applications around another blockchain. One-time transactions support both XRP and issued assets such as RLUSD.
Recurring payment sessions currently have a narrower scope and support XRP only. Under this model, an agent can deposit XRP and use the funds across hundreds of paid requests, authorizing additional spending as responses are received. The provider can collect the total amount without recording each individual request as a separate on-chain transaction.
Stablecoin-based sessions are not yet available. RLUSD support for this functionality depends on a proposed XRPL upgrade that has not yet been deployed, so RLUSD payment channels remain unavailable.
The Open Wallet Standard tackles wallet management rather than the payment protocol itself. It allows AI agents to request transactions without obtaining direct access to private keys and can incorporate controls such as spending limits and approved recipient addresses.
Supporting both MPP and x402 gives developers a way to connect their existing payment systems with the XRP Ledger. Ripple is therefore positioning XRP and RLUSD as payment options for applications that may have selected their payment standards before choosing a blockchain.
The commercial picture remains limited for now. The toolkit is still in beta, no MPP customer has been publicly identified by Ripple, and the company has not released payment-volume data for the new integration.
Attention will now turn to the proposed XRPL upgrade that could enable stablecoin payment sessions and to whether developers using MPP or x402 begin generating measurable transaction activity on the network. Until then, the update demonstrates broader compatibility for Ripple’s payment infrastructure rather than confirmed large-scale XRP adoption by AI agents.
