Ripple Adds XRP Payments to Stripe and Tempo AI Standard

RippleX has released version 1.1 of its XRPL AI Starter Kit, adding support for the Machine Payments Protocol (MPP) co-authored by Stripe and Tempo, making the XRP Ledger a settlement rail for AI agent payments alongside the Open Wallet Standard. The xrpl-mpp-sdk ships in beta, with no commercial customer or payment volume evidence attached to the launch.

What the v1.1 kit adds to the XRPL developer stack

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 targets position the kit explicitly within the agentic payments design space rather than as a standalone Ripple product. For related coverage, see Ripple and UC Berkeley Launch University Digital Asset Xcelerator.

This builds on Ripple’s initial XRPL AI Starter Kit release, which introduced the foundational tooling for developers building payment flows on the ledger. Version 1.1 expands the standard compatibility surface without altering the underlying XRPL settlement mechanics. For related coverage, see Ripple Stablecoin Hits Record as Spot XRP ETFs Draw Capital.

XRPL as an MPP settlement rail

Under the new integration, XRPL supports MPP single payments denominated in XRP, IOUs, and Multi-Purpose Tokens (MPTs). For session-based payments, the kit routes through XRPL Payment Channels, which allow an agent to open a channel, exchange signed off-chain vouchers, and close with just two on-chain transactions for the entire session. For related coverage, see Fed Meeting Nightmare for Warsh? Why Bitcoin Could Shine.

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: RippleX says the channel can process signed session-payment vouchers at a rate exceeding 100,000 per second, with only the open and close 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. 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 assuming end-to-end compatibility.

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, where 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 to production-grade agent deployments depends on how broadly MPP itself is adopted by the broader agent framework ecosystem.

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, which 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

Source: @jazzicoop on X

What developers should verify before adopting the kit

CoinDesk notes that the payment software is 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 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 relationship implies direct XRP acceptance.
• Production support: Assess whether RippleX provides an SLA, issue tracker, or support channel for beta adopters encountering settlement failures.

XRP is trading at $1.29, with a market capitalization of approximately $81.3 billion, providing 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.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.