Ripple brings news with updated XRPL AI Starter Kit to version 1.1, adding support for the Machine Payments Protocol, or MPP, a standard co-authored by Stripe and Tempo for software agents that pay for services without a checkout flow. The release also adds Open Wallet Standard support, giving developers a common interface for managing wallets across multiple blockchains.
Now, developers can build AI agents that pay for data, computing, and other online services using XRP or RLUSD, Ripple’s dollar-pegged stablecoin. That matters structurally more than commercially at this stage. The software remains in beta, and Ripple’s announcement names no commercial customers using the new MPP integration and discloses no payment volume for it.
This is Ripple building out payment infrastructure ahead of demonstrated demand.
MPP works on a simple loop: a service responds to an agent’s request with a price, the agent authorizes payment, and the service delivers the requested resource. No human approves a checkout screen; the transaction is just another step in the agent’s workflow.
Ripple isn’t betting the house on one standard. It already added support for x402, a separate web-payment protocol, back in June, and MPP now joins it rather than replacing it. That’s a hedge, not a commitment to a winner, and it reflects an environment where the agentic-payments space hasn’t settled on a dominant rail.
The same logic underpins why AI systems are increasingly being used to assess XRP’s prospects in the first place: utility narratives now compete directly with speculative ones for the token’s valuation case.
Earn $50 and Enter $300K Prize Draw on EdgeX
How the Payment Mechanics Actually Work?
A business already building on Stripe and Tempo’s open protocol can now offer XRP or RLUSD payments through Ripple’s integration without re-architecting around a new blockchain. One-time payments support both XRP and issued tokens, such as RLUSD, out of the gate.
Ongoing payment sessions are more limited: they currently require XRP specifically. The intended use case is an agent depositing XRP once, running hundreds of paid queries, and authorizing incremental spending after each response, with the provider collecting the accumulated total without putting every individual query on-chain.
Extending that session model to stablecoins depends on a proposed ledger upgrade that hasn’t shipped yet, so RLUSD-denominated payment channels aren’t live.
The Open Wallet Standard piece addresses a different problem: key management across chains. It lets agents request transactions without directly accessing private keys, with safeguards such as spending limits and approved destinations built into the interface.
Trade XRP on Bybit and Get a Chance to Win Our $1,000 USDT Airdrop
Ripple News: Positioning and What’s Still Missing
Supporting both x402 and MPP gives developers a route onto the XRP Ledger regardless of which payment standard they picked first. That’s the real strategic value here, beyond the news: Ripple is inserting XRP and RLUSD into applications whose developers chose their payment protocol before choosing a blockchain, rather than trying to convince them to adopt XRPL-specific tooling from scratch.
So, what’s missing? The kit remains beta software. No named commercial customer is using the MPP integration, and Ripple has published no payment-volume figures to indicate actual usage.
The near-term catalyst to watch isn’t this release itself but whether the proposed ledger upgrade enabling stablecoin payment sessions actually ships, and whether any developer building on MPP or x402 discloses real transaction flow through XRPL. Until then, this is Ripple securing optionality in a standards race that hasn’t been decided, not confirmation that agents are paying in XRP at any meaningful scale.
Discover: The Best Token Presales
