four agentic payment protocols just shipped. here's what developers actually need to know before picking one.

NOTE: touch is article per recommended_touch. Score 88 ≥85 and product_fit mnemopay qualifies. Flagged needs-human per Dev.to auto-approval cap (0 auto-approved).

four agentic payment protocols just shipped. here's what developers actually need to know before picking one.

AP2 by Google. x402 by Coinbase. MPP by Stripe and Tempo. And a handful of others. PYMNTS called it this week: the agentic payment protocol market is reaching saturation, and consolidation is probably coming.

that's true at the protocol layer. but developers building payment-gated MCP tools aren't picking a protocol — they're picking infrastructure. and the protocol question is maybe 20% of that decision.

here's the other 80%.

the protocol is the wire format. you still need everything else.

every agentic payment protocol solves the same narrow problem: how does an agent carry a payment credential from one service to another without a human re-entering card details every time?

that's genuinely important. but once the wire format is decided, you still need:

spend controls: who sets the limit on what this agent can spend per invocation, per day, per session?
settlement logic: per-invocation, per-session, or monthly subscription — and what happens when the agent fails mid-flow?
reputation scoring: before you let an unknown agent hit your premium endpoint, how do you know it's not a runaway loop or a bad actor?
audit trail: which agent version ran this transaction, under what authorization scope, and can you produce that in 48 hours if a regulator asks?

none of the four protocols above ship a full answer to those four questions. they ship the credential transport. the rest is your problem.

why the MnemoPay approach is different

MnemoPay (part of BizSuite) doesn't bet on a single protocol. the payment layer is protocol-aware but not protocol-locked — when x402 and MPP consolidate down to one winner, the instrumentation layer doesn't need to change.

what MnemoPay ships out of the box:

Agent FICO (300-850): a reputation score for paying agents, calculated from transaction history, failure rate, and authorization scope. services gate on it before settling.
per-invocation settlement: each tool call settles independently. no monthly billing model, no shared wallet state between sessions.
spend limit API: the agent's owner sets a per-invocation cap before it goes to production. if the cap is hit, the payment doesn't go through — no manual intervention required.
structured audit log: every transaction writes a signed log entry. 48-hour audit delivery is built on top of this.

672 tests. v1.0.0-beta.1 shipped. 1.4K weekly npm downloads.

what to do right now while the protocol wars settle

the honest answer is: don't block your MCP monetization on waiting for a protocol winner.

the payment credential format will standardize. the infrastructure around it — spend controls, reputation, settlement logic, audit trail — won't be solved by the protocol spec. build on an abstraction layer that can swap the wire format when the market settles.

install: npm install @bizsuite/mnemopay

docs and live sandbox: https://getbizsuite.com/mnemopay