TL;DR
- XRPL AI Starter Kit 1.1 adds Stripe and Tempo’s MPP, enabling AI agents to pay for online services with XRP and RLUSD.
- XRP payment channels support repeated small payments during sessions, while recurring stablecoin sessions still depend on a proposed upgrade to the XRP Ledger.
- Open Wallet Standard lets agents request transactions without private-key access and enforce spending controls, but the new payment software remains in beta today for developers.
Ripple has expanded its XRP Ledger AI Starter Kit with support for a payment standard developed by Stripe and Tempo, pushing XRP and RLUSD deeper into the emerging market for machine-to-machine commerce. Version 1.1 adds the Machine Payments Protocol, or MPP, alongside the Open Wallet Standard, giving developers tools for AI agents to pay for data, computing, and other online services. The notable shift is that XRP can now function directly inside a payment framework designed for autonomous software, rather than requiring developers to build an entirely separate crypto payment flow for developers and businesses.
XRP Payment Channels Bring Repeated Agent Transactions Into Focus
MPP is designed around a straightforward interaction: a service returns a price, an AI agent authorizes payment, and the requested resource is delivered. Ripple’s integration allows those transactions to use XRP and ledger-issued assets such as RLUSD. That puts XRP and Ripple’s dollar-pegged stablecoin into a standard intended for software that pays while it works. Ripple is also keeping support for x402, the web-payment standard it added in June, signaling that its developer strategy is to support multiple emerging machine-payment approaches rather than commit exclusively to one across applications increasingly reliant on autonomous digital services.
The update becomes more interesting with XRP payment channels, which are designed for repeated small payments during an ongoing session. An agent could deposit XRP once, make hundreds of paid requests, and incrementally authorize additional spending as responses arrive, while the service provider later collects the accumulated amount. This structure could reduce the need to place every individual request directly on the ledger, without settling every interaction separately. Issued tokens such as RLUSD already work for individual payments, but recurring payment sessions currently require XRP, with stablecoin support dependent on a proposed XRP Ledger upgrade.
Open Wallet Standard support adds another layer by letting agents request transactions across blockchain wallets through a common interface without gaining access to private keys. The system can also enforce controls including spending limits and approved payment destinations, giving developers tools to constrain autonomous activity. The release combines payment flexibility with guardrails intended to make agent-driven transactions more manageable. Still, the software remains in beta. Ripple has not named commercial customers using the new MPP integration, and no payment-volume figures were disclosed, leaving real-world adoption as the next unanswered question for the toolkit at scale.
