Tempo mainnet ships with Stripe-coauthored Machine Payments Protocol
A payments chain plus an HTTP 402 protocol that is rail-agnostic across cards and stablecoins.
protocol
Machine Payments Protocol
Open machine-payment protocol co-authored by Stripe and Tempo, using HTTP 402 and multiple payment methods.
Machine: /v1/intelligence/entity/mpp · Graph: /v1/graph/entities/mpp
Graph relationships
- evt-mastercard-agentic-payments
- evt-mcp-paid-tools-gap
- evt-openai-apps-agents-commerce
- evt-stablecoin-agent-wallets-pattern
- evt-stripe-mpp-blog
- evt-tempo-mainnet-mpp-2026-03-18
- http
- stripe
- tempo
Timeline
Stripe documents MPP as an internet-native way for agents to pay
PaymentIntents, Shared Payment Tokens and stablecoins without a checkout UI.
Agent wallets converge on stablecoins plus policy limits
Visa tokens, x402 USDC and MPP SPTs are different wrappers on the same control problem.
Agent commerce protocols proliferate beyond crypto-native stacks
Stripe ACP, Visa Intelligent Commerce, MPP and x402 now sit in one landscape.
Mastercard is named as a Tempo/MPP design partner for agent payments
Card-network participation in MPP is a distribution signal, not a live volume print.
Paid MCP is still an overlay, not a core MCP feature
The protocol gives tools/list and tools/call. Payment is someone else’s 402.