Tempo Network moved into live operation on March 18, 2026 with the launch of its mainnet and the debut of the Machine Payments Protocol, or MPP, developed with Stripe. The rollout positions Tempo as an infrastructure layer for autonomous AI-agent payments across both fiat and crypto rails.
At the center of the launch is a payment model built around streaming “sessions” and a payments directory, both designed to make machine-driven transactions more continuous and less dependent on one-off approvals. The core idea is to reduce friction for high-frequency automated payments by grouping large numbers of microtransactions into more efficient settlement flows.
A few things I like about MPP (machine payments protocol)
Payment-method agnostic (supports stablecoins on Tempo, Stripe, cards, Bitcoin lightning, etc)
Open and extensible (without our permission)
Streaming payments (via state channels)
Minimal and efficient https://t.co/ixTUYtJOqW
— Matt Huang (@matthuang) March 18, 2026
A Payments Architecture Built for Machine Commerce
Tempo described MPP as an open, rail-agnostic standard co-authored with Stripe and designed for internet-scale settlement. The protocol is meant to let agents draw from pre-authorized funds during continuous payment sessions instead of triggering a new payment process for every interaction.
That structure changes the economics of small-value transactions. By allowing thousands of microtransactions to settle through a single aggregated operation, MPP is designed to make machine-to-machine commerce more practical across both fiat and crypto environments.
Tempo said the protocol supports fiat, cryptocurrencies, and stablecoins including USDC from launch. That mix gives the network flexibility to route value across different payment formats without forcing users or services into a single settlement rail.
Stripe framed the launch in similar terms and emphasized that the design is meant to reduce sensitive credential exposure during automated payments. The company described MPP as an internet-native standard for agent payments rather than a narrow crypto-only payments tool.
Stablecoins, Cards, and Lightning Expand the Model
Tempo and Stripe also presented the protocol as something that can extend into existing financial infrastructure rather than compete with it in isolation. Visa has extended MPP to support card-based payments, while Lightspark has integrated Bitcoin payments through the Lightning Network.
Stripe also highlighted additional token-based payment formats connected to the broader rollout. Support for agentic network tokens and buy-now-pay-later tokens, alongside partners such as Affirm and Klarna, suggests that MPP is being positioned as a broader programmable payments layer rather than a single-use protocol.
Tempo said more than 100 services were compatible with MPP at launch and introduced a payments directory to make those services easier to discover. That directory is designed to support pay-per-call APIs and other machine-facing services that want to monetize access through automated, programmatic payment flows.
A system built around continuous outflows and pre-authorized settlement changes how liquidity, counterparty exposure, and operational control must be managed when machine agents begin moving funds at scale.
The promise of the launch is clear, but so is the execution challenge. Adoption will ultimately depend on merchant uptake, custody design for pre-authorized funds, and the ability of firms to trust the authorization, settlement, and compliance controls that sit behind automated payment behavior.