What Stripe’s Agentic Commerce Suite Actually Is#

A single integration that connects your product catalog to every AI agent that implements the Agentic Commerce Protocol.

McKinsey projects $900 billion to $1 trillion in US B2C agentic commerce revenue by 2030. That’s not a forecast about a distant future. Stripe launched the Agentic Commerce Suite on December 11, 2025, and WooCommerce was named a launch partner the same day. Over 4 million WooCommerce stores are now in the pipeline to receive their first AI-agent orders.

The suite solves a specific integration problem. Before ACS, connecting your store to a single AI shopping agent — ChatGPT, Copilot, Perplexity — meant building and maintaining a custom API endpoint for each one. Different catalog specifications, different checkout flows, different payment handling. Stripe estimated this could take up to six months per agent. ACS collapses that to a single integration point.

You connect your product catalog to Stripe once. Stripe syndicates your product data, pricing, and availability to every AI agent you enable in the dashboard. When an agent-initiated purchase happens, Stripe handles the checkout session, processes payment via a Shared Payment Token, and delivers the completed order to your store via webhook. The Agentic Commerce Protocol — co-developed by Stripe and OpenAI in September 2025 — provides the shared technical language that makes this work across agents.

Brands already live on ACS include Urban Outfitters, Anthropologie, Etsy, Coach, Kate Spade, Ashley Furniture, Revolve, and Nectar. The ecommerce platforms rolling out ACS support include WooCommerce, Shopify, BigCommerce, Squarespace, Wix, and commercetools.

You may be interested in: Stripe Agentic Commerce Suite Just Went Live for WooCommerce

Shared Payment Tokens: The Cryptographic Primitive#

The technical solution to the question nobody outside payment-protocol circles was asking: what happens when AI agents become a payment fraud surface?

Here’s the thing. Traditional checkout assumes a human enters card details on a merchant’s payment page. The merchant — or their payment processor — handles the credential. In agentic commerce, the AI agent sits between the buyer and the merchant. If the agent handles raw card credentials, every compromised agent becomes a credential-theft vector.

Shared Payment Tokens eliminate that surface entirely. When a buyer authorises a purchase inside Copilot or ChatGPT, Stripe issues a single-use token scoped to one transaction, one merchant, and one amount. The AI agent receives this token — not the card number, not the CVV, not the expiry date. The agent passes the token to the merchant’s Stripe integration, which processes the payment. If the token is intercepted, it can’t be reused or redirected.

Stripe’s Shared Payment Tokens are single-use cryptographic credentials that let AI agents authorise purchases without ever seeing the buyer’s card number, eliminating the credential-theft surface that conventional checkout flows create.

The consent layer matters as much as the cryptography. Before Stripe issues the token, it validates verifiable consent credentials — proof that the buyer explicitly authorised this specific purchase through this specific agent. That consent verification is what separates a legitimate agentic purchase from an agent acting without authorisation.

In March 2026, Stripe expanded SPTs to support Visa Intelligent Commerce and Mastercard Agent Pay network tokens, plus BNPL providers Affirm and Klarna. That expansion made SPTs the only payment primitive that unifies cards, network tokens, and flexible payments in a single interface for agentic commerce.

How Copilot Checkout Uses Stripe ACS#

The purchase completes inside the conversation. Your WooCommerce store never sees a browser.

Microsoft unveiled Copilot Checkout at the NRF 2026 retail conference in January 2026. The feature lets shoppers complete purchases directly inside a Copilot conversation without being redirected to the retailer’s website. Stripe, PayPal, and Shopify handle the payment processing. Copilot Checkout is live in the US.

The flow works like this. A Copilot conversation naturally leads to a product recommendation. When the user signals purchase intent, Microsoft communicates with Stripe through a direct integration. Stripe connects to the merchant’s store via the Agentic Commerce Protocol, pulling real-time product data, pricing, and shipping options. A native checkout interface appears inside the Copilot conversation.

The buyer enters their payment credentials within Copilot. Those credentials never reach the merchant. Stripe issues a Shared Payment Token, passes it to the merchant’s Stripe integration, and the payment processes. The merchant receives a completed order via webhook. No browser opened the merchant’s site. No JavaScript executed on the merchant’s domain. No client-side tag fired.

