Tempo Goes Live: A New Era for Machine Payments

On March 18, 2026, Tempo, the payments-first Layer 1 blockchain built by Stripe and Paradigm, launched its mainnet. With it came the Machine Payments Protocol (MPP), an open standard co-authored with Stripe for agent-to-service payments. This is not just another blockchain launch. It is the moment a $95 billion payments company put its full weight behind the idea that machines will be the primary economic actors of the next decade.

Tempo is purpose-built for payments. While general-purpose chains like Ethereum optimize for decentralized computation and Base optimizes for low-cost consumer transactions, Tempo's architecture is designed from the ground up for one thing: moving money between machines at massive scale. The numbers reflect that focus: over 100,000 transactions per second, sub-second finality, and transaction costs measured in fractions of a cent.

The significance goes beyond raw throughput. Stripe processes over $1 trillion in payment volume annually. Paradigm has backed some of the most consequential companies in crypto. When these two build a blockchain together, the signal to the market is unmistakable: machine payments are not a niche experiment. They are the next major payment paradigm.

For the agentic commerce ecosystem, Tempo's launch represents a third major infrastructure option alongside Base (Coinbase's x402-native chain) and Solana (the high-speed chain with 35 million-plus x402 transactions). Each chain brings different strengths, different ecosystems, and different visions for how agent payments should work.

What Is the Machine Payments Protocol?

MPP (the Machine Payments Protocol) is an open standard co-authored by Stripe specifically for agent-to-service payments. It defines how machines request, authorize, and settle payments with other machines. If x402 brought payments into HTTP and ACP brought shopping flows to agents, MPP brings continuous, session-based payment relationships to the machine economy.

A critical motivation behind MPP is that x402, the dominant agent payment protocol, is crypto-only. x402 settles exclusively in stablecoins on blockchains like Base and Solana. For Stripe, a company whose entire business is built on traditional payment rails (credit cards, bank transfers, digital wallets), this was a non-starter. The vast majority of merchants and businesses that Stripe serves do not accept crypto. Building a protocol that excluded those merchants would mean building a protocol that excluded most of the economy. MPP exists in large part because Stripe needed an agent payment standard that could work with the payment methods its millions of merchants already accept, not just crypto.

At its core, MPP solves a problem that existing protocols handle incompletely: ongoing payment relationships between an agent and a service. When an agent uses an API continuously, making hundreds or thousands of calls per hour, individual per-request payments (as in x402) create unnecessary overhead. MPP introduces payment sessions: an agent opens a session with a service, pre-authorizes a spending budget, and the service draws against that budget as the agent consumes resources. Settlement happens periodically or when the session closes, not on every request.

MPP is payment-method agnostic by design. It works with multiple payment rails:

• Crypto: stablecoins on Tempo and other chains
• Card payments: traditional credit and debit via the Visa network extension
• Fiat wallets: cards, wallets, and bank transfers via the Stripe network extension
• Bitcoin Lightning: instant, near-zero-fee payments via the Lightspark network extension

This flexibility is deliberate. Stripe and Paradigm understood that forcing all agent payments through a single payment rail would limit adoption.

The protocol uses HTTP-based control flow, making it familiar to any developer who has built web services. Payment requests, session management, and settlement notifications all flow over standard HTTP endpoints. There is no proprietary SDK required, no custom binary protocol, and no blockchain-specific tooling needed to implement the basics.

MPP launched with a payments directory listing over 100 services (APIs, data providers, compute resources, and agent tools) that accept MPP payments from day one. This directory is machine-readable, so agents can discover MPP-enabled services programmatically, understand their pricing, and initiate payment sessions without human configuration.

MPP Key Features: Sessions, Flexibility, and Directory

Three features distinguish MPP from other agent payment protocols:

1. Payment sessions. Unlike per-request payment models (x402) or per-checkout flows (ACP), MPP supports continuous payment relationships. An agent opens a session, defines a budget, and consumes services over time. The service provider tracks usage and settles against the session budget. This model maps naturally to how agents actually work: they do not make isolated one-off purchases but engage in sustained, multi-step workflows that consume resources continuously. Sessions can be time-bounded (one hour, one day) or task-bounded (until the agent completes a specific goal), giving both agents and service providers flexibility in how they structure their commercial relationships.

2. Payment-method agnosticism. MPP defines the protocol for requesting and authorizing payments but does not mandate how value actually moves. This is handled by network extensions, pluggable modules that connect MPP to specific payment rails. At launch, three network extensions are available:

