What is the difference between MnemoPay and Google AP2?

Google AP2 is the Agent Payments Protocol — a wire spec that lets an AI agent route a payment to any of 60+ partner processors (Mastercard, Adyen, PayPal, Coinbase, American Express, Revolut, UnionPay International). It is Apache 2.0 with a public GitHub. MnemoPay is the trust + governance layer above any payment rail. AP2 routes the money. MnemoPay produces the Ed25519-signed receipt, runs agent FICO, holds escrow, enforces HITL approval, and emits EU AI Act Article 12 audit bundles.

Does MnemoPay support AP2?

Yes. MnemoPay ships a GoogleAP2Rail adapter in the SDK. Every AP2 routed payment automatically writes a signed entry to the MnemoPay audit chain, attaches to the agent's reputation, and runs through FiscalGate budget enforcement before the AP2 routing call is even made.

When would I use AP2 alone vs MnemoPay?

Use AP2 alone when you need agent-to-merchant payment routing and your processors are already AP2 partners and you don't need an audit trail, reputation, or budget caps. Add MnemoPay when you need: an Article 12 audit bundle, portable agent identity, escrow with dispute windows, HITL approval for high-value charges, or a spend policy that follows the agent across non-AP2 rails (Stripe direct, Paystack, Lightning, x402).

Can I use AP2 + MnemoPay for EU AI Act compliance?

Yes — AP2 alone does not produce Article 12 audit bundles. MnemoPay's audit chain emits the exact log format Article 12 (Title VII high-risk systems) requires: timestamped events, agent identity, policy version, decision rationale, and a Merkle root that lets a regulator verify the chain hasn't been tampered with. Use AP2 as the rail, MnemoPay as the evidence layer, and you have both compliant routing and compliant logging by August 2 2026 enforcement.

Is AP2 a MnemoPay competitor?

No. AP2 is a wire protocol — it defines how an agent communicates a payment intent to a partner processor. MnemoPay is a software layer — it defines what gets recorded around that payment, how the agent's reputation evolves, and how compliance evidence is produced. They sit at different points in the stack and the MnemoPay SDK explicitly composes with AP2.

Comparison · 2026

MnemoPay vs Google AP2

AP2 routes payments across 60+ processors. MnemoPay produces signed receipts + agent FICO + Article 12 audit. They compose cleanly via the GoogleAP2Rail adapter.

tl;dr

AP2 is the Agent Payments Protocol — announced April 3 2026 with 60+ partners (Mastercard, Adyen, PayPal, Coinbase, AmEx, Revolut, UnionPay). Apache 2.0. Public GitHub.

MnemoPay is the trust layer that records what AP2 routes — Ed25519-signed receipts, agent FICO, escrow, HITL approval, Article 12 audit bundles.

Not substitutes. AP2 routes the payment. MnemoPay produces the evidence.

Feature compare

Capability	AP2	MnemoPay
What layer	Payment routing protocol	Trust + governance layer
Launched	April 3 2026	April 2025
Launch partners	60+ (Mastercard, Adyen, PayPal, Coinbase, AmEx, Revolut, UnionPay)	Rail-agnostic
Money rails covered	Card networks + bank rails of partner list	Stripe, Paystack, Lightning, x402, AP2, custom
Signed receipts	Partner-dependent	Ed25519 + Merkle chain, partner-independent
Agent FICO score	No	Yes — 300-850, payment + behavior weighted
Escrow	No	Yes — built-in, with dispute window
HITL approval	No	Yes — charge_request / charge_approve
EU AI Act Article 12 bundles	No	Yes — exportable, Merkle-verified
Spend policy	Partner-dependent	FiscalGate budgets + per-merchant + categories
License	Apache 2.0	Apache 2.0
SDK install	AP2 client libs	`npm install @mnemopay/sdk`
Best when	Routing across the AP2 partner list	Audit trail + reputation + multi-rail + compliance

Use them together

AP2 is the rail your agent routes through. MnemoPay is the recorder that wraps every routed payment with a signed receipt, FICO update, and audit chain entry. The MnemoPay SDK ships a GoogleAP2Rail adapter:

import MnemoPay, { GoogleAP2Rail } from "@mnemopay/sdk";

const agent = MnemoPay.quick("my-agent");
await agent.useRail(new GoogleAP2Rail({ partner: "adyen" }));

// FiscalGate enforces the budget BEFORE AP2 routes
const tx = await agent.charge(42.50, "weekly api credits");
await agent.settle(tx.id);

// audit bundle exports the AP2 partner refs + signed receipts
const bundle = await agent.exportBundle({ format: "article12" });

When to use which

Use AP2 alone

Your processors are already in the AP2 partner list. You don't need an audit bundle. You don't need agent FICO. You're on a card-network-only stack.

Add MnemoPay

EU operations (Article 12 enforcement Aug 2 2026). Need agent FICO for cross-platform trust. Need escrow + HITL approval. Have non-AP2 rails (x402, Lightning, direct Stripe MPP). Need a Merkle-verified compliance evidence chain.

Also see

npm install @mnemopay/sdk

Apache 2.0 · v1.11.1 · Free self-hosted forever