What Is Tempo? Stripe and Paradigm's Stablecoin Blockchain Explained 

What is Tempo?

Tempo is a Layer 1 blockchain built for stablecoin payments. Incubated by Stripe and Paradigm, it went live on mainnet on March 18, 2026, after a public testnet phase that began in December 2025.

The chain is fully EVM-compatible, so developers can deploy any smart contract they want using the same tools they would on Ethereum, including Solidity, Foundry, and Hardhat. At the same time, the network is tuned for what payment systems actually need: fees that stay predictable when the network is busy, throughput that holds up under high transaction volume, and settlement that's reliable at scale.

In practice, that translates to roughly 0.6-second finality, gas fees paid in USD stablecoins instead of a volatile native token, and built-in support for memos, smart accounts, and machine payments.

Why Tempo was built

The stablecoin market has grown more than tenfold in five years and now sits around $300 billion, with the US Treasury projecting growth to $3 trillion by 2030. Most of that value moves on blockchains that weren't designed to handle payment workloads, and that's the gap Tempo is built to close.

In Tempo's framing, the issue with using general-purpose chains for stablecoin payments comes down to three things:

• Fees fluctuate. Transaction costs depend on what else is happening on the chain.
• Throughput is limited. Performance gets squeezed when the network is busy.
• Transaction structures don't fit payment flows. Features that production payment systems rely on, like memos, smart accounts, and compliance controls, aren't built into the base protocol on most chains.

Tempo's design choice is to address those gaps at the protocol layer rather than as add-ons. The chain is built around what real payment systems require: predictable costs, high throughput, and reliable settlement at volume.

Who's behind Tempo

Tempo is incubated by Stripe and Paradigm. In Tempo's own framing, the company brings together Stripe's experience in global payments and Paradigm's depth in crypto. The Tempo team also builds and maintains Reth, the Ethereum execution client the chain runs on, and Foundry, a smart contract development framework widely used across Ethereum.

Tempo was designed in close collaboration with an initial group of design partners that includes Anthropic, Coupang, Deutsche Bank, DoorDash, Lead Bank, Mercury, Nubank, OpenAI, Revolut, Shopify, Standard Chartered, and Visa. That partner list has since expanded, with dozens of ecosystem partners now spanning asset issuers, on-ramps and off-ramps, compliance providers, wallets and custodians, and privacy solutions.

In April 2026, Stripe, Visa, and Zodia Custody joined Tempo as anchor validators, running the consensus that secures the network. The chain is being built with decentralization as a stated goal: the Tempo client is open source under the Apache license, with a roadmap toward a permissionless validator set.

How Tempo works

Underneath the surface, Tempo is an EVM-compatible blockchain with payment-specific features built directly into the protocol.

The base runs on Reth, the Ethereum execution client built and maintained by the Tempo team. Consensus uses Simplex Consensus, via Commonware. Together they deliver around 0.6-second deterministic finality with no re-orgs, which means once a transaction is confirmed it's settled.

Above that foundation, Tempo adds a set of payment-specific features:

Dedicated payment lanes. Blockspace is reserved at the protocol level for payment transactions. When other applications on the chain get busy, payment fees stay low and stable.

Stablecoin-native gas. Fees are paid in USD stablecoins through a built-in Fee AMM that converts between supported tokens automatically. No separate volatile token to acquire or manage.

TIP-20 token standard. Tempo's native fungible token standard. It extends ERC-20 with transfer memos for reconciliation, compliance controls for issuers, and reward distribution. Stablecoins issued on Tempo use this standard by default.

Modern transactions. Smart accounts come standard. Transactions can be batched into one, scheduled for the future, sponsored by another wallet so users don't need to hold any stablecoin to transact, or signed with passkeys instead of seed phrases.

Built-in stablecoin DEX. A protocol-level exchange optimized for stablecoin-to-stablecoin swaps and tokenized deposits.

Opt-in privacy. Confidential balances and transfers, designed with regulated issuers so compliance and auditability still work.

Because Tempo is fully EVM-compatible, all of this is accessible to anyone already building with Ethereum tooling.

What you can do on Tempo

Tempo positions itself as a payments-first chain, and the use cases it focuses on reflect that. The list ranges from everyday consumer payments to enterprise treasury operations to a new category of agent-driven commerce.

