Ripple is giving XRP payments a more machine-friendly job.
The company has expanded its XRP Ledger developer kit to support the Machine Payments Protocol, or MPP, a standard created by Stripe and Tempo for automated transactions between AI agents and online services.
The update, part of version 1.1 of the XRPL AI Starter Kit, also adds support for the Open Wallet Standard. That framework allows software to manage wallets across multiple blockchains through a shared interface.
The pitch is distinctly internet-native: instead of a person clicking “buy,” an AI agent can request a service, authorize a payment and receive the result on its own.
MPP is designed around that loop. A service sets a price after receiving a request, the agent approves the payment, and the provider delivers whatever the software asked for.
Stripe and Tempo co-authored the standard, giving Ripple a way to plug XRP payments into an existing approach to machine-driven commerce rather than building an entirely separate system.
XRP Payments Want a Seat in the Agent Economy
RippleX head of product Jazzi Cooper framed the strategy directly on X: “Our job is to make XRP and RLUSD first-class options wherever developers are building.”
RLUSD, Ripple’s dollar-pegged stablecoin, is supported alongside XRP in the new tooling. Ripple previously added x402 support, another standard for web payments, in June.
Backing both standards gives developers using either approach a way to accept payments on the XRP Ledger.
That matters because the blockchain choice may come after the payment standard. A company already building around Stripe and Tempo’s protocol could potentially add XRP or RLUSD without abandoning the system it has chosen for machine-to-machine payments.
For AI agents, the practical question is simple. If software is buying data, computing power or another digital service, it needs both a way to pay and a currency the seller accepts.
Ripple is positioning XRP and RLUSD as two possible answers.
The new XRP payments integration gets more interesting when transactions happen repeatedly. XRP payment channels could let an agent fund a session upfront, make hundreds of smaller payments as it works and avoid putting every individual transaction directly onchain.
There is a catch. While individual payments already support issued tokens such as RLUSD, session-based payments currently require XRP. Support for stablecoins in those channels would depend on a proposed upgrade to the XRP Ledger.
For now, the software is still in beta. Ripple has not named commercial customers using the MPP integration, and the company has provided no payment-volume figures.
That leaves XRP payments in an early but clearly defined experiment: machines spending money autonomously, one online request at a time.