Disclosure: I work on Pink Agentic AI Payments at PinkWallet, which is one of the 33 entries below (spend-control layer). Every entry links to a primary source: the company's own docs, blog or press release. Pink is described with the same fields as everyone else, including that it is early access with a test-money sandbox. The full table with check dates lives at pinkwallet.com/agentic/learn/agentic-payments-market-map-2026.
Short answer: "AI agent payment platform" covers seven different jobs. In 2026 the main players are: protocols (x402, AP2, ACP, MPP, UCP), card-network programs (Visa Trusted Agent Protocol, Mastercard Agent Pay), agent wallets (Coinbase, Circle, Crossmint, Fireblocks, Privy, Turnkey, Catena, Payman), payment MCP servers (Stripe, Square, Mollie, Razorpay, Airwallex, Plaid), spend-control and approval layers (Pink, Locus, PolicyLayer, SpendNod, goodmeta), agent identity / KYA (Skyfire, Cloudflare) and agentic checkout (Adyen, PayPal, Checkout.com, Stripe).
If you are choosing one, first decide which job you need done. A protocol does not hold money, a wallet does not decide whether a purchase is allowed, and an MCP server only exposes a PSP's existing API. Most production setups combine three layers: a rail (card or wallet), a way for the agent to call it (MCP or API), and a control layer that says yes, ask a human, or no before money moves.
Entries were last checked against their primary sources on 2026-09-28 (Pink's sandbox re-checked 2026-10-01). Status labels are quoted from each vendor's own wording.
Protocols & standards (5)
- Coinbase / x402 Foundation — x402: Lets servers request stablecoin payment via HTTP 402 before returning a resource. Status: Live; governed by x402 Foundation (Linux Foundation). Source
- Google / FIDO Alliance — AP2 (Agent Payments Protocol): Proves via signed mandates that a user authorized an agent's purchase. Status: Live; donated to FIDO Alliance. Source
- OpenAI + Stripe — ACP (Agentic Commerce Protocol): Standardizes agent-to-merchant checkout inside a chat interface on card rails. Status: Live spec; OpenAI and Stripe as Founding Maintainers. Source
- Stripe + Tempo — MPP (Machine Payments Protocol): Standardizes HTTP 402 machine-to-machine payments over stablecoins, cards and BNPL. Status: Published March 18, 2026. Source
- Google — UCP (Universal Commerce Protocol): Open-source checkout standard for agentic commerce, compatible with AP2. Status: Announced January 11, 2026. Source
Card-network agent programs (2)
- Visa — Trusted Agent Protocol (TAP): Lets merchants cryptographically verify a request comes from a trusted agent. Status: In development and deployment. Source
- Mastercard — Agent Pay (Agentic Tokens): Issues permissioned, tokenized credentials so agents pay within set limits. Status: Announced 2025; "Agent Pay for Machines" launched 2026. Source
Agent wallets & stablecoin rails (9)
- Coinbase — AgentKit / Agentic Wallet: USDC wallet for agents with per-session caps and OFAC screening. Status: GA-toned; no beta label found. Source
- Circle — Agent Wallets (circlefin/skills): Sets time-bound USDC spend limits and address allow/blocklists for agents. Status: Not labeled GA/beta. Source
- Crossmint — Agent Wallets & Checkout: Non-custodial stablecoin wallets with scoped, revocable card allowances for agents. Status: Not labeled GA/beta. Source
- Fireblocks — Agentic Payments Suite: MPC wallets let agents pay any x402/MPP merchant with an audit trail. Status: Early access (request access). Source
- Privy — AI Agent Wallets: Embedded wallets with a policy engine for agent transfer limits and approvals. Status: GA (production volume cited, no beta label). Source
- Turnkey — Agentic Payments (Policy Engine): Scopes what each agent wallet can sign by address, contract, spend limit. Status: Launched. Source
- Catena Labs — Catena: Governance and banking platform giving agents accounts, payments, stablecoin rails. Status: GA-toned; pursuing a bank charter. Source
- MetaMask (Consensys) — Agentic wallet architecture: Describes a control layer defining what an agent may do before signing. Status: Explainer; multiple custody models cited in production. Source
- Payman — Genie MCP bridge: Agentic-AI banking; natural-language MCP bridge to a remote Genie server. Status: Not labeled GA/beta. Source
Payment MCP servers & agent toolkits (6)
- Stripe — Stripe MCP server: Exposes the Stripe API to agents; write actions need human confirmation. Status: GA (some sub-tools in Preview). Source
- Square (Block) — Square MCP Server: Gives agents Square API access behind a connecting-client allowlist. Status: Beta. Source
- Mollie — Mollie MCP Server: Connects AI tools to a Mollie account using natural language. Status: Not labeled GA/beta. Source
- Razorpay — Razorpay MCP Server: Integrates Razorpay payment APIs with AI tools via MCP. Status: Not labeled; READ_ONLY flag available. Source
- Airwallex — AgentOS MCP: Money-out actions disabled by default; write tools need confirmation. Status: Beta. Source
- Plaid — Dashboard MCP server: Diagnostics and analytics tools only; does not move money. Status: Active development; limited support. Source
Spend control, policy & approval (5)
- PinkWallet — Pink Agentic AI Payments: MCP server (7 tools) + REST API + console: per-agent budgets and vaults, plain-language rules (first match decides, unlisted is blocked), fraud checks before amount tiers, human approval on the phone, 15 published industry setups. Status: Early access; public sandbox live, confirmed by us 2026-10-01 (test credentials); production not yet available. Source
- Locus — Locus: Three-layer policy engine checks every agent transaction against a budget. Status: GA; Y Combinator-backed. Source
- PolicyLayer — PolicyLayer: Checks every agent MCP tool call against policy before it runs. Status: Live, self-serve. Source
- SpendNod — SpendNod: Open-source, self-hosted human-in-the-loop authorization gateway for agent transactions. Status: Free, MIT-licensed. Source
- goodmeta — agent-verifier-mcp: MCP server enforcing a budget-authority protocol; tracks agent spend across services. Status: Open source on GitHub. Source
Agent identity / KYA (2)
- Skyfire — KYA + KYA-Pay tokens: Attaches verified identity to agents and funds per-agent spend limits. Status: Commercial; self-serve signup. Source
- Cloudflare — Monetization Gateway (pay per crawl): Verifies crawler identity and lets publishers charge AI agents via HTTP 402. Status: Announced July 1, 2026. Source
Checkout / agentic commerce platforms (4)
- Adyen — Agent Platform (ACP + UCP): Manages full ACP and UCP checkout flows for Adyen merchants. Status: Live. Source
- PayPal — Agent Ready (ACP): Lets merchants build a ChatGPT app that accepts payments via ACP. Status: Live guide; some payment methods listed "coming soon". Source
- Checkout.com — ACP support: Supports the Agentic Commerce Protocol for enterprise merchants. Status: Announced November 25, 2025. Source
- Stripe — Agentic commerce (ACP checkout): Lets AI agents transact with sellers on a buyer's behalf. Status: Seller integrations available; agent-side integration in private preview. Source
How to pick (five questions)
- What rail do you need? Cards (Visa, Mastercard, Stripe Issuing), stablecoins (x402, MPP, Coinbase, Circle) or both (Crossmint, Fireblocks).
- Who approves? If a person must sign off above a threshold, check that the product documents a human-approval step, not just a prompt instruction.
- Is the limit per agent? A per-account limit does not stop one runaway agent from using the whole budget.
- Where is the limit enforced? Server-side, before the payment executes. A limit written in the system prompt can be talked around by prompt injection.
- Can you test with fake money? Prefer products with a sandbox so you can try the rules before anything real moves.
Missing someone?
This is a point-in-time snapshot of a fast-moving market. If your company or protocol belongs on the map, or a row is wrong, leave a comment with a link to your own docs and it will be added or corrected.
Top comments (0)