Machine Payments Protocol (MPP)

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Watch

Primary summary from verified readiness

Evidence strength Strong

Decision

Human editorial judgment · 2026-08-20

Wait for stronger evidence

Why: MPP has serious backing (Stripe, Visa, Mastercard, Deutsche Bank, Standard Chartered, OpenAI, Anthropic as design partners) and aligns with our machine-payments thesis, but it is months old, single-chain in practice, carries Stripe/Tempo vendor lock-in, and shares the slot with x402 — adopting now risks re-plumbing protected payment code twice.
Next: Read the MPP open spec + HTTP 402 flow and compare its mandate/settlement model against our AP2/ACP abstraction (Rule #4 60% sharing). Do NOT integrate until non-Tempo rail support and idempotency/settlement-finality semantics (Rule #3) are documented and tested; track whether MPP and x402 converge or whether a hybrid middleware (supporting both) becomes the de-facto pattern.

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Initial public reading