← Back to Blog

How ACP Actually Works: The Payment Flow for WooCommerce Stores

Quick Answer: The Agentic Commerce Protocol (ACP) is an Apache 2.0 open standard co-maintained by OpenAI, Stripe, and Meta that defines how an AI agent runs checkout against a merchant. The agent indexes the merchant’s product feed, creates a checkout session, receives a scoped Shared Payment Token from Stripe, and the merchant charges it — the merchant stays merchant of record throughout, and the agent never sees raw card data. For WooCommerce store owners, the critical gap is tracking: an ACP purchase generates no GA4 session and no ad platform pixel event.

How does the Agentic Commerce Protocol process a purchase step by step?

The agent indexes the merchant’s product feed, the shopper selects a product in conversation, the agent creates a checkout session against the merchant’s ACP endpoints, a Shared Payment Token is issued by the payment provider, the merchant charges the token, and Stripe creates the order in WooCommerce. ACP was released under Apache 2.0 on September 29, 2025, co-developed by OpenAI and Stripe (Eco.com, 2025) — it’s the first open standard that codifies how an AI agent runs a purchase against a real merchant.

The flow is deliberately linear. The agent never bypasses the merchant’s checkout — it drives through it. Each step hands off a scoped piece of data to the next: the product feed tells the agent what’s available, the checkout endpoints tell it how to buy, the payment token tells Stripe how much to charge, and the webhooks tell the agent what happened. No step gives the agent more access than it needs.

For a WooCommerce store owner, the practical question is whether your store can serve each of these four steps. If you can’t generate a structured product feed, the agent can’t discover your products. If you don’t have ACP checkout endpoints, the agent can’t start a transaction. The protocol is a chain, and a missing link breaks it.

ACP was released under Apache 2.0 on September 29, 2025, co-developed by OpenAI and Stripe as the first open standard for agent-to-merchant checkout (Eco.com, 2025).

What is a Shared Payment Token in ACP?

A Shared Payment Token is a scoped, single-use payment credential issued by Stripe that works only for a specific merchant, only up to a set amount, and expires after a limited time — the AI agent never sees the buyer’s raw card data. Tokens are scoped by currency, maximum amount, and expiration (Cognativ / Stripe, 2026).

The scoping is what makes this safe. A token issued for Merchant A can’t be used at Merchant B. A token issued for $50 can’t be charged $51. A token issued with a 15-minute expiry can’t be used after 16 minutes. The agent passes the token to the merchant, the merchant passes it to Stripe, and Stripe verifies every constraint before authorising the charge.

This solves the trust problem that blocked agentic commerce for years. The buyer doesn’t hand their card to the agent. The agent doesn’t hand a card to the merchant. Stripe sits between them and issues a credential that works exactly once, for exactly one merchant, for exactly the right amount.

Related: Stripe’s Agentic Commerce Suite Went Live for WooCommerce on December 11

Does the merchant stay merchant of record with ACP?

Yes — the merchant remains the merchant of record throughout the entire ACP transaction, retaining control over products, pricing, transaction processing, and fulfillment. The agent is a facilitator, not an intermediary. It doesn’t hold inventory, set prices, or process payments — it coordinates the conversation and hands off to your existing checkout infrastructure.

This distinction matters for liability, tax, and customer relationships. Because the merchant is the seller, the merchant issues the receipt, the merchant handles the return, and the merchant owns the customer data from the order. The agent is a shopping assistant that brought the customer to your door — not a marketplace that sits between you and the buyer.

What product feed format does ACP require?

OpenAI’s product feed specification accepts JSONL, CSV, or TSV with core fields including item ID, title, description, URL, brand, seller name, image, availability, and price — merchants register at chatgpt.com/merchants to sync their products. The feed supports JSONL, CSV, or TSV formats (Cognativ, 2026).

For WooCommerce store owners, this means generating a structured export of your product catalogue in one of those formats and keeping it synced. The feed is what makes your products visible to the agent — without it, you don’t exist in the agent’s product universe. The fields map closely to WooCommerce’s standard product data, so the technical lift is a feed generator that runs on a schedule, not a manual export.

The feed is also the first place where data quality matters. If your product titles are vague, your descriptions are thin, or your availability is stale, the agent either can’t recommend you or recommends you inaccurately. The feed is your storefront for the agent channel.

What are the four moving parts of ACP?

