Introducing the Machine Payments Protocol

Source
machine-paymentsstripeagentic-commercemppmicropaymentsstablecoinspayment-protocolsm2m

Summary

Stripe and Tempo have launched the Machine Payments Protocol (MPP), an open standard for AI agents to make payments programmatically via HTTP 402 responses, supporting both fiat (cards, BNPL via Shared Payment Tokens) and stablecoins. The protocol is submitted to IETF and aims to eliminate the need for agents to navigate human checkout flows, enabling microtransactions, per-use API access, and eventually subscriptions.

Key Insight

  • The real value isn’t for agents specifically - MPP removes the need for account creation and API key setup. An agent (or any machine client) can hit an HTTP endpoint, get a 402 “Payment Required” response with pricing details, pay, and access the resource. This is useful for any programmatic access, not just LLM agents.
  • Competing standards exist: L402 (Bitcoin Lightning), x402 (any blockchain). MPP’s advantage is Stripe backing = existing merchant infrastructure, fiat support, and familiar dashboard/reporting.
  • The unsolved problem is authorization, not payment: MPP handles the “how to pay” but not “should the agent pay this?” Spending caps, human-in-the-loop approval for high-value transactions, and budget management are left to the agent harness/framework - a separate infrastructure layer that doesn’t exist yet in a standardized way.
  • Killer use case: agents accessing paywalled content (journalism, research papers, premium APIs) on a per-query basis without monthly subscriptions. This is better for bursty workloads and removes the “I can’t access that” problem that plagues research agents today.
  • HN skepticism is valid: the protocol is thin (essentially a structured 402 response), the RFC appears AI-generated, there’s no refund/dispute mechanism, and it lacks B2B essentials like invoices and receipts. For now it only handles one-way money transfer.
  • Business model shift: services can now monetize per-request from agents without requiring account signup. Browserbase (headless browsers) and PostalForm (physical mail) already use this.