Tempo launches x402 payments with Base-to-Tempo settlement

Tempo has launched a facilitator for services that charge software clients through x402. The initial supported payment route accepts USDC on Base and pays the service provider OUSD on Tempo…

Will Slatton2 min read

Tempo has launched a facilitator for services that charge software clients through x402. The initial supported payment route accepts USDC on Base and pays the service provider OUSD on Tempo, according to its integration guide. Brendan Ryan, who works on machine payments at Tempo, announced the release on 19 November.

For commerce developers selling access to an API or an agent tool, it offers another way to collect usage payments. The documented product concerns paid server resources; it does not establish a new Shopify checkout option or an integration merchants can enable in their admin.

Base payments in, Tempo payouts out

An x402 client requests a resource, receives a payment requirement and retries with a signed payment. The seller's middleware asks the facilitator to verify and settle it. Tempo's current support table lists Base mainnet USDC for incoming payments and Tempo mainnet OUSD for payouts. Treat broader “any rail” language in the launch thread as the design direction, rather than evidence that every network is supported today.

Developers supply a server-side API key with the required scope and a Tempo payout address. The guide includes JavaScript and Python integration examples and a sandbox route for testing. Buyers can continue using compatible x402 clients.

Check payout completion separately

A successful settlement response does not mean the Tempo payout is already complete. The guide says it first waits for the Base receipt; OUSD arrives a few minutes later once Base is final. The response provides a payout identifier to poll until confirmation.

Our practical recommendation is to track the payment and payout states separately, reconcile both transaction legs and test failure handling before exposing a paid production endpoint. An HTTP 200 response alone is insufficient: the API can return a failed verification or settlement result inside that response.

This is relevant infrastructure for teams monetising machine access to services. It is not evidence of merchant demand, a measured conversion lift or independently verified performance superiority. Ryan's initial speed claims remain vendor benchmarks.

ℹ️
Current documented route: USDC on Base in, OUSD on Tempo out. Confirm the separate Tempo payout before treating settlement as complete.
Tempo’s 19 November launch animation illustrates its settlement design. Only the Base payment route is listed in the current support table. Watch the original announcement.
Filed underAI

More from AI

See all →