ACP has four components: a structured product feed the agent indexes, agentic checkout endpoints the merchant hosts, delegated payment through scoped tokens, and order lifecycle webhooks that communicate status changes back to the agent. Each component handles one job, and together they form the full purchase cycle.

The product feed is discovery — it tells the agent what you sell. The checkout endpoints are the transaction — they accept the agent’s checkout request and return a payment session. The delegated payment is the money — a scoped token moves from buyer to Stripe to merchant. The webhooks are the confirmation loop — they tell the agent the order was created, shipped, delivered, or cancelled.

The merchant remains merchant of record throughout the entire ACP transaction, retaining control over products, pricing, transaction processing, and fulfillment (Stripe, 2025).
ComponentWhat It DoesWho Provides It
Product FeedMakes products discoverable to the agentMerchant (JSONL/CSV/TSV)
Checkout EndpointsAccepts agent checkout requestsMerchant (hosted API)
Delegated PaymentScoped token moves money securelyStripe / PayPal
Order WebhooksReports order status changes to agentMerchant → Agent

Related: UCP vs ACP: The Two Agentic Commerce Protocols, Compared

Can non-Stripe merchants use ACP?

Yes — ACP is an open standard and the Delegated Payment specification allows non-Stripe merchants to accept agentic payments, with PayPal now listed as a second compatible payment provider alongside Stripe. PayPal joined as a compatible PSP alongside Stripe (Eco.com, 2026), widening the merchant base that can participate.

The Delegated Payment specification is the layer that makes this possible. It abstracts the payment step so that any payment provider can implement the token-issuing flow. Stripe built the reference implementation and runs the managed checkout, but the protocol doesn’t require Stripe — it requires a provider that speaks the Delegated Payment spec.

For WooCommerce merchants already on PayPal, this is significant. You don’t need to migrate to Stripe to sell through ACP. You need a payment provider that implements the token specification, and PayPal is now on that list.

What commerce types does ACP support?

ACP supports flexible configurations for physical goods, digital goods, subscriptions, and asynchronous purchases — it’s not limited to simple one-time product transactions. ACP supports physical goods, digital goods, subscriptions, and asynchronous purchases (Stripe, 2025).

This matters because WooCommerce stores don’t just sell widgets. They sell subscriptions through WooCommerce Subscriptions, digital downloads through Easy Digital Downloads, and bookings through WooCommerce Bookings. If ACP could only handle simple product purchases, it would exclude a large share of the WooCommerce ecosystem. The protocol was designed from the start to handle the range of commerce patterns merchants already use.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

Where is ACP available geographically?

Stripe-managed checkout through ACP is available in the US, Canada, and select European countries — geographic availability follows Stripe’s standard payment processing coverage. Available in US, Canada, and select European countries (Cognativ, 2026).

If you’re a WooCommerce store owner outside those regions, you can’t use Stripe-managed ACP checkout yet. The protocol itself is open and geographic-neutral, but the managed checkout — the turnkey version that handles token issuance and payment processing for you — requires Stripe’s infrastructure. As PayPal and other providers build their implementations, geographic coverage will expand to match their own processing footprints.

Related: What is the Universal Commerce Protocol for WooCommerce?

How does ACP differ from UCP?

ACP was built by OpenAI and Stripe for agent-to-merchant checkout inside ChatGPT, while UCP was built by Google and Shopify to cover the full commerce journey from discovery to post-purchase — ACP optimises for buying, UCP optimises for shopping. OpenAI, Stripe, and Meta are lead maintainers of ACP; Google and Shopify lead UCP (Eco.com, 2026).

The practical difference: ACP picks up once the agent already knows what the buyer wants. It’s a checkout protocol — here’s the product, here’s the payment, here’s the confirmation. UCP starts earlier. It covers product discovery, comparison, identity linking, and post-purchase support as well as checkout.

For WooCommerce store owners, the question isn’t which is better — it’s which agents your buyers use. If your customers shop through ChatGPT, you need ACP. If they shop through Google or Copilot, you need UCP. If they use both, you need both. The protocols serve different ecosystems, and the ecosystems aren’t merging.

What tracking data does an ACP purchase generate in WooCommerce?

The order exists in WooCommerce admin and in Stripe’s dashboard, but no GA4 session, no Meta Pixel event, and no Google Ads gclid is generated — server-side tracking at the order hook is the only method that captures the conversion. There’s no browser, no cookie, and no client-side JavaScript executing during an ACP transaction.

