What to Know
- Ripple’s updated XRP Ledger AI Starter Kit adds support for the Stripe and Tempo-backed Machine Payments Protocol.
- The beta software allows AI agents to make one-time payments using XRP and ledger-issued tokens such as RLUSD.
- The kit also supports ongoing XRP payment sessions, a feature designed for repeated service requests such as data or computing access.
- Extending ongoing payment sessions to stablecoins such as RLUSD depends on a proposed XRP Ledger upgrade.
- The Open Wallet Standard integration lets agents request transactions without gaining access to private keys.
- Built-in safeguards include spending limits and approved destinations for agent-initiated transactions.
- Ripple previously added support for x402 in June and is now backing MPP as another route for machine-to-machine web payments.
- The release remains in beta, with no commercial customer names or payment volume disclosed for the new MPP integration.
Ripple Pushes XRP Deeper Into AI Payments
Ripple has expanded its XRP Ledger developer tooling with support for the Machine Payments Protocol, a payments standard associated with Stripe and Tempo, as the company seeks to position XRP and RLUSD for a new generation of automated software-driven transactions. The update arrives through Version 1.1 of the XRPL AI Starter Kit, a beta developer package designed to help builders create AI agents that can pay for online services while performing tasks on behalf of users.
The change matters because AI agents are increasingly being discussed as active participants in digital commerce rather than passive software assistants. If an agent needs to purchase access to data, computing resources, content, application features, or other online services, it needs a way to receive pricing information, authorize payment, and complete the transaction without manual intervention each time. Ripple’s latest kit is aimed at making XRP and ledger-issued tokens such as RLUSD available inside that workflow.
The Machine Payments Protocol, or MPP, gives a service a structured way to respond to an agent’s request with a price. The agent can then authorize payment, after which the service delivers the requested resource. In this setup, crypto is not being positioned only as a speculative asset. It is being framed as a programmable payment instrument that can support automated online activity, particularly where software needs to pay repeatedly, quickly, and with defined permissions.
How the Developer Kit Works
Version 1.1 of the XRPL AI Starter Kit adds MPP support alongside the Open Wallet Standard, which is designed to let software manage wallet interactions across multiple blockchains through a shared interface. For developers, that can reduce the friction of building agent payment flows that need to interact with wallets while still preserving key security boundaries.
A central feature of the update is that AI agents can request transactions without directly accessing private keys. That distinction is important. Private keys represent control over funds, and giving autonomous software unrestricted access to them would create obvious security risks. By allowing agents to request transactions rather than control keys, the Open Wallet Standard integration keeps the agent’s role closer to that of a controlled requester inside a permissioned workflow.
The kit also supports safeguards including spending limits and approved destinations. Those controls are especially relevant for agentic commerce, where software may initiate payments repeatedly as it completes tasks. A spending cap can limit financial exposure if something goes wrong, while destination controls can help ensure that payments are routed only to services or addresses that have been approved in advance.
The beta software supports one-time payments using XRP and ledger-issued tokens such as RLUSD. It also supports ongoing XRP payment sessions, which are built for repeated interactions. That session model could be useful for services that charge small amounts each time an AI agent requests a resource, because the agent can fund a session and authorize usage over time rather than requiring every individual request to be settled separately on-chain.
Why Payment Sessions Matter for XRP
The payment session feature gives XRP a specific role in the emerging machine payments stack. In a repeated-use scenario, an agent could deposit XRP once, make numerous paid requests during a session, and authorize incremental spending as services are delivered. The provider could then collect the accumulated amount without requiring each individual query to appear as a separate blockchain transaction.
That design is particularly relevant for use cases where the value of each request may be small but the number of requests may be frequent. AI agents may need to purchase many separate pieces of data, access tools, call application programming interfaces, or use computing resources during a broader task. A payment mechanism that can handle repeated usage efficiently may be more practical than a system that treats every interaction as a standalone payment event.
For now, the ongoing session feature is tied to XRP. Individual payments already support issued tokens such as RLUSD, Ripple’s dollar-pegged stablecoin, but extending the session model to stablecoins depends on a proposed XRP Ledger upgrade. That distinction is important for developers evaluating the kit today, because it means XRP has the broader session functionality in the current beta release while stablecoin-based sessions remain conditional on future ledger-level changes.
Market participants are watching this distinction because stablecoins have become a common settlement choice in crypto payments, while XRP has long been associated with fast value transfer and payment use cases. Ripple’s strategy appears to be to keep both available where possible, allowing developers to choose between XRP and RLUSD depending on the needs of a specific application, treasury model, or user experience.
Ripple Backs Multiple Web Payment Standards
Ripple’s latest move follows its earlier support for x402 in June, another standard focused on web payments. By supporting both x402 and MPP, Ripple is not forcing developers into a single protocol path. Instead, it is trying to ensure that XRP Ledger payment options are available across more of the emerging machine payments landscape.
This approach may help Ripple reach developers who have already chosen a payments standard before deciding which blockchain or token to support. If a business is building around the Stripe and Tempo-backed open protocol, the new MPP integration gives that business a route to accept XRP or RLUSD through the XRP Ledger. If another developer is working with x402, Ripple’s earlier integration offers a separate path.
For builders, optionality can matter. Machine payments are still an early category, and developers may not yet know which standards will gain the most traction. Supporting more than one standard can reduce the risk that a project is locked into a narrow ecosystem. For Ripple, the benefit is clear: the more standards that can route payments through the XRP Ledger, the more chances XRP and RLUSD have to appear in agent-driven payment flows.
The involvement of Stripe and Tempo in MPP also gives the update added visibility. Stripe is a major payments company, while Tempo is a blockchain built for payments. Their role in co-authoring the standard places MPP within a broader discussion about how payment infrastructure should adapt when software, not only humans, initiates commercial activity online.
Beta Status Keeps Expectations Grounded
Despite the strategic significance of the release, the software remains in beta. Ripple has not named commercial customers using the new MPP integration, and it has not provided payment volume associated with the feature. That means the update should be viewed as developer infrastructure rather than evidence of large-scale adoption already taking place.
Technical traders and market participants often react to integrations involving XRP because they can shape narratives around utility, liquidity, and network relevance. However, there is a difference between enabling a capability and proving that the capability is being used at scale. The current update expands what developers can build, but measurable demand will depend on whether applications adopt the tools and whether users trust agents to make payments on their behalf.
There are also practical questions around security, permissions, accounting, and user experience. Agent payments require clear controls so that users understand what an agent is allowed to buy, how much it can spend, and which services it can pay. The Open Wallet Standard integration addresses part of that challenge by emphasizing transaction requests, spending limits, and approved destinations, but real-world implementation will still depend on how developers design their applications.
For XRP, the most immediate implication is narrative and infrastructure expansion. The token is being placed inside a payments architecture designed for AI agents, while RLUSD is included for one-time issued-token payments. The larger commercial question is whether machine payments become a meaningful source of on-chain activity and whether XRP Ledger tools can compete with other payment assets already used by developers.
What Comes Next for XRP and RLUSD in Agent Commerce
The next phase will likely depend on developer experimentation, ledger upgrades, and the broader adoption of AI agents that need paid access to online resources. If the proposed ledger upgrade enabling stablecoin payment sessions moves forward, RLUSD could gain a more flexible role in repeated payment flows. Until then, XRP holds the key session-based function within the current beta kit.
Developers evaluating the toolkit will likely focus on whether it can simplify wallet management, reduce payment friction, and enforce enough controls for autonomous activity. Service providers, meanwhile, will need to decide whether accepting XRP or RLUSD offers enough benefit compared with other payment options already available in crypto and traditional payments.
For Ripple, the release supports a broader objective: making XRP and RLUSD first-class options wherever developers are building payment-capable software. The company is positioning the XRP Ledger not just as a network for transfers, but as infrastructure for automated economic activity involving AI agents, web services, wallets, and programmable permissions.
The update does not guarantee adoption, and the beta label underscores that the market is still early. Still, it marks another step in the effort to connect crypto payment rails with AI-driven software workflows. If agent commerce develops into a larger category, integrations like MPP and x402 support could become important battlegrounds for which digital assets are accepted by default.
Frequently Asked Questions (FAQs)
What did Ripple add to the XRPL AI Starter Kit?
Ripple added support for the Machine Payments Protocol and the Open Wallet Standard in Version 1.1 of the XRPL AI Starter Kit, enabling developers to build AI agents that can request and make payments using XRP and ledger-issued tokens such as RLUSD.
What is the Machine Payments Protocol?
The Machine Payments Protocol is a standard that lets a service respond to an AI agent’s request with a price, after which the agent can authorize payment and receive the requested resource. It is designed for automated payment activity between software and online services.
How is Stripe connected to this update?
Stripe and Tempo co-authored the Machine Payments Protocol. Ripple’s developer kit now supports that standard, which gives builders using the protocol a way to route payments through the XRP Ledger with XRP and supported ledger-issued tokens.
Can AI agents pay with RLUSD?
The beta software supports one-time payments with ledger-issued tokens such as RLUSD. However, ongoing payment sessions for stablecoins such as RLUSD depend on a proposed XRP Ledger upgrade and are not available in the same way as XRP sessions in the current beta.
Why are XRP payment sessions important?
XRP payment sessions can help services that charge repeatedly for small requests. An agent can set aside XRP for a session, make repeated paid queries or service calls, and allow the provider to collect accumulated payment without putting every individual request on the blockchain.
Does the AI agent control private keys?
The Open Wallet Standard integration is designed so that agents can request transactions without gaining access to private keys. This helps keep control of funds within a safer permission structure while still allowing automated payment workflows.
What safeguards are included for agent payments?
The integration supports safeguards such as spending limits and approved destinations. These controls can help restrict how much an AI agent is allowed to spend and where it is allowed to send payment requests.
Is the new MPP integration commercially active?
The payment software remains in beta. Ripple has not named commercial customers using the new Machine Payments Protocol integration and has not disclosed payment volume tied to the feature.
Why does this matter for XRP?
The update places XRP inside an emerging framework for AI-driven payments, giving developers a way to use XRP for automated online service access. Its long-term importance will depend on developer adoption, real usage, and whether machine payments become a meaningful category in crypto commerce.