RippleX Adds XRP Payments to Stripe and Tempo's AI Standard in New Developer Kit
Key Takeaways
- •RippleX's XRPL AI Starter Kit version 1.1 adds support for the Machine Payments Protocol, an open machine-to-machine payment standard co-authored by Stripe and Tempo, as well as the Open Wallet Standard.
- •The XRP Ledger supports MPP single payments in XRP, IOUs, and Multi-Purpose Tokens, with RippleX citing 3–5 second settlement times and sub-cent fees for native XRP payments.
- •Session-based agent payments use XRPL Payment Channels that RippleX says can process signed vouchers at rates exceeding 100,000 per second while recording only two on-chain transactions per session.
- •Stripe states MPP enables developers to accept agent payments through its PaymentIntents API, but direct acceptance of XRP is unconfirmed and requires independent verification by developers.
- •The xrpl-mpp-sdk ships in beta with no commercial customers or payment volume cited in the announcement, and RLUSD is included as a first-class stable-value settlement option alongside XRP.

RippleX has released version 1.1 of its XRPL AI Starter Kit, adding support for the Machine Payments Protocol (MPP), an open standard co-authored by Stripe and Tempo. The upgrade positions the XRP Ledger as a settlement rail for AI agent payments alongside the Open Wallet Standard, although the accompanying xrpl-mpp-sdk ships in beta, with no commercial customers or payment volume cited in the launch announcement.
The RippleX announcement frames the update around two open-standard integrations: the Open Wallet Standard, which governs how AI agents discover and authorize wallets, and MPP, an internet-native protocol for programmatic agent payments, including microtransactions and recurring payments. Both integrations place the kit explicitly within the agentic payments design space rather than presenting it as a standalone Ripple product.
The standards angle matters because conventional checkout assumes a human completing verification steps at every purchase — a flow autonomous software agents cannot take part in directly. Protocols like MPP and the Open Wallet Standard are designed to replace those human-in-the-loop steps with machine-readable rules for how agents discover wallets, authorize payments, and settle them.
The release builds on Ripple's initial XRPL AI Starter Kit, which introduced foundational tooling for developers building payment flows on the ledger. Version 1.1 broadens the kit's compatibility with emerging standards without altering the underlying XRPL settlement mechanics.
XRPL as an MPP settlement rail
Under the new integration, the XRP Ledger supports MPP single payments denominated in XRP, IOUs, and Multi-Purpose Tokens (MPTs). Session-based payments route through XRPL Payment Channels, which allow an agent to open a channel, exchange signed off-chain vouchers during a session, and close it with just two on-chain transactions for the entire session.
RippleX says single XRP payments through the MPP integration settle in 3–5 seconds with sub-cent fees. The Payment Channel path is designed for high-frequency agent interactions: according to RippleX, a channel can process signed session-payment vouchers at a rate exceeding 100,000 per second, with only the opening and closing transactions hitting the ledger.
How the Stripe and Tempo connections shape developer payment workflows
MPP is co-authored by Tempo and Stripe as an open, internet-native standard for machine-to-machine payments. Stripe's own announcement describes MPP as enabling developers to accept agent payments through its PaymentIntents API in a few lines of code. For merchants, that detail matters because PaymentIntents is Stripe's core payment-processing API — the same integration surface already used for card checkout — so MPP support would slot into stacks many payment teams already operate.
That statement, however, does not say Stripe's PaymentIntents directly accepts XRP. The integration surface between Stripe's MPP implementation and XRPL's settlement rail requires independent verification by developers before end-to-end compatibility can be assumed.
Tempo's AI standard and the agentic payments layer
Tempo's role as MPP co-author positions the protocol as infrastructure for the emerging agentic payment layer, in which AI agents transact autonomously without human approval loops. XRPL's inclusion as a supported settlement rail means developers building MPP-compatible agents can designate XRP, IOUs, or MPTs as the payment asset without writing custom settlement logic. Whether that translates into production-grade agent deployments depends on how broadly MPP itself is adopted by the broader agent framework ecosystem. From here, the measurable signals are whether agent frameworks and wallet providers beyond MPP's co-authors implement the standard, and whether RippleX's SDK moves from beta to a stable release with independently audited settlement guarantees.
RLUSD as a complementary settlement asset
RippleX's framing of the kit also references RLUSD, Ripple's dollar-pegged stablecoin, as a first-class option alongside XRP within MPP flows. Developers building payment agents that require stable-value denomination can route through RLUSD rather than native XRP, a distinction that matters for use cases where token price exposure is unacceptable to the counterparty.
"Agentic payments will be multi-platform and multi-rail. Our job is to make XRP and RLUSD first-class options wherever developers are building. The latest XRPL AI Starter Kit expands support for the open standards developers are converging on: Open Wallet Standard, MPP from Tempo…"
— Jazzi Cooper (@jazzicoop), September 16, 2026, on X
What developers should verify before adopting the kit
CoinDesk notes that the payment software is in beta and that Ripple's announcement names no commercial MPP customers or payment volume. The xrpl-mpp-sdk label signals pre-production status, meaning smart contract risk, API stability, and settlement finality guarantees have not been independently audited.
Developer due-diligence checklist:
- API stability: Confirm whether the xrpl-mpp-sdk API surface is versioned and whether breaking changes are expected before a stable release.
- Supported payment flows: Verify which MPP payment types (single vs. session) are implemented and whether IOU and MPT flows carry the same latency and fee characteristics as native XRP.
- Custody and compliance: Clarify who holds custody of Payment Channel collateral during a session and whether open channels expose operators to regulatory obligations under applicable money transmission frameworks.
- Testing environments: Check whether the SDK ships with a testnet configuration and a mock MPP receiver for integration testing before touching mainnet Payment Channels.
- Stripe PaymentIntents compatibility: Independently verify whether Stripe's MPP implementation accepts XRPL as a settlement rail, rather than assuming the co-authorship implies direct XRP acceptance.
- Production support: Assess whether RippleX provides an SLA, issue tracker, or support channel for beta adopters encountering settlement failures.
Market context
XRP is trading at $1.29, with a market capitalization of approximately $81.3 billion, per CoinGecko — the liquidity backdrop against which developers will evaluate XRP as a viable agent payment asset. The Fear & Greed Index sits at 50 (Neutral), reflecting no sentiment-driven distortion in XRP's current trading environment.