Let that sink in. The purchase happens, the money lands, the order appears in your dashboard — and your ad platforms see nothing. GA4 doesn’t record a session. Your conversion pixel doesn’t fire. Your ROAS calculation is missing revenue that actually came in through your checkout.

Server-side tracking with tools like Transmute Engine captures the Stripe webhook events that fire when an ACP transaction completes, routing the conversion signal to GA4 and ad platforms that never saw the browser-less purchase. Without it, every ACP order is a hole in your attribution data — revenue you earned but can’t report.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • ACP is a six-step chain: product feed → checkout session → Shared Payment Token → merchant charges → order created → webhooks confirm.
  • The agent never sees card data: Shared Payment Tokens are scoped, single-use, and expire — the buyer’s payment details stay with Stripe.
  • The merchant stays merchant of record: you control products, pricing, fulfillment, and customer data throughout.
  • ACP and UCP serve different ecosystems: ACP for ChatGPT, UCP for Google and Copilot — many stores will need both.
  • ACP purchases are invisible to client-side tracking: no GA4 session, no pixel, no gclid — server-side tracking is the only path to attribution.
How does the Agentic Commerce Protocol process a purchase step by step?

The agent indexes the merchant’s product feed, the shopper selects a product in conversation, the agent creates a checkout session against the merchant’s ACP endpoints, a Shared Payment Token is issued by Stripe, the merchant charges the token, and Stripe creates the order in WooCommerce. The merchant stays merchant of record throughout.

What is a Shared Payment Token in ACP?

A Shared Payment Token is a scoped, single-use payment credential issued by Stripe that works only for a specific merchant, only up to a set amount, and expires after a limited time. The AI agent never sees the buyer’s raw card data — the token is the only payment artifact it handles.

Does the merchant stay merchant of record with ACP?

Yes. The merchant remains the merchant of record throughout the entire ACP transaction, retaining control over products, pricing, transaction processing, and fulfillment. The agent facilitates the transaction but never owns it.

What product feed format does ACP require?

OpenAI’s product feed specification accepts JSONL, CSV, or TSV with core fields including item ID, title, description, URL, brand, seller name, image, availability, and price. Merchants register at chatgpt.com/merchants to sync their product catalogues.

What are the four moving parts of ACP?

ACP has four components: a structured product feed the agent indexes, agentic checkout endpoints the merchant hosts, delegated payment through scoped tokens, and order lifecycle webhooks that communicate status changes back to the agent.

Can non-Stripe merchants use ACP?

Yes. ACP is an open standard and the Delegated Payment specification allows non-Stripe merchants to accept agentic payments. PayPal is now listed as a second compatible payment provider alongside Stripe, so merchants using either processor can participate.

What commerce types does ACP support?

ACP supports flexible configurations for physical goods, digital goods, subscriptions, and asynchronous purchases. It is not limited to simple one-time product transactions — the protocol was designed to handle the range of commerce patterns merchants already use.

Where is ACP available geographically?

Stripe-managed checkout through ACP is available in the US, Canada, and select European countries. Geographic availability follows Stripe’s standard payment processing coverage, so merchants outside those regions cannot use Stripe-managed ACP checkout yet.

How does ACP differ from UCP?

ACP was built by OpenAI and Stripe for agent-to-merchant checkout inside ChatGPT, while UCP was built by Google and Shopify to cover the full commerce journey from discovery to post-purchase. ACP optimises for buying, UCP optimises for shopping. OpenAI, Stripe and Meta maintain ACP; Google and Shopify lead UCP.

What tracking data does an ACP purchase generate in WooCommerce?

The order exists in WooCommerce admin and in Stripe’s dashboard, but no GA4 session, no Meta Pixel event, and no Google Ads gclid is generated. Server-side tracking at the WooCommerce order hook is the only method that captures the conversion for ad platforms.

References

  1. Eco.com (2025). ACP — Agentic Commerce Protocol Explained. Source
  2. Stripe (2025). Developing an Open Standard for Agentic Commerce. Source
  3. Cognativ (2026). Agentic Commerce Protocol Guide. Source
  4. Stripe Newsroom (2025). Stripe and OpenAI Instant Checkout. Source
  5. Seresa (2026). Stripe’s Agentic Commerce Suite Went Live for WooCommerce. Source