Ripple Adds XRP Agent Payments as Binance and Algorand Build Wallet Controls and x402 Commerce Rails

Ripple, Binance, BNB Chain and Algorand are putting payment permissions, wallet controls and repeatable settlement routes into AI-agent products.

AI agents need more than a wallet address before they can take part in a payment flow. A business must define who funded the agent, what it may buy, how often it can pay and how a merchant can trace the order back to an approved customer. Ripple is adding repeatable XRP and RLUSD payment support to a developer kit that works with Stripe and Tempo standards. Binance and BNB Chain are addressing wallet permissions and an agent lifecycle standard. Algorand is promoting x402 as a route for software agents to pay for services, while payment companies work through fraud and funding rules. The products are different, but each moves agentic commerce toward the controls that blockchain services need for card networks, merchants and payment providers.

Ripple Adds XRP and RLUSD Agent Payments to Its Stripe and Tempo Developer Kit

Ripple added support for repeated XRP and RLUSD payments to a developer kit linked to Stripe and Tempo's AI-payment standard. The update gives a software agent a way to pay for a service more than once and manage payment activity across supported blockchain networks.

The payment flow still needs limits. A company must decide which wallet funds the agent, which service it may access and when a human must approve a purchase. Those constraints matter when an agent pays for data, software calls or a merchant order on behalf of a customer. They also give AI crypto services a practical route from a chat interface to a controlled payment action.

Binance Adds Agentic Wallet Controls as BNB Chain Publishes a Lifecycle-Protocol Draft

Binance expanded its agentic wallet controls, while BNB Chain published a draft of its Agent Lifecycle Protocol v0.4 for autonomous-agent management and self-funding. The two releases focus on the point at which an agent receives authority to use a crypto balance.

A wallet permission is more useful when the account owner can scope it to a balance, a task or a merchant. Lifecycle controls can also help a platform record how an agent was created, who authorized it and when the permissions should end. That gives crypto wallets a clearer role in agent commerce: a place to hold an approved payment balance rather than an unrestricted treasury for software.

Algorand Positions x402 for Agent Commerce as Payment Firms Define Funding and Fraud Rules

Algorand presented x402 as a protocol for blockchain-backed agent payments and commerce. Separately, payment firms are developing controls for funding sources and fraud risk as stablecoin-based agent transactions move from experiments into service access and checkout use cases.

The protocol layer can handle a request and a payment, but a merchant still needs a clear record of the buyer and the funding source. Payment teams also need limits that stop an agent from spending outside its brief or routing a charge through an unapproved wallet. These checks mirror the work done by crypto payment gateways when they connect a merchant to a new payment method.

They also matter to a business that plans to accept crypto payments as a merchant without creating a separate checkout process for every agent platform. The same recordkeeping helps shops accepting cryptocurrency reconcile a new payment channel beside cards and bank transfers.

AI-agent payments are moving from proof-of-concept tooling into wallet, protocol and merchant-integration work. The next deployment tests will depend on whether the platforms can keep each payment tied to a known funding source, permission set and customer approval.