• Visa: card payment support through the Visa Intelligent Commerce infrastructure
• Stripe: cards, wallets, and bank transfers through Stripe's existing payment processing stack
• Lightspark: Bitcoin Lightning support for instant, near-zero-fee payments over the Lightning Network

Additional network extensions can be built by anyone since the specification is open.

3. The payments directory. MPP includes a built-in service discovery mechanism, a machine-readable directory where services register their capabilities, pricing, and payment terms. At launch, over 100 services are listed. This solves the cold-start problem that plagues new payment protocols: agents do not need to be pre-configured with service endpoints and payment details. They can discover services, compare pricing, and initiate payments dynamically.

Tempo's Architecture: Built for Machine Scale

Tempo's blockchain architecture reflects its singular focus on payments. While general-purpose chains must balance computation, storage, and consensus across diverse use cases, Tempo optimizes every layer for payment throughput and finality.

The chain achieves over 100,000 transactions per second with sub-second finality. For context, Visa's global network handles approximately 65,000 transactions per second at peak. Tempo's capacity exceeds this by a significant margin, anticipating a future where machine-to-machine transactions vastly outnumber human-initiated ones. Solana, the current speed leader in the agentic commerce ecosystem, processes around 4,000 transactions per second in practice. Base handles roughly 100 transactions per second. Tempo represents a generational leap in raw throughput.

Sub-second finality is critical for machine payments. When an agent makes a payment, it needs confirmation that the payment succeeded before proceeding to the next step of its workflow. Multi-second or multi-minute confirmation times, acceptable for human transactions where the user can wait, are unacceptable for agents executing hundreds of operations per minute. Tempo's consensus mechanism is optimized for this use case, providing definitive settlement in under one second.

Transaction costs are designed to be negligible at scale. Tempo's fee structure assumes millions of micropayments per day, not thousands of large-value transfers. The economic model works when the cost of a payment is measured in fractions of a cent, enabling business models like pay-per-API-call, pay-per-token, and pay-per-second that are uneconomical on chains with higher transaction fees.

Tempo also provides native stablecoin support. USDC is available on Tempo from launch, with additional stablecoin integrations planned. This eliminates the need for agents to manage volatile native tokens for gas payments, a significant usability improvement over chains where agents must hold ETH, SOL, or other volatile assets to pay transaction fees.

Launch Partners: The Who's Who of Global Finance and AI

Tempo's launch partner list reads like a directory of the most consequential companies in finance and AI. This is not a typical crypto launch with a handful of DeFi protocols and NFT marketplaces. This is a coordinated go-live with institutions that collectively process trillions of dollars and serve billions of users.

The launch partners span every major sector of the economy:

