How to accept payments from AI agents

Short answer: there are three practical paths, and they are not mutually exclusive. ACP (OpenAI + Stripe) lets you sell inside ChatGPT: existing Stripe merchants can enable agentic payments in about one line of code using the Shared Payment Token, while others can use Stripe’s Shared Payment Token API or the Delegated Payments Spec, with no change of processor and the merchant staying merchant of record. UCP (Google + Shopify) lets eligible retailers sell through agentic checkout 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 (Coinbase) accepts stablecoins natively over HTTP through a facilitator. Pick by surface: ACP to sell in ChatGPT, UCP for Google surfaces, AP2 for a network-aligned framework, x402 for crypto or pay-per-call APIs.

Path 1: ACP, sell inside ChatGPT

The Agentic Commerce Protocol powers Instant Checkout in ChatGPT. Orders flow from the agent to your backend over ACP; you accept or decline, charge the payment method, calculate and remit tax, and handle fulfillment and returns as usual. If you already process with Stripe, you can enable agentic payments by updating as little as one line of code; if not, you can still participate via Stripe’s Shared Payment Token API or by adopting the Delegated Payments Spec. Keep your product data current. See how Instant Checkout works 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. It powers agentic checkout on eligible Google product listings in AI Mode and the Gemini app, with Google Pay at launch and PayPal announced; 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 (USDC and other ERC-20 on Base, Polygon, Arbitrum, World, Solana). It suits pay-per-call APIs and machine-to-machine commerce. See the x402 standard page.

Compare all five standards →

Frequently asked questions

How does a merchant accept payments from AI agents?

By making checkout agent-ready: adopt ACP to sell inside ChatGPT (one line of code for existing Stripe merchants via the Shared Payment Token), UCP to sell on Google AI Mode and Gemini, and/or support AP2 or x402 depending on the surface and payment type.

Do I need to change my payment processor?

No. ACP keeps the merchant as merchant of record and works with existing processors. Stripe merchants can enable agentic payments by updating as little as one line of code; other processors can use Stripe’s Shared Payment Token API or the Delegated Payments Spec.

What do I need to sell through ChatGPT Instant Checkout?

Adopt the Agentic Commerce Protocol and keep your product data current (titles, descriptions, images, price, availability). See the OpenAI and Stripe docs linked below; the exact feed cadence should be confirmed against the official documentation.

How do AI agents pay with stablecoins?

Via x402: the server returns an HTTP 402 with payment requirements, the agent submits a signed payment, and a facilitator settles on-chain (e.g. USDC). AP2 also covers crypto through the A2A x402 extension.

Stay current on the standards

A note when a standard moves (ACP, UCP, AP2, MCP, x402). No spam.