Agentic payments protocols map (ACP, AP2, x402, MPP)

The 2025–2026 landscape is a protocol contest, not a single standard. This map helps you place announcements without memorizing every acronym.

Dates and names move fast—verify primary sources. Not legal/financial advice.

Layer cake

Layer	Question	Examples
Identity	Who is the agent acting for?	Platform agent IDs, Cloudflare handles, network TAP
Commerce intent	What is being bought?	ACP-style cart/checkout in assistants
Payment authorization	How is money approved?	Tokenized cards, wallet policies
Settlement rail	How does value move?	Cards, bank, stablecoins, x402 micropayments
Merchant acceptance	Can the seller receive it?	Gateways, Monetization Gateway, PSPs

Named stacks (orientation)

Name	Rough role
ACP (Agentic Commerce Protocol)	OpenAI + Stripe lineage—assistant commerce / checkout patterns
AP2 / agent payment protocols (Google et al.)	Agent-to-payment collaboration standards efforts
x402	HTTP-native payment required / micropayment patterns for machines
MPP (Machine Payments Protocol)	Stripe/Tempo-class machine-to-machine payment coordination
Mastercard Agent Pay / Visa agent programs	Card-network agentic payment programs
Cloudflare Wallets + Monetization Gateway	Edge identity + wallet + seller micropayments narrative

Comparison questions (use these, not hype)

Human-in-the-loop required each purchase?
Card rail, account balance, or crypto/stablecoin?
B2C shopping vs B2B API metering?
Who is liable for unauthorized agent spend?
Is it shipping in production or pilot language only?

AI prompt for reading a press release

Summarize this payments announcement into: problem, identity model, money movement, human controls, GA vs announced, open questions for a CFO and a security lead.
Do not invent product availability. Text: [paste]

Published by Tabaconda LLC, Florida, USA.

Practical next steps

Read one primary vendor or standards document this week—not only summaries.
Write a one-page policy for any agent that can move money (spend controls).
Separate announced features from what your account can enable today.
Log experiments; do not fund unconstrained wallets.
Revisit this page when product status changes—timestamps matter in payments infrastructure.

Editorial limits

Pay By Prompt provides general technology orientation for a fast-moving space. It is not an offer of payment services, investment advice, or legal counsel. Confirm availability, licensing, and compliance obligations with qualified professionals and official documentation.

How to use a protocols map

Do not treat names as interchangeable. For each protocol or program track:

Problem it claims to solve
Who must implement (merchant, wallet, network, agent)
Status: draft / pilot / GA signals from primary sources
Fit to your threat model

Comparison worksheet

Name	Primary sources	Your notes	Last checked

Update monthly while the space moves fast.

Stripe & assistant commerce · Card network agent pay · Cloudflare Wallets

Published by Tabaconda LLC, Florida, USA.

Naming hygiene

Acronyms proliferate. Maintain an internal glossary with links to primary specs and “last verified” dates. Public pages on this site aim to stay readable without pretending every draft protocol is production law.

When to ignore a protocol

If it has no implementers you can test, no threat model, and no operational story for refunds and disputes, file it under watchlist rather than roadmap.

Field notes for protocols acp ap2 x402

Teams and households using this guide should adapt checklists to local rules. Write down owners for each action item, dates for verification, and links to primary sources. Prefer short experiments with clear freeze criteria over open-ended automation. When something is uncertain, label it uncertain and schedule a human follow-up rather than guessing. Revisit this section after your next real-world attempt and capture what broke—process improves only when notes exist.

Checklist you can copy

State the goal in one sentence.
List constraints (budget, time, tools, legal).
Identify what AI may draft vs what a human must approve.
Define success metrics before you start.
Archive prompts, decisions, and outcomes together.
Schedule a retrospective within seven days.

Common mistakes on this topic

Skipping primary sources
Treating marketing pages as contracts
Expanding scope mid-flight without new caps
Failing to document exceptions
Assuming last month’s product status still holds

Cross-link to related guides on this site from the Related section above, and keep the home hub path map handy so readers can continue without orphaning their journey.

Published by Tabaconda LLC, Florida, USA. General education only.