Agentic Payments — Master Source Brief (for sub-agent writers)

Last updated: 2026-04-21. Use this as a starting point. Verify everything you cite. Do NOT invent sources or URLs. If unsure, say "as reported by [X]" and link an archived/secondary source. When you cannot verify, omit rather than invent.


A. Verified Industry Protocols & Programs

1. Google — Agent Payments Protocol (AP2)

2. OpenAI + Stripe — Agentic Commerce Protocol (ACP)

3. Visa — Trusted Agent Protocol & Visa Intelligent Commerce

4. Mastercard — Agent Pay

5. American Express — Agentic Commerce program

6. PayPal — Agent Toolkit + MCP server

7. Coinbase — x402 protocol

8. Skyfire

9. Nekuda

10. Catena Labs (Sean Neville, ex-Circle)

11. Crossmint

12. Cloudflare — pay-per-crawl + Web Bot Auth + AI Agent Identity

13. Walmart × OpenAI Instant Checkout (Oct 14, 2025)

14. Universal Commerce Protocol (UCP) — Google + Shopify

15. Stripe — Agent Toolkit + Issuing for agents


B. Verified Academic / Standards Papers (as of 2026-04-21)

Citation rule: ONLY cite papers you can find at the exact URL given. If the URL fails, drop it.

C. Industry Reports & Analyses

D. Definitions to use consistently

  • Agentic payment: a payment initiated, executed, and/or authorized by an autonomous software agent (typically LLM-driven) acting on behalf of a principal under delegated authority.
  • Mandate (AP2 sense): a verifiable credential signed by a user (and possibly a merchant) that authorizes specific agent behavior.
  • Human-Present (HP) vs Human-Not-Present (HNP) flows.
  • Merchant of Record (MoR) retention.
  • Facilitator (x402): non-custodial settlement intermediary.
  • KYA (Know-Your-Agent): extension of KYC to agents — identity, principal, scope.
  • MCP: Anthropic's Model Context Protocol (Nov 2024 release). https://modelcontextprotocol.io
  • A2A: Google's Agent-to-Agent protocol (Apr 2025).

E. Hard rules for sub-agent writers

  1. Every claim of fact (date, partner, fund amount, technical detail) must cite a URL from this brief OR be verified via web_search/web_fetch and cited.
  2. Use Markdown footnote-style references [^1] with full URL in a Sources section at end of your section.
  3. Do not cite arXiv IDs that you have not personally fetched (use web_fetch on the abstract page).
  4. If a fact is disputed across sources, present both with citations.
  5. Cross-reference other sections by their filename, e.g. (see [Card Networks](04-card-networks.md)).
  6. Word target is a floor not a ceiling — but quality > quantity.
  7. Use UK or US English consistently within your section; be technically precise.
  8. Tables, code blocks, and protocol diagrams (mermaid) are encouraged.