AI Atlas
Intermediate · ~2 min read #agentic-commerce #ap2 #x402

Agent Payments

Agentic payments: an AI agent spending money on a user's behalf

The umbrella term for protocols and mechanisms that aim to make purchases and payments an AI agent makes on a user's behalf safe, verifiable and recognizable to merchants.

AGENT PAYMENTS · FOUR QUESTIONS, SEPARATE PROTOCOLSUSERsigns the limitsAGENTbuys on their behalfMERCHANTmerchant of recordCart & checkout: which language?ACPOpenAI + StripeUCPGoogle + partnersDid the user really approve?AP2mandate: Open → ClosedACPallowance: amount · timeHow does the money move?x402HTTP 402 · per requestcard networkPSP · tokenWho is this agent?Visa TAPRFC 9421 signatureAgent PayMastercardThe agent never carries the card itself: limits are set in advance, provably
Definition

Payment systems were built on the assumption that a human presses the pay button. When an agent shops for a user, that assumption breaks and three new questions appear: in what language do the agent and the merchant talk about the cart and checkout? How do you prove the user really approved this spend? How does the merchant know the incoming agent is not a malicious bot?

In 2025-2026 several open protocols appeared that answer different combinations of these questions (status as of November 2026):

  • AP2 (Agent Payments Protocol): Started by Google, handed to the FIDO Alliance in April 2026; latest release v0.2.0. It turns user approval into signed mandates: a Checkout Mandate and a Payment Mandate, each with an "Open" stage carrying constraints and a "Closed" stage carrying the finalized transaction.
  • x402: Born at Coinbase, housed since April 2026 in the x402 Foundation under the Linux Foundation; protocol version 2. It uses HTTP's 402 Payment Required code to put per-request payment inside the HTTP request.
  • ACP (Agentic Commerce Protocol): A checkout and delegated payment protocol maintained by OpenAI and Stripe, in beta; latest version 2026-04-17.
  • UCP (Universal Commerce Protocol): A commerce protocol Google announced in January 2026 together with Shopify, Etsy, Wayfair, Target and Walmart; it covers discovery, checkout, identity linking and orders, and can use AP2 as an extension for payment authorization.
  • Visa Trusted Agent Protocol: Solves the agent's identity, not the payment: the agent signs every HTTP request with RFC 9421 HTTP Message Signatures, and the merchant verifies it as a registered agent.

The shared idea: the agent should not carry "the card itself"; the limits of the spend (amount, time window, merchant) should be set in advance and provably, and every transaction should leave a trail that can be audited later.

Analogy

The difference between handing an assistant your credit card, and handing them a signed note saying "buy this item, from this store, for at most this amount, this week" plus a single-use prepaid card.

In the first case the assistant can do anything, and proving what happened later is hard. In the second, the store sees the note and knows the assistant really comes from you, the card will not work above the limit, and the signed note shows who approved what in a dispute. Agent payment protocols try to build the second arrangement digitally.

Real-world example

A user tells their assistant "buy two concert tickets the moment they go on sale, total under $150" and goes to sleep. With AP2, the user signs Open mandates carrying these constraints in advance. When the sale opens, the agent fills in the ticket seller's checkout (e.g. over UCP); if the cart is under $150, Closed Checkout and Payment Mandates are created and go to the payment network. If the price exceeds the limit, the agent cannot complete the purchase.

When the same agent calls a paid API to fetch the seat map, the server returns 402; the agent signs a payment of a few cents with x402 and retries.

Code examples
x402 v2 · a 402 response and a paid retry http
# 1) First request
GET /premium-data HTTP/1.1
Host: api.example.com

# 2) The server returns its payment requirements
HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: <base64(PaymentRequired)>

# PaymentRequired (decoded, abbreviated):
# { "x402Version": 2,
#   "accepts": [{ "scheme": "exact", "network": "eip155:84532",
#                 "amount": "10000", "payTo": "0x2096…", "maxTimeoutSeconds": 60 }] }

# 3) The client retries with a signed payment payload
GET /premium-data HTTP/1.1
Host: api.example.com
PAYMENT-SIGNATURE: <base64(PaymentPayload)>

# 4) The server verifies and settles the payment via the
#    facilitator's /verify and /settle endpoints, then returns 200
ACP Delegated Payment · allowance (2026-04-17) json
{
  "allowance": {
    "reason": "one_time",
    "max_amount": 15000,
    "currency": "usd",
    "checkout_session_id": "csn_01HV3P3XYZ789",
    "merchant_id": "ticket_store",
    "expires_at": "2026-11-15T21:00:00Z"
  }
}
// max_amount is in minor units (15000 cents = $150).
// The token is valid only for this merchant, this checkout session and this window.
When to use
  • Flows where the agent really spends money on the user's behalf (travel, tickets, subscriptions, procurement)
  • You want to sell on AI surfaces such as ChatGPT or Google AI Mode / Gemini (ACP, UCP)
  • You want to charge per request for your API or content without accounts (x402)
  • You need to tell shopping agents apart from malicious bots on your site (Visa TAP, Web Bot Auth)
When not to use
  • The agent only researches products and shows links — payment stays with the human
  • A classic e-commerce checkout is enough for humans and you have no agent traffic
  • You want to turn on autonomous payments without limits, logging and reversal in place — build those first
Common pitfalls

Handing the agent the card itself

Putting a raw card number or an unlimited API key into the agent's context makes it leakable via prompt injection. Limited, single-use tokens (ACP allowance) or signed mandates (AP2) exist for exactly this.

Leaving the budget to the protocol

The x402 spec explicitly leaves client-side budget management out of scope. Without a spending cap, an allowed-domain list and logging, an agent stuck in a loop can drain the wallet.

Assuming old mandate names are current

AP2 v0.1 and the September 2025 announcement used Intent, Cart and Payment Mandate; the v0.2 docs define Checkout and Payment Mandates with Open/Closed stages. Check which version an article describes.

Mixing up the two ACPs

The Agentic Commerce Protocol (OpenAI + Stripe) and IBM's Agent Communication Protocol, which merged into A2A in August 2025, share an acronym. In a commerce context, ACP almost always means the first.

Mistaking authentication for consent

A Visa TAP signature shows the agent is registered and tied to a user; on its own it does not prove the user approved this particular cart. Consent needs a mandate or an explicit user step in the checkout flow.