Ripple’s XRPL AI Starter Kit v1.1 now supports Stripe and Tempo’s Machine Payments Protocol. XRP can run continuous payment sessions; RLUSD works only for one-off payments until a ledger upgr
- Ripple’s XRPL AI Starter Kit v1.1 now supports Stripe and Tempo’s Machine Payments Protocol.
- XRP can run continuous payment sessions; RLUSD works only for one-off payments until a ledger upgrade.
- The integration is in beta, with no live commercial volume on Stripe’s merchant rails yet.
- Circle launched its rival Arc blockchain a day earlier, splitting the field for AI-agent settlement.
Ripple released version 1.1 of its XRPL AI Starter Kit on September 17, adding support for the payment standards that Stripe and the payments blockchain Tempo co-authored earlier in 2026. The update lets developers building autonomous AI agents settle purchases in XRP and in RLUSD, Ripple’s dollar-backed stablecoin, inside software that buys data, computing power and cloud services without a human approving each transaction. Jazzi Cooper, head of product at RippleX, framed the goal as making XRP and RLUSD “first-class options wherever developers are building.”
Two Stripe-Tempo standards now carry XRP under the hood
Two protocols sit at the center of the release. The first is the Machine Payments Protocol, which Stripe and Tempo published in March 2026 as a way for software to pay on demand. An AI agent asks a service for a resource, such as a data pull from an API. The service returns a price for that specific request. The agent authorizes payment, and the service delivers the asset. Every step runs machine-to-machine, at a speed no human checkout flow could match.
The second is the Open Wallet Standard, a cross-chain interface that lets software move funds across several blockchains through one wallet layer. Its design keeps private keys out of the agent’s reach. An agent can request and initiate a transaction, but it works inside guardrails the developer sets, including hard spending limits and a whitelist of approved destination addresses. Without that separation, handing a wallet to an autonomous program would be reckless.
Why XRP gets streaming sessions and RLUSD does not
The kit treats XRP and RLUSD differently, and the difference is structural rather than a matter of preference. XRP can open what MPP calls a payment session. An agent deposits XRP once, then runs hundreds of paid queries against a service, authorizing a fraction of a cent per query. The service tallies the total and settles the accumulated sum off-chain, which keeps the ledger from choking on thousands of tiny transactions.
RLUSD cannot do that yet. One-off payments work in RLUSD and other issued tokens, but continuous, session-based streaming stays XRP-only for now. Extending payment channels to stablecoins would require a future upgrade to the XRPL ledger itself. For a stablecoin Ripple has spent all year pushing into banks and payment corridors, that is a real limit on where RLUSD can operate inside the agent economy until the upgrade lands.
Capability in the kit
XRP
RLUSD
One-off payments
✓ Yes
✓ Yes
Continuous streaming sessions
✓ Yes
✕ No
Cost per query in a session
Fractions of a cent
N/A
Settlement of accumulated queries
Off-chain, single sum
N/A
Needs a future XRPL upgrade
No
Yes
Backing both x402 and MPP so developers never switch frameworks
MPP is not Ripple’s only wager on machine payments. In June 2026 the company adopted x402, a web-native payments standard, and it now backs both. The logic is distribution rather than loyalty to one design. Developers who already picked x402 or MPP for their agent stack do not have to rebuild anything to route settlement through the XRP Ledger. Ripple meets them on whichever standard they chose.
Why Tempo’s Stripe ties matter more than its speed
Tempo is the piece that gives this reach. Incubated by Stripe and Paradigm, it launched its mainnet in March 2026 as a Layer-1 blockchain built for commerce, with sub-second finality and a multi-billion-dollar Series A. The technical spec is competitive. The connection to Stripe is the real asset.
Stripe processes payments for more than 4 million merchants. Tempo sits close to that network, which means Ripple’s integration drops XRP and RLUSD into applications whose developers committed to a payment standard before they ever picked a blockchain underneath it. Tempo also breaks from the Ethereum and Solana model on fees. Rather than forcing users to hold a native token for gas, it lets them pay transaction costs in the same stablecoin they are already moving. Its DoorDash pilot puts that to work, letting couriers take instant stablecoin payouts instead of waiting days on bank settlement.
Stripe spent 2026 building a full crypto stack, not running a trial
The Ripple integration reads differently once you see what Stripe has assembled around it. Through 2026 the company moved from accepting crypto toward operating the full settlement layer for programmable money. It combined Bridge for stablecoin orchestration, Privy for embedded wallets, and Stripe Elements for on- and off-ramps. Working with a separately governed group called the Open Standard, it introduced Open USD, a shared stablecoin infrastructure that runs settlement for businesses and routes reserve revenue back to the companies that drive its use. In September it hired Drew Turchin, previously of Native Markets, to scale a stablecoin-card business that already clears billions of dollars in monthly volume.
Circle launched Arc one day earlier and split the field
The timing was not subtle. One day before the Ripple news, on September 16, Circle launched Arc, its own institutional blockchain. CEO Jeremy Allaire described it as an economic operating system aimed at the same markets Tempo and Ripple want: tokenized assets, institutional commerce and AI-agent transactions. Circle lined up eleven founding validators to secure the network, including BlackRock, Visa, Mastercard and DTCC. Two camps are now forming around agent settlement, one built on Stripe, Tempo and Ripple, the other on Circle and Arc, and they are recruiting the same institutions. SBI Group shows how literal that overlap is: it is one of Ripple’s own RLUSD partners in Japan and a founding Arc validator at the same time.
Tempo
Stripe & Paradigm camp
Backed by
Stripe and Paradigm
Mainnet live
March 2026
Marquee partners
Stripe merchant network, DoorDash pilot
Built for
Stablecoin commerce, AI-agent payments, sub-second finality
VS
Arc
Circle camp
Backed by
Circle
Mainnet live
September 16, 2026
Marquee partners
BlackRock, Visa, Mastercard as validators
Built for
Tokenized markets, institutional commerce, AI-agent transactions
A year of bank deals and a MiCA license sit under the kit
Ripple spent the first half of 2026 threading RLUSD and the XRP Ledger into regulated finance. It launched localized RLUSD in specific corridors, teaming with SBI Group to bring the stablecoin to Japan through SBI VC Trade and with BiLira to expand in Türkiye. Deutsche Bank integrated Ripple’s payment rails to sharpen its cross-border transfers and FX operations, while DXC Technology began embedding Ripple technology into legacy banking systems that move trillions of dollars. Ripple also tokenized traditional assets directly on the XRPL with Aviva Investors, and secured preliminary approval for a MiCA crypto-asset service provider license in Luxembourg. That license is the piece that lets Ripple deploy payment or AI infrastructure inside the EU without tripping the bloc’s rules.
Three gates between this beta and real agent volume
For now the software is in beta. Making XRP and RLUSD default settlement choices inside a developer kit is not the same as merchant volume flowing through Stripe’s live rails. Market commentators, including Scott Melker, read the move as infrastructure groundwork rather than commercial traffic, and the distinction is fair. No enterprise volume runs through these standards today.
Three things gate the shift from groundwork to real use. The beta has to graduate to production. Stripe has to actually route transactions from its merchant base onto these standards rather than merely supporting them. And the XRPL upgrade that would let RLUSD run streaming sessions has to ship, since without it the stablecoin Ripple markets to institutions stays locked out of the highest-frequency agent payments.
The clearest tell will come from Stripe’s side. If Open USD and the Tempo rails start carrying merchant settlement in volume, the standards Ripple just adopted become the default plumbing for a large share of agent payments, and XRP’s session mechanic turns genuinely valuable rather than merely available. If Circle’s Arc pulls the institutional validators and the tokenization mandates instead, Ripple’s early standard-level integration becomes a hedge it has to defend. The next signal to watch is not another integration announcement but the first published figures on live transaction volume across any of these rails.
The post Ripple Puts XRP Payments Behind Stripe’s Payment Standard appeared first on ETHNews.