• AI Labs: Anthropic and OpenAI, the two leading frontier AI labs. Their participation signals that the model providers themselves see machine payments as a core capability, not an afterthought. Agents built on Claude and GPT will have native pathways to Tempo and MPP.
• Card Networks: Visa and Mastercard, the two largest card networks. Visa provides a network extension for MPP, enabling card-based agent payments. Mastercard extends the reach to its merchant network. Together, they cover the vast majority of card-accepting merchants globally.
• Payments and Commerce: Stripe (which co-built Tempo) brings its payments infrastructure and merchant base of millions of businesses. Shopify, which powers millions of online stores, provides a direct path for agents to purchase from Shopify merchants.
• Real-World Logistics: DoorDash brings food delivery, groceries, and physical goods into the picture, demonstrating MPP is not limited to digital goods and API access.
• Financial Services: Nubank (Latin America's largest digital bank, 100 million-plus customers), Revolut (European digital banking leader), Standard Chartered (global banking), and UBS (wealth management). Their participation suggests traditional finance sees agent payments as a near-term reality.
• Bitcoin Bridge: Lightspark, built by former Meta executives, provides the Bitcoin Lightning network extension for instant, near-zero-fee payments over Bitcoin's second layer, bridging the Bitcoin ecosystem into MPP without requiring agents to deal with Bitcoin's slower base-layer settlement.

Use Cases: What Agents Can Do with Tempo and MPP Today

MPP's session-based model and broad network extension support unlock several categories of agent commerce that were impractical or impossible with existing protocols.

Pay-per-call APIs become frictionless. An agent that needs to query a weather API, a flight search engine, a legal database, or a code generation service can open an MPP session, make hundreds of calls, and settle at the end. The service provider does not need to issue API keys, manage subscription tiers, or handle billing because MPP handles payment as a native part of the request flow. With over 100 services in the directory at launch, agents have a significant catalog of MPP-enabled tools from day one.

Monetized MCP servers are a natural fit. MCP (Model Context Protocol) defines how agents connect to tools and data sources. MPP adds a payment layer on top, so tool providers can charge per invocation, per data record, or per compute second. A flight search MCP server could charge $0.001 per search query. A document analysis tool could charge $0.01 per page processed. These micropayments are economically viable on Tempo where transaction fees are negligible.

Gated content unlocks new business models for publishers. Instead of paywalls that block entire articles or subscription models that charge monthly fees, MPP enables per-article, per-section, or even per-paragraph pricing. An agent researching a topic could pay $0.05 to access a relevant article, $0.10 for a research report, or $0.001 for a data point, all within a single session.

Multi-service agent workflows become economically coherent. Consider an agent tasked with planning a business trip:

1. Search flights (pay-per-search via MPP session)
2. Book the optimal flight (card payment via Visa extension)
3. Reserve a hotel (card payment via Stripe extension)
4. Arrange ground transportation (DoorDash integration)
5. Generate an expense report (API call)

Each step involves a different service and potentially a different payment method, but MPP provides a unified framework for the entire workflow.

Agent-to-agent payments become first-class citizens. When one agent hires another agent for a subtask (a research agent hiring a data analysis agent, for example) MPP provides the commercial infrastructure. The hiring agent opens a session with the worker agent, defines a budget, and the worker agent draws against that budget as it performs the work. No invoicing, no reconciliation, no manual payment initiation.

How Tempo Compares to Base and Solana in the Agentic Stack

With Tempo's launch, the agentic commerce ecosystem now has three major blockchain options, each with distinct strengths and positioning.

Base, built by Coinbase, is the home of x402, the HTTP-native micropayment protocol. Base's strength is its deep integration with Coinbase's ecosystem: Coinbase wallets, Coinbase exchange, Coinbase Commerce, and the x402 standard. If your agent operates in the Coinbase ecosystem, Base is the natural choice. Base handles roughly 100 transactions per second with low fees and has a growing developer community. The x402 protocol on Base is battle-tested with millions of transactions.

Solana is the speed and cost leader of the current generation. With 400-millisecond finality, fees of approximately $0.00025 per transaction, and over 35 million x402 transactions processed, Solana has proven its viability for agent micropayments. Solana's strengths are its speed, its low cost, its large developer community, and its rich DeFi ecosystem. Phantom, the leading Solana wallet, has been actively building agent-facing tools including an MCP server for wallet operations.

Tempo enters as the payments-specialized option. Its raw throughput (100,000-plus TPS) dwarfs both Base and Solana. Its session-based MPP protocol addresses use cases that x402's per-request model handles less elegantly. Its network extensions for Visa, Stripe, and Lightspark provide bridges to traditional payment infrastructure that neither Base nor Solana match. And its launch partner list (Anthropic, OpenAI, Visa, Mastercard, Shopify, DoorDash) represents a breadth of ecosystem support that is unprecedented for a new chain.

However, Tempo is brand new. Base and Solana have years of battle-testing, established developer tooling, and proven reliability. Tempo's 100,000-plus TPS claims need to be validated under real-world load. Its smart contract capabilities are more limited than general-purpose chains, by design. And its ecosystem, while impressive in launch partners, has yet to develop the depth of tooling, tutorials, and community support that Base and Solana offer.

The likely outcome is not winner-take-all but specialization. Base for the Coinbase ecosystem and x402-native applications. Solana for high-speed, low-cost agent transactions with deep DeFi integration. Tempo for enterprise-grade payments, multi-payment-method flows, and applications that need bridges to traditional financial infrastructure. Infrastructure layers like UCP and multi-chain routers will abstract away the chain choice for most agents, routing payments to the optimal chain based on cost, speed, and counterparty requirements.

What Tempo Means for the Future of Agent Payments

Tempo's launch is significant not just for what it is but for what it signals about the trajectory of machine payments.

Four signals stand out:

1. Institutional credibility is flowing into agent payments. Stripe is not a crypto-native startup experimenting with a novel idea. It is the backbone of internet commerce, processing payments for millions of businesses. When Stripe builds a blockchain, the message to every CFO, CTO, and product manager is clear: machine payments are coming to your business, and the infrastructure is being built by companies you already trust.

2. MPP's open-source specification lowers the barrier to entry. The protocol specs are available on GitHub, and anyone can implement an MPP-compatible service or build a network extension. This openness is critical because closed payment protocols create vendor lock-in, while open protocols create ecosystems. If MPP achieves broad adoption, it could become the HTTP of machine payments: a shared standard that everyone builds on.

3. The network extension model is genuinely innovative. Rather than forcing all payments through crypto rails (as x402 does) or through traditional rails (as AP2 does), MPP creates a pluggable architecture where any payment method can participate. This pragmatism reflects Stripe's DNA: meet merchants and payers where they are, rather than demanding they adopt new payment methods.

4. The launch partner list demonstrates that agent payments are no longer a crypto-only conversation. When Visa, Mastercard, DoorDash, Shopify, Nubank, Revolut, Standard Chartered, and UBS are all in the room, the conversation has shifted from "should machines have payment capabilities?" to "how do we give machines payment capabilities safely and at scale?"

The question is no longer whether AI agents will transact autonomously. It is which protocols, which chains, and which standards will mediate those transactions. Tempo and MPP have staked a strong claim. The next twelve months will determine whether that claim holds.

MPP Specifications: Open Source and Developer-Ready

One of the most consequential decisions behind MPP is its open-source release. The full protocol specification is available on GitHub, licensed for anyone to implement, extend, or fork. This stands in contrast to many payment protocols that lock their specifications behind enterprise agreements or restrict implementation to approved partners.

The MPP specification defines several core components. The payment request format describes how a service communicates its pricing, accepted payment methods, and session terms to an agent. The session lifecycle defines how sessions are opened, maintained, extended, and closed, including handling for edge cases like network interruptions, budget exhaustion, and disputed charges. The settlement protocol defines how accumulated charges within a session are finalized and how value is transferred between parties.

Network extensions follow a defined interface specification. Any organization can build a network extension that connects MPP to a new payment rail, whether that is a regional bank transfer system, a mobile money network, a cryptocurrency, or a novel payment method that does not exist yet. The three launch extensions (Visa, Stripe, Lightspark) serve as reference implementations.

The payments directory uses a standardized schema that services use to register their capabilities. Each directory entry includes the service's endpoint, supported MPP version, accepted payment methods (which network extensions it supports), pricing model (per-request, per-second, per-unit, subscription), and machine-readable description of what the service does. Agents can query the directory to discover services, compare pricing, and select the best option for their needs.

For developers, getting started with MPP is straightforward. A basic MPP-enabled service can be implemented in under 100 lines of code using the reference libraries. A basic MPP-enabled agent needs a wallet (for crypto payments), or an existing Stripe or Visa integration (for traditional payments), plus the MPP client library. The documentation includes quickstart guides, code samples in multiple languages, and a testnet for development and testing.

Security, Compliance, and the Enterprise Angle

Tempo and MPP were built with enterprise requirements in mind from day one, a notable departure from the typical crypto-first approach of most blockchain launches.

On the compliance front, MPP includes hooks for KYC/AML verification at the session level. When an agent opens a payment session, the service can require identity verification through the agent's ERC-8004 registration, a KYA (Know Your Agent) attestation, or a traditional KYC check on the agent's operator. This compliance layer is optional (low-value micropayments can proceed without it) but it ensures that MPP can meet regulatory requirements for higher-value transactions.

Tempo's consensus mechanism includes transaction monitoring capabilities that enable real-time compliance screening. Suspicious transaction patterns can be flagged, and compliance teams can audit transaction histories through standard blockchain explorers and analytics tools. Cleared, a compliance-focused company in the Payment Infrastructure category, has already integrated with Tempo to provide BSA/OFAC screening for agent transactions.

The enterprise angle extends to Tempo's governance model. Unlike fully decentralized chains where governance happens through token-weighted voting, Tempo uses a hybrid model that includes institutional stakeholders (Stripe, Visa, Mastercard, and other launch partners) in governance decisions. This is controversial in the crypto community but reassuring to enterprises that need predictable governance and clear accountability.

For security, Tempo inherits standard blockchain security properties: immutability, cryptographic verification, and transparent transaction histories. MPP sessions add an additional security layer: each session has explicit bounds (maximum budget, time limit, allowed operations), and the service cannot draw more than the authorized amount. If an agent is compromised, the blast radius is limited to the current session's budget, not the agent's entire wallet.

Stripe's existing security infrastructure (fraud detection, dispute resolution, chargeback handling) is available through the Stripe network extension. This means agents paying with traditional payment methods through MPP get the same fraud protections that Stripe provides to human buyers. Visa's network extension includes Visa's own fraud detection and tokenization capabilities.

Key Companies and Organizations Behind Tempo

Tempo's ecosystem spans the full spectrum of finance, technology, and AI.

Stripe co-built Tempo and co-authored MPP. As the payments infrastructure behind millions of internet businesses, Stripe brings unmatched merchant reach and developer trust. Stripe's CEO Patrick Collison has described Tempo as "the payment network for the next era of the internet, one where software doesn't just assist transactions but initiates them."

Paradigm, the crypto-focused venture firm, co-built Tempo and provides the blockchain engineering expertise. Paradigm's portfolio includes some of the most important infrastructure projects in crypto, and its involvement signals deep technical credibility.

Visa provides the card payment network extension for MPP and brings its Intelligent Commerce infrastructure, the same platform used by Lobster.cash for agent virtual debit cards. Visa's participation means agents can pay at any of Visa's 100 million-plus merchant locations worldwide.

Mastercard mirrors Visa's role, extending MPP's reach to its global merchant network. Together, Visa and Mastercard cover virtually every card-accepting merchant on the planet.

Anthropic (Claude) and OpenAI (GPT) are both launch partners, ensuring that the two leading AI model families have optimized pathways to Tempo and MPP. This is notable because Anthropic has been closely associated with MCP and the x402 ecosystem, while OpenAI has been aligned with ACP and Stripe. Their dual participation in Tempo suggests MPP may become a bridge between these previously distinct ecosystems.

Shopify provides the e-commerce layer, giving agents direct access to millions of online stores. DoorDash provides real-world logistics and delivery. Nubank, Revolut, Standard Chartered, and UBS represent the banking sector's early commitment. Lightspark brings Bitcoin Lightning connectivity, completing the bridge between crypto-native and traditional finance.

The Bigger Picture: What Tempo Tells Us About the Agent Economy

Zoom out from the technical details and Tempo's launch tells a story about where the agent economy is heading.

The era of experimentation is giving way to the era of infrastructure. The first wave of agentic commerce (x402 on Base, ACP on Stripe, AP2 at Google) proved the concept. Agents can transact. The question is no longer "can they?" but "at what scale, with what reliability, and through what infrastructure?" Tempo is built for the scale phase: 100,000-plus TPS, sub-second finality, institutional launch partners, and enterprise-grade compliance.

Payment pluralism is winning over payment maximalism. Early agentic commerce discussions were often framed as crypto vs. fiat, x402 vs. ACP, Base vs. Solana. Tempo and MPP reject this framing entirely. Through network extensions, MPP supports crypto, cards, bank transfers, and Bitcoin Lightning simultaneously. The message is clear: agents should use the best payment method for each transaction, and the protocol should be agnostic.

Traditional finance is not watching from the sidelines; it is building. Stripe, Visa, Mastercard, and a roster of major banks are not just endorsing Tempo; they are active participants building network extensions and integrating MPP into their existing infrastructure. This institutional involvement accelerates adoption in ways that crypto-only solutions cannot, bringing regulatory clarity, merchant acceptance, and consumer trust.

The race for developer adoption is the real competition. Tempo's success will ultimately be determined not by its throughput numbers or its launch partner list but by whether developers build on it. The open-source MPP specification, the reference libraries, the 100-plus service directory, and the developer documentation are all bids for developer attention. In an ecosystem where Base has Coinbase's developer tools, Solana has its mature toolchain, and Ethereum has the largest developer community in crypto, Tempo needs to offer a compelling developer experience to compete.

For anyone building in agentic commerce today, Tempo and MPP are impossible to ignore. They may not replace the existing x402 and ACP ecosystems, but they introduce a third option that combines the best of crypto infrastructure (programmability, speed, global reach) with the best of traditional finance (institutional trust, regulatory compliance, universal merchant acceptance). The next twelve months will reveal whether Tempo becomes a foundational pillar of the agent economy or a well-funded entrant that could not dislodge incumbents. Either way, the bar for what agent payment infrastructure must deliver has just been raised significantly.