Join early accessPlain-language definitions and evidence-based guides to the protocols, wallets, and controls behind AI agents that can pay — x402, AP2, ACP, Visa TAP, Mastercard Agent Pay, MCP payments, and more.
Definitions of the core terms in agentic payments.
Glossary
Agentic payments let AI agents initiate and execute transactions on a human's behalf. Definitions, protocols (x402, AP2, ACP), and open questions.
Glossary
x402 is Coinbase's open protocol that uses the HTTP 402 status code to let servers charge AI agents and apps in stablecoins. Origins, mechanics, governance.
Glossary
AP2 is Google's open protocol for AI agents to make purchases using signed 'mandates.' Origins, mechanism, governance, and how it differs from x402/ACP.
Glossary
ACP is OpenAI and Stripe's open standard letting AI agents complete purchases inside a chat interface. Origins, checkout flow, license, and comparisons.
Glossary
An AI agent wallet is a crypto or payment wallet built for autonomous AI agents rather than humans, with spend limits and delegated signing. Examples inside.
Glossary
AI agent spending controls are the rules — caps, allowlists, approval thresholds, velocity limits — that bound what an autonomous agent can pay for. How AP2, card networks, and wallets each implement them.
Glossary
Know Your Agent (KYA) verifies which human or organization an AI agent represents before letting it transact. How Skyfire's KYA works and how it relates to KYC.
Glossary
Mastercard Agent Pay lets AI agents transact using Agentic Tokens — permissioned, tokenized payment credentials. Announcement, mechanism, and named partners.
Glossary
Visa Trusted Agent Protocol lets merchants cryptographically verify legitimate AI shopping agents instead of treating them as bots. Mechanism, partners, and specs.
Glossary
MCP payments let an AI agent call payment tools (create an invoice, charge a card, issue a refund) through the Model Context Protocol. Official servers, risks, and safeguards.
Longer, comparative pieces for developers and technical decision-makers.
Guide
16 payment companies checked for an official MCP server that moves money, plus what auth and spending controls each one actually documents.
Guide
Stripe MCP stops accepting full-access secret keys and non-Agent restricted keys on Oct 31, 2026. Here's who's affected, how to migrate, and how to scope agent spend.
Guide
x402, AP2 and ACP solve different layers of AI agent payments: pay-per-request stablecoin settlement, proof of user authorization, and in-chat checkout. Side-by-side comparison, adoption data for 13 providers, and when to use which.
Guide
A layer-by-layer market map of agentic AI payments in 2026 — protocols, card-network programs, agent wallets, payment MCP servers, and spend-control/policy tools — with 33 companies, primary sources, and status for each.
Guide
A copy-paste policy template and 9 controls (budgets, allowlists, approval thresholds, credential scoping) for letting AI agents spendunder finance oversight.
Guide
There is no single best payment API for AI agents — the right pick depends on what the agent needs to do. A use-case-by-use-case guide to card checkout, stablecoin micropayments, agent wallets, MCP-based account access, and identity, sourced to each provider's own documentation.
Guide
Five documented ways to let an AI agent pay for per-call or metered API usage without handing it an open-ended credential: x402 pay-per-request, provider spend limits, single-use virtual cards, an MCP policy layer, and human approval — compared, with a setup checklist.
Guide
Guide
AI agents pay through MCP by calling a payment tool that budget and approval rules check first. Pink Agentic AI Payments adds that policy layer over any MCP payment server.
Guide
A dated, source-linked timeline of protocol launches, official payment MCP servers, card-network agent programs and governance changes in AI agent payments.
Guide
x402 (Coinbase, now the x402 Foundation) and MPP (Stripe and Tempo) both turn HTTP 402 into a machine payment layer. Side-by-side comparison of settlement rails, SDKs, spend controls and governance, sourced from each protocol's own docs.
Guide
An operational runbook for developers and finance/IT teams: what to do in the first 15 minutes after an AI agent misuses a payment credential, how to investigate, what you can recover, and how to prevent a repeat.
Guide
Four confusions developers keep hitting when implementing AP2 (Agent Payments Protocol) mandate and budget-constraint semantics — budget.max unit mismatches, a false-negative violations list, mandate replay, and a skippable checkout-binding check — documented against the AP2 reference implementation and filed as public GitHub issues.
Guide
A sourced, use-case-by-use-case comparison of virtual/programmable card providers that let an AI agent spend within limits — Privacy.com, Ramp, Brex, Stripe Issuing, Lithic, Marqeta, Crossmint, and AgentCard — with controls, signup path, and MCP/API access for each, sourced to each provider's own docs.
Guide
A sourced comparison of 11 providers, including Pink Agentic AI Payments, that document spending governance for AI agents — Payman, Skyfire, Coinbase CDP, Circle, Crossmint, Lithic, Stripe Issuing, AgentCard, Tempo, Openfort, and Nevermined — by control layer (card network, wallet/onchain, API policy, MCP), with the exact caps, approvals, and audit features each vendor documents.
Guide
The exact field or flag each provider documents for capping what an AI agent can spend — Stripe, Privacy.com, Lithic, AgentCard, Crossmint, Coinbase CDP, Circle, Tempo, Payman, Skyfire, AP2, and x402 — with its unit, its period options, and where it's actually enforced.
Guide
A sourced map of who actually governs each AI-agent payment spec in 2026 — x402, AP2, ACP, MPP, UCP, MCP, Visa's Trusted Agent Protocol and Mastercard Agent Pay — with the steward, licence, status and the last governance change for each.
Guide
A five-step, vendor-neutral setup guide for finance, IT, and procurement leads who want an AI agent to pay vendors automatically — which rail to use per vendor type, how to write the spending policy, how to wire approvals, how to audit, and how to plan for incidents. Every control cited is sourced to the provider's own docs.
Guide
A sourced shortlist of 8 providers that document stablecoin support for machine-to-machine or AI agent payments — Coinbase, Circle, Stripe, Skyfire, Crossmint, Nevermined, Openfort, and Tempo — compared by stablecoin/chain, M2M mechanism, key custody, per-agent spending controls, and availability, each claim linked to the vendor's own docs.
Guide
A use-case-led, sourced comparison of 10 payment providers — Stripe Issuing, Lithic, Privacy.com, AgentCard, Crossmint, Coinbase CDP, Circle, Payman, Skyfire, and Openfort — for companies letting an AI agent buy SaaS, API usage, and larger purchases on their behalf. Every control is sourced to the provider's own docs.
Guide
Ramp Agent Cards issue real single-use corporate cards to AI agents. Pink enforces spending rules before a credential exists. Sourced comparison.
Guide
Brex's MCP server gives agents read and expense-tracking access today, not payment execution. Pink checks rules before issuing a credential. Sourced.
Guide
Coupa's Navi Connect MCP exposes 30+ procurement tools to AI agents, inheriting the signed-in user's permissions. Pink checks rules first. Sourced.
Guide
Stripe's Agent Toolkit and MCP server use a human-confirmation gate on sensitive writes. Pink checks rules before a credential exists. Sourced.
Guide
AWS AgentCore Payments moves stablecoin micropayments at machine speed, GA since Aug 2026. Pink adds a human-approval rule layer. Sourced comparison.
Guide
Marqeta's MCP server issues virtual cards with velocity and spend controls, in beta. Pink checks rules before any credential exists. Sourced.
Guide
A direct, step-by-step setup: connect an AI agent to Pink over MCP or REST, set per-agent budgets and payee rules, and see real sandbox outputs for allowed, pending-human, and blocked payments.
Guide
How Pink's server-side policy engine evaluates every AI agent payment, circuit breakers, amount tiers, payee rules, fraud signals and time windows, with a real dry-run trace and live sandbox outputs.
Guide
How Pink's MCP server lets an AI agent in Claude, ChatGPT or another MCP client check and pay an invoice within budgets, caps and approval rules, with the 7 MCP tools and real connection steps.
Guide
How to give an AI agent its own agent key, vault and budget in Pink: real field names, a worked procurement-agent config, and concurrent-load tests including a shared ceiling across multiple agents.
Guide
The 6 recurring risks in agent-initiated payments (budget runaway, payee drift, prompt injection, missing audit trail, no human in the loop, over-scoped credentials) mapped to Pink's server-side controls, with concurrent-load test results and an honest list of what isn't covered yet.
How companies in different industries use Pink Agentic AI Payments — see the full Use cases hub.
Use case
How a company lets a travel-booking agent pay for flights and hotels inside per-trip caps, currency rules and manager approval above a threshold.
Use case
How an e-commerce company lets ads, creator, procurement and returns agents pay against revenue, signed briefs and POs, with tiered refunds and carrier statement checks.
Use case
How a logistics or freight company lets agents pay carrier invoices, fuel and toll spend and multi-currency payees, with statement matching and after-hours human checks.
Use case
How a manufacturer lets purchasing agents pay suppliers against a PO and warehouse scan, from an allowlist, with fraud checks and 2-of-3 approval above a threshold.
Use case
How an agency lets ad-buying and payout agents spend per client inside separate vaults and monthly caps, with the client's approver in the loop.
Use case
How a multi-store retailer gives each store its own agent, vault and budget, with warehouse-scan checks on reorders and regional manager sign-off above a threshold.
Use case
How a law, accounting, or consulting firm lets agents pay SaaS bills, research purchases and contractors, with duplicate-invoice checks and partner sign-off.
Use case
How a property manager lets a maintenance agent pay allowlisted vendors, catches bank-detail-change fraud, and keeps a reserve vault agents can't touch.
Use case
How a coffee shop or restaurant lets purchasing, marketing and payroll agents pay suppliers and bills inside rules a human set, with approvals for anything unusual.
Use case
How a SaaS startup lets engineering, ops and recruiting agents pay for cloud spend, subscriptions and contractors, with a $200/day rule that stopped a $49,600 bug.
Contact Email: [email protected]
ALTIVOX SPHERE SPÓŁKA ZO.O. is a wholly owned subsidiary of PinkWallet, registered in Poland in the Polish Ministry of Finance's virtual-currency activity register (registration number: RDWW-1797), authorized to provide cryptocurrency exchange and digital asset custody services in the EU under AML/CTF regulations.
PinkWallet (Pink Technologies Inc) is registered as a Money Services Business with the U.S. Department of the Treasury, FinCEN (Registration No. 31000321450011), enabling it to provide users with cross-border fund settlement and international payment services under the U.S. regulatory framework.
PinkWallet (Pink Wallet Technology Inc.) is registered as a Money Services Business with FINTRAC, Canada's financial intelligence unit (Registration No. C100001073), enabling it to provide users with cross-border fund settlement and virtual currency services under the Canadian regulatory framework.
