Fabric Foundation has enabled RoboPay to settle payments between AI agents and robots using Stripe's Machine Payments Protocol on Tempo blockchain and the x402 standard on Base, according to a post on X. Both rails generate onchain payment records tied to completed tasks.

The dual-protocol support addresses a narrow but growing layer of machine-to-machine commerce: autonomous agents requesting work from robots and needing cryptographic proof of settlement. Stripe's Machine Payments Protocol, launched in March 2026, routes payments through the robot itself rather than a separate facilitator. The x402 standard, which originated from Coinbase infrastructure, uses an intermediary broadcaster on Base. Both methods leave an onchain transaction hash as receipt.

The payment flow works as follows. An agent sends an HTTP request asking a robot to perform a task. The robot responds with a 402 Payment Required status code, stating its price and the terms of each settlement rail. The agent cryptographically signs a stablecoin transfer but does not yet broadcast it. Once the agent retries with the signed instruction, the payment settles onchain: on Stripe's MPP the robot itself broadcasts the transaction to Tempo; on x402 a facilitator broadcasts it to Base. After verification, the robot executes the requested task and returns an HTTP 200 response with the transaction hash as proof.

RoboPay is designed for autonomous agents that need to pay for compute, data retrieval, or physical tasks without human intermediation. The protocol eliminates counterparty risk in task execution, since the agent's signed instruction settles onchain before the robot performs work. Both rails produce verifiable settlement records, allowing agents and robots to audit their economic history across different blockchains.

Stareoipe's Machine Payments Protocol represents one of the first enterprise payment rails purpose-built for agent-agent commerce. By supporting both MPP and x402, RoboPay lets agents choose between Tempo's throughput characteristics and Base's ecosystem liquidity. The addition of onchain settlement trails makes RoboPay compatible with audit and compliance tools that require immutable transaction records.

RoboPay now operates across two separate blockchains and settlement models. An agent using RoboPay can route a single task request across both Stripe's and x402's networks depending on the robot's preferred settlement chain, though this requires the agent to manage two separate signing keys and two separate stablecoin balances. If RoboPay has not published guidance on multi-chain routing by the end of Q3 2026, agents will need to manually select which settlement rail to use for each task.