For WooCommerce stores, this means the order appears in WooCommerce admin — a real, recorded order with line items, shipping address, and payment confirmation. But GA4 has no record of the purchase event. Meta Pixel never fired. Google Ads has no conversion to attribute. The order is revenue. The order is also invisible to every advertising platform the store optimises against.

ACS Timeline: From Launch to Network Token Support#

Six months from announcement to production-grade multi-network payment primitive.

Date	Event	WooCommerce Impact
September 2025	Stripe and OpenAI launch Agentic Commerce Protocol (ACP)	Open standard established; ChatGPT Instant Checkout goes live on ACP
December 11, 2025	Stripe launches Agentic Commerce Suite; WooCommerce named launch partner	WooCommerce Stripe Gateway begins ACS integration development
January 8, 2026	Microsoft unveils Copilot Checkout at NRF 2026 with Stripe, PayPal, Shopify	Copilot Checkout live in US; WooCommerce stores on Stripe can receive orders
March 3, 2026	SPTs expanded: Visa, Mastercard network tokens; Affirm and Klarna BNPL	Agentic orders can now use BNPL and network tokens through same SPT interface
April 14, 2026	WooCommerce 10.7 ships agentic_commerce gateway flag in core	Any payment gateway plugin can declare itself agentic-commerce capable
April–June 2026	WooCommerce Stripe Gateway rolling out ACS settings, feed sync, webhook handling	Agentic Commerce UI, product feed sync dashboard, checkout.session.completed processing

40% of Americans have already made a purchase they would not have considered without an AI agent recommending it, according to a 2026 Visa and Morning Consult study. The volume curve is accelerating while the measurement infrastructure on most stores is still designed for browser-based checkout.

McKinsey projects $900 billion to $1 trillion in US B2C agentic commerce revenue by 2030, and 40% of Americans have already made a purchase they would not have considered without an AI agent recommending it.

You may be interested in: WooCommerce ACP vs UCP: Agentic Commerce 2026

WooCommerce Stripe Gateway: What Ships and When#

The official plugin is shipping Agentic Commerce settings, feed sync, and webhook handling. The tracking gap remains your problem.

The WooCommerce Stripe Gateway plugin changelog tells the story. Recent releases added an Agentic Commerce settings UI with feature introduction, onboarding guide, enable/disable toggle, and webhook secret management. An admin dashboard for monitoring product feed sync status, history, errors, and triggering manual syncs. Detection of Agentic Commerce sessions via payment_intent.agent_details so their checkout.session.completed webhooks aren’t skipped.

The plugin also fixed a critical issue: Agentic Commerce checkout.session.completed orders were failing on null WooCommerce sessions. That failure is precisely what you’d expect when an order arrives with no browser session — the plugin was looking for a WC session object that doesn’t exist in an agentic flow. The fix handles the null session gracefully and creates the order from the webhook payload alone.

For SKU management, the plugin now uses SKU as the Agentic Commerce catalog identifier so checkout.session.completed line items resolve correctly, with a product-ID fallback for SKU-less products. Product deletion events are batched and uploaded to Stripe as a product_catalog_feed with delete:true, keeping your agent-facing catalog in sync.

What the plugin doesn’t solve: sending the conversion event to your advertising platforms. The webhook delivers the order to WooCommerce. Your GA4 tag doesn’t fire because there’s no browser. Your Meta Pixel doesn’t fire for the same reason. The gap between “WooCommerce received the order” and “GA4/Meta/Google Ads received the conversion signal” is where revenue becomes invisible.

The Invisible Revenue Problem#

The order exists in WooCommerce admin and in Stripe. It exists nowhere else.

Follow a single Agentic Commerce Suite purchase from intent to confirmation. A user tells Copilot to buy a product from your store. Copilot calls your store’s ACP endpoint via Stripe for catalog and pricing. GA4 sees nothing — no browser, no JavaScript, no client_id. Meta Pixel doesn’t fire. Google Ads has no impression to log.

Stripe issues a Shared Payment Token. The payment processes. A checkout.session.completed webhook hits your WooCommerce store. The Stripe Gateway plugin creates the order. If your store fires GA4, Meta Pixel, or Google Ads conversion tags only on the WooCommerce thank-you page, none of them fire — there is no thank-you page being loaded.

