An ACP integration has three parts: a product feed that tells ChatGPT what you sell, a checkout API that the agent calls to build and complete an order on your system, and a delegated payment token that lets you charge the shopper without ever seeing their card. The Agentic Commerce Protocol is an open Apache 2.0 spec, still labelled beta, with OpenAI and Stripe as founding maintainers. This guide walks through each part using the published specs as of November 2026. It is not a substitute for the spec itself, and we have not built a production integration.
- Latest stable ACP spec version
- 2026-04-17
- Checkout-session endpoints you implement
- 5
- Payment providers in OpenAI's spec (Stripe, Adyen, Braintree)
- 3
- Spec status (Apache 2.0)
- Beta
What changed in 2026, and is ACP still worth it?
ACP launched on 29 September 2025 alongside ChatGPT Instant Checkout. In March 2026 OpenAI scaled back in-chat Instant Checkout and moved ChatGPT shopping towards discovery, as Retail Gazette and others reported. Sources disagree on the exact date (4, 17 or 24 March). ACP itself did not stop. It still powers merchant integrations such as Instacart, Target, DoorDash and Expedia, and the spec kept moving.
- ACP initial release with ChatGPT Instant Checkout
- PayPal adopts ACP for ChatGPT
- Spec update: fulfilment enhancements
- Spec update: extensions, discounts, payment handlers
- OpenAI scales back in-chat Instant Checkout
- Latest stable spec: cart, feed, orders, authentication, MCP
For most merchants the practical takeaway is that the feed matters now, while full checkout is worth building if you sell in categories where ChatGPT merchant apps are active or you expect other ACP-speaking agents. Shoppers' view of this is in our ACP explainer.
Part 1: The product feed
Everything starts with the feed. OpenAI's feed spec requires nine fields on every product: item_id, title, description, url, brand, seller_name, image_url, availability and price. The examples use JSONL, and CSV and TSV are also supported. Delivery is by file upload to an SFTP server, and OpenAI's docs also list a Feeds API with products and promotions endpoints.
Two flags control what ACP can do with a product:
is_eligible_search(aliasenable_search) defaults to true. Setting it to false also turns off checkout.is_eligible_checkout(aliasenable_checkout) defaults to false. Setting it to true only works when search is also on and checkout is enabled for your integration. The spec says the flag "doesn't complete checkout onboarding".
So you can be discoverable in ChatGPT without offering agent checkout at all. The details, including optional variant, shipping and returns fields, are in product feeds for AI agents.
Part 2: The Agentic Checkout API
Under ACP the agent does not scrape your checkout page. It calls endpoints you host. OpenAI's checkout spec defines five:
| Endpoint | Method | What it does |
|---|---|---|
/checkout_sessions |
POST | Create a session with the requested items |
/checkout_sessions/{checkout_session_id} |
POST | Update items, address or fulfilment option |
/checkout_sessions/{checkout_session_id} |
GET | Return current session state |
/checkout_sessions/{checkout_session_id}/complete |
POST | Finalise and create the order |
/checkout_sessions/{checkout_session_id}/cancel |
POST | Cancel if not already completed |
Each request from OpenAI carries an Authorization bearer key, an Idempotency-Key, a Signature (Base64 signature of the body), a Timestamp in RFC 3339 format, and Request-Id and API-Version headers. Your system returns line items, totals, taxes, shipping options and any messages the shopper must see. You stay in control of prices and stock, because the session is computed on your side.
- Shopper approves in agent
- Agent calls /checkout_sessions
- Your pricing and stock
- /complete with payment token
- Order webhook back
Order webhooks
After an order exists, you send events back so the agent can show status. The spec's webhook table lists order_created and order_updated, with data including checkout_session_id, permalink_url, status and refunds. The same page's overview writes them as order.created and order.updated, so confirm the exact names with OpenAI before you go live. Webhooks are signed with an HMAC key OpenAI provides.
Handle idempotency and retries
Agents retry. Store the Idempotency-Key with each mutating request and return the original response for duplicates, or you risk creating two orders for one approval. This is ordinary payments hygiene, but it matters more when no human is watching the button.
Part 3: Delegated payments
At /complete, the agent sends a payment_data object containing a token and a provider. OpenAI's spec allows stripe, adyen and braintree. The example token is spt_123, a Stripe Shared Payment Token.
Stripe's shared payment token docs describe an SPT as "a scoped grant to use the customer's payment method", limited by currency, maximum amount and expiry. The agent sets the maximum to match the order total and can revoke the token. On Stripe you create a PaymentIntent with payment_method_data[shared_payment_granted_token], and refunds then work as with any other payment.
Key points from Stripe's docs as of November 2026:
- SPTs are available in the US, Canada and about 30 European countries, including the UK.
- If you use another processor, Stripe's resolve API returns network credentials once. A second resolve fails.
- Behind the token, Stripe may use network tokens from Mastercard Agent Pay, Visa Intelligent Commerce or American Express ACE.
- A
shared_payment.granted_token.deactivatedwebhook tells you when a token is consumed, expired or revoked.
The spec repository separates this into the Delegate Payment spec, which payment service providers implement. Most merchants never touch it directly; they use a provider that already supports it.
The PayPal shortcut
PayPal adopted ACP for ChatGPT on 28 October 2025. According to PayPal's announcement, merchant catalogs can reach ChatGPT through PayPal's ACP server, and PayPal buyer protection applies. If you already sell through PayPal, ask your account team before writing endpoints yourself. Shoppers' side: PayPal and AI agents.
How should you roll it out?
- Ship the feedRequired fields, search on, checkout off.
- Read the spec versionPin to 2026-04-17 and send API-Version.
- Build sessions in a sandboxCreate, update, retrieve, complete, cancel.
- Wire paymentsAccept SPTs via Stripe, or Adyen or Braintree tokens.
- Send order webhooksConfirm event names, sign with the HMAC key.
- Use the production checklistOpenAI's docs include one before launch.
Pros and cons for merchants
Pros
- You keep pricing, stock and the customer record as merchant of record
- Open spec with versioned releases and multiple payment providers
- Feed alone gets you into ChatGPT discovery
Cons
- Spec is still beta and was updated four times in its first seven months
- In-chat Instant Checkout was scaled back in March 2026
- Onboarding for checkout is separate from flipping the feed flag
Bottom line
Treat ACP as two projects. The feed is cheap, useful immediately and shared with other channels. The checkout API and delegated payments are a real engineering effort that pays off mainly if your category has active ChatGPT merchant integrations or you expect more ACP-speaking agents. If you are on Shopify or PayPal, check what they already do for you first, and compare the alternatives in ACP vs AP2 vs UCP and UCP and AP2 for merchants. For the overall checklist, see making your store agent-ready.


