What Is Agentic Payments?
Agentic payments are financial transactions that an autonomous AI agent initiates, authorizes, and executes on behalf of a user or business, within limits the user has pre-set, rather than a human approving each individual step.
This distinguishes agentic payments from ordinary automation like autopay or scheduled bill payments, which move money on a fixed schedule for a fixed amount. An agentic payment involves the agent deciding whether, when, and how much to pay based on a broader goal ("book me the cheapest flight under $400 next Tuesday"), not a static rule.
Key facts
- No single inventor or governing body. "Agentic payments" is an industry-wide category name, not one company's product. Several large technology and payments companies have each published their own open protocol: Google's Agent Payments Protocol (AP2) (announced September 16, 2025), Coinbase's x402 (whitepaper published May 6, 2025), and OpenAI/Stripe's Agentic Commerce Protocol (ACP) (announced September 29, 2025).
- Two payment rails are being used in parallel. Card-network-style implementations extend existing tokenization and add cryptographic "mandates" proving a human authorized the agent (AP2's Intent/Cart Mandates, per the Google Cloud announcement). Stablecoin-based implementations settle directly on a blockchain over HTTP, with no card network in the loop (x402's facilitator model, per the x402 whitepaper).
- Governance is consolidating into open-source foundations. x402 moved from a Coinbase-led project to the Linux Foundation-governed x402 Foundation, which had its operational launch on July 14, 2026 with premier members including Google, Stripe, Visa, Mastercard, AWS, and Coinbase, per the Linux Foundation's press release. AP2 was donated by Google to the FIDO Alliance on April 28, 2026, per Google's blog post.
- The core unsolved problem is authorization, not payment rails. Every protocol in this space is primarily solving the same question — how does a merchant or bank know an AI agent's transaction genuinely reflects what the user wanted, and who is liable if it doesn't — using cryptographically signed "mandates," tokens, or credentials rather than a human clicking "confirm."
How it works
- A human sets a goal and constraints for an agent (e.g., a spending cap, category, or specific task) — this step is what protocols like AP2 call an Intent Mandate.
- The agent searches, negotiates, or selects an option (a flight, an API call, a product) autonomously, without further human input at this stage.
- The agent's choice is recorded as a verifiable, tamper-evident artifact — a signed "Cart Mandate," a signed payment payload, or a token — that a merchant or payment processor can check.
- The payment is authorized and settled, either through a traditional processor (card rails, via ACP or AP2) or directly on-chain via a stablecoin transfer (via x402).
- A record of the mandate/signature is kept so that, in a dispute, it's possible to determine whether the agent acted within its authorized bounds.
Comparison of major agentic payment protocols
| x402 | AP2 | ACP | |
|---|---|---|---|
| Initiated by | Coinbase Developer Platform (May 6, 2025) | Google (Sept 16, 2025) | OpenAI + Stripe (Sept 29, 2025) |
| Primary rail | Stablecoins on-chain (Base, Solana) | Card, bank transfer, stablecoin (rail-agnostic) | Card rails via existing payment processors |
| Stablecoin support | Yes — native | Yes — via x402 extension | Not specified in primary sources reviewed |
| Card support | Not specified in primary sources reviewed | Yes | Yes |
| Authorization model | Signed payment header verified by a "facilitator"; settlement fails signature checks if tampered | Cryptographically signed Intent Mandate + Cart Mandate (verifiable credentials) | Checkout flow with capability negotiation and payment-handler tokenization |
| Open-source license | Apache-2.0 | Apache-2.0 | Apache-2.0 |
| Current governance | x402 Foundation (Linux Foundation) | Donated to FIDO Alliance | Jointly governed by OpenAI and Stripe as Founding Maintainers |
FAQ
Is agentic payments the same as autopay? No. Autopay executes a fixed, pre-approved amount on a schedule. Agentic payments let an AI agent decide whether, when, and how much to pay based on a goal, within limits a human set in advance.
Who invented agentic payments? No single company. It's an industry category; Google (AP2), Coinbase (x402), and OpenAI/Stripe (ACP) each published competing/complementary open protocols in 2025.
Do agentic payments require cryptocurrency? No. AP2 and ACP are built to work over existing card and bank rails. x402 is stablecoin-native. Some products, like Coinbase's Agentic Wallets, combine both.
What stops an AI agent from overspending? Protocols rely on pre-set spending limits ("mandates," session caps, or per-transaction limits) that are cryptographically signed and checked before a payment settles, rather than trusting the agent's judgment alone.
Are these protocols compatible with each other? Partially. AP2 is designed as an extension of the A2A protocol and supports MCP, and Google has co-developed an x402 extension for AP2 with Coinbase, Ethereum Foundation, and MetaMask, per the Google Cloud announcement. ACP interoperability with AP2/x402 is not specified in the primary sources reviewed.
