How to accept payments from AI agents
Short answer: there are four practical paths, and they are not mutually exclusive. ACP (OpenAI + Stripe) currently carries product discovery in ChatGPT: merchants publish eligible product feeds and promotions, then keep checkout on their own site or use a ChatGPT app. UCP (Google + Shopify) was announced for an agentic checkout rollout on Google AI Mode and the Gemini app, with the retailer remaining seller of record. AP2 (Google) is a payment-agnostic framework for authorizing agent-led payments across cards, stablecoins and bank transfers. x402 accepts stablecoins natively over HTTP through a facilitator. Pick by surface and documented capability, then confirm the live integration terms before building.
Path 1: ACP, product discovery in ChatGPT
The Agentic Commerce Protocol powered the original Instant Checkout flow in ChatGPT. On 24 March 2026 OpenAI announced a focus on product discovery and merchant checkout. OpenAI now documents ACP for product discovery: merchants share product feeds and promotions so that ChatGPT can represent their catalogue. The shopper then completes checkout on the merchant side or inside a ChatGPT app. Keep titles, descriptions, images, price and availability current, because these are the public inputs on which discovery depends. See what happened to Instant Checkout and the ACP standard page.
Path 2: UCP, sell on Google AI Mode and Gemini
The Universal Commerce Protocol, launched by Google on 11 January 2026 and co-developed with Shopify, Etsy, Wayfair, Target and Walmart, standardizes the full shopping journey: discovery, checkout and post-purchase support. Google announced that it would soon power checkout on eligible product listings in AI Mode and the Gemini app, with Google Pay for the initial rollout and PayPal as a future option; the retailer remains the seller of record. Capabilities are served over REST APIs, MCP or A2A. See the UCP standard page.
Path 3: AP2, authorize agent-led payments
Google’s Agent Payments Protocol is payment-agnostic and designed as an extension of the A2A protocol and MCP, developed with 60+ organizations including Mastercard, PayPal and American Express. It captures user intent through verifiable credentials (mandates) and spans cards, stablecoins and real-time bank transfers. See the AP2 standard page.
Path 4: x402, native stablecoin payments
x402 revives the HTTP 402 status code: your server responds with payment requirements, the agent submits a signed payment, and a facilitator settles on-chain. The exact scheme uses EIP-712 and EIP-3009 on EVM networks and TransferChecked on Solana. It suits pay-per-call APIs and machine-to-machine commerce. See the x402 standard page.
Accepting payment is only half the loop. Before an agent can buy, it has to discover and correctly read your products — a separate, machine-readable problem the payment standards do not solve. See how AI agents find and read your products to make your catalogue agent-ready.