Money movement

• Remittances. Cross-border transfers that settle in seconds instead of days, at a fraction of the cost of traditional wires or correspondent banking.
• Global payouts. Paying out to workers, sellers, creators, and contractors anywhere in the world, in any supported currency, without banking delays or fees.
• Payroll. Faster funding and cheaper cross-border payouts for payroll providers, with 24/7 settlement that works outside of traditional banking hours.

Built-in payments and treasury

• Embedded finance. Companies can build programmable payment flows directly into their products, using any supported stablecoin and without standing up separate ledger infrastructure.
• Microtransactions. Sub-cent payments enabling true pay-per-use pricing for APIs, content, and IoT services.
• Tokenized deposits. Financial institutions can move customer funds onchain for instant settlement and 24/7 interbank transfers, bypassing the limitations of banking-hours systems.

Agentic commerce

• AI agent payments. Tempo's design supports low-cost, instant payments for autonomous agents that need to transact across the internet. This use case has its own dedicated infrastructure on Tempo, covered in the next section.

Machine Payments Protocol (MPP)

The Machine Payments Protocol is an open standard for machine-to-machine payments, co-authored by Stripe and Tempo. It lets any client (an AI agent, app, or human) pay for any service inline with an HTTP request. No API keys, billing accounts, or signup flows.

How it works

A client requests a paid resource. The server responds with HTTP 402 Payment Required and a challenge describing the price. The client pays, retries with a credential, and the server returns the resource along with a receipt. The whole exchange happens in a single request cycle, with no redirects, webhooks, or out-of-band settlement.

Sessions: OAuth for money

For agents that need to make many payments in a row (continuously consuming APIs, model inferences, or data queries), MPP supports sessions. An agent deposits funds into reserve once, then makes payments via signed off-chain vouchers as it consumes resources. The server periodically settles the accumulated vouchers onchain.

The pattern compresses thousands of small payments into a single settlement, enabling true pay-per-use at internet scale.

What MPP enables

• Pay-per-call APIs. Service providers can monetize APIs without requiring account signup or API key management.
• Agent-driven workflows. Autonomous agents can transact across the internet without human intervention.
• Monetized MCP servers. Model Context Protocol servers can charge for queries directly.
• Gated content. Paid resources can be unlocked with a single inline payment instead of subscriptions or paywalls.

At launch, the Payments Directory at mpp.dev lists more than 100 MPP-compatible services across model providers, developer infrastructure, compute platforms, and data services.

An open, rail-agnostic standard

MPP is not tied to any single payment rail. The same protocol works with stablecoins on Tempo (using TIP-20 transfers), cards via Stripe, Bitcoin via Lightning, and custom payment methods anyone can build. The core Payment HTTP Authentication Scheme has been submitted to the IETF for standardization.

For Tempo specifically, the chain is well suited for MPP because of its sub-second deterministic finality (fast enough for synchronous request-response flows), sub-cent fees (low enough for micropayments), and dedicated payment lanes that stay reliable under load.

What to watch next

A few areas worth watching as Tempo moves through its first year of mainnet:

Decentralization milestones. Tempo's first anchor validators are Stripe, Visa, and Zodia Custody (by Standard Chartered), with additional participants expected. Tempo has stated a roadmap toward permissionless validators.

More stablecoin issuers. Tempo's TIP-20 standard is designed for stablecoin issuance, with partners like AllUnity (a BaFin-regulated issuer building a euro stablecoin) and Bridge already building on it. Tempo has indicated more partner stories will be shared over the coming weeks.

Exchange integration. Several major exchanges support Tempo natively for stablecoin deposits and withdrawals. Backpack now supports USDT0 deposits and withdrawals natively on the network. Continued exchange adoption would be a meaningful signal of network growth.

Machine Payments Protocol ecosystem growth. The Payments Directory at mpp.dev launched with more than 100 MPP-compatible services. Adoption by additional AI agent platforms, model providers, and data services will be a leading indicator of how machine-to-machine commerce develops.

Tempo Zones. Tempo launched Zones in April 2026, parallel permissioned chains that let companies run private stablecoin transactions while staying interoperable with Tempo's public mainnet. Watch for the first major enterprises using Zones for confidential payroll, treasury, or merchant settlement.