The downstream effects compound. Your GA4 acquisition report undercounts revenue. Your Google Ads Smart Bidding model trains on incomplete conversion data. Your Meta Advantage+ campaigns optimise against a signal that is silently becoming less representative of actual revenue. Every week that agentic order volume grows, the optimisation gap widens.

Translation: a store that receives 5% of revenue from agentic orders today might attribute those sales to “direct / none” in GA4 — or not attribute them at all. As the agentic share grows toward the McKinsey projection, the stores optimising ads without the server-side conversion signal will be making budget decisions based on an increasingly incomplete picture of which channels actually drive revenue.

Attributing Agentic Orders Back to Ad Platforms#

The webhook carries the signal. A server-side pipeline delivers it.

The checkout.session.completed webhook payload for an ACS order includes payment_intent.agent_details — a field that doesn’t exist on standard Stripe orders. This field carries the agent attestation: which AI surface originated the purchase (Copilot mobile, Copilot desktop, ChatGPT, Brand Agent), the Shared Payment Token attestation, and the consent verification metadata.

A server-side event pipeline reads these fields from the webhook, constructs a conversion event, and delivers it directly to Microsoft Ads UET CAPI, Google Ads Conversion API, and Meta Conversions API. The conversion hits the ad platform server-to-server, bypassing the missing browser session entirely. Your bid optimisation model receives the signal. Your attribution reports reflect the revenue.

The pattern is the same one that server-side tracking uses for any non-browser conversion — phone orders, POS transactions, CRM-triggered purchases. The difference is that agentic commerce adds a new conversion source that will scale faster than any of those channels. Transmute Engine™ handles this by reading the agent_details attestation fields from the Stripe webhook, enriching the event with the standard attribution dimensions, and writing the conversion to every configured downstream destination in a single processing pass.

For stores not running a server-side pipeline, the minimum viable capture is a WordPress action hook on woocommerce_payment_complete that checks for the presence of agent_details in the Stripe charge metadata, logs the agent source as order meta, and sends a server-side API call to your primary ad platform. It’s not elegant, but it’s the difference between seeing the revenue and not seeing it.

Key Takeaways#

• Stripe’s Agentic Commerce Suite is the payment infrastructure behind Microsoft Copilot Checkout — a single integration that connects your product catalog to AI agents via the Agentic Commerce Protocol, with WooCommerce as a named launch partner.
• Shared Payment Tokens are single-use, narrowly-scoped cryptographic credentials that let AI agents authorise purchases without handling card numbers, eliminating the credential-theft surface that would make agentic commerce a fraud magnet.
• Copilot Checkout purchases complete with no browser session on your site — no JavaScript executes, no client-side tag fires, and no thank-you page loads, making the order invisible to GA4, Meta Pixel, and Google Ads by default.
• The WooCommerce Stripe Gateway plugin is shipping ACS support including Agentic Commerce settings UI, product feed sync, and checkout.session.completed webhook handling — but it doesn’t solve the advertising attribution gap.
• Server-side event capture is the only way to attribute agentic orders back to the advertising platforms that drove the buyer to Copilot in the first place, using the payment_intent.agent_details field from the Stripe webhook payload.
• The revenue gap compounds over time — every agentic order that goes untracked degrades the accuracy of Smart Bidding, Advantage+, and any other automated optimisation model trained on browser-based conversion data.

References#

• Stripe. (2025). Introducing the Agentic Commerce Suite: A Complete Solution for Selling on AI Agents. stripe.com
• Microsoft Advertising. (2026). Conversations That Convert: Copilot Checkout and Brand Agents. about.ads.microsoft.com
• American Banker / PaymentsSource. (2026). Stripe Advances Security for Agentic Commerce. americanbanker.com
• WooCommerce. (2026). Stripe’s Agentic Commerce Suite Launching With WooCommerce Support From Day One. woocommerce.com
• McKinsey & Company. (2025). Agentic Commerce Revenue Projections: US B2C Market 2025-2030. mckinsey.com
• Visa / Morning Consult. (2026). AI Agent Purchase Influence Survey: US Consumer Behaviour. usa.visa.com

If your WooCommerce store uses Stripe and you’re preparing for the agentic order volume that’s already arriving, explore how server-side tracking captures every conversion — including the ones that never touch a browser.