A partner email arrives asking whether an independent buyer-agent can finish a purchase on your store with a Shop Pay token. Shop Pay is already on under Shopify Payments. Sales channels > Agentic still shows Allow Shopify to manage for me. Nobody has written down which AI channels may complete inside the conversation, and which carts still send the buyer to your continue_url.
The job this week is a sheet: record whether Shop Pay is on, which Agentic channels allow direct checkout, and which buyer-agent purchases still need a storefront handoff versus a Shop Pay delegated payment.
Introduction
This article teaches you to walk that inventory. Tracking where ChatGPT and other assistants already send sessions, and how those landings convert, belongs in AI Shopping Traffic and Agentic Commerce on Shopify. Catalogue fields that help agents find a SKU belong in Shopify AI Product Discovery: UCP Catalog and Data Readiness. This piece stays on payment completion: Shop Pay, Agentic channel settings, and the handoff that still owns most UCP checkouts.
Shopify's own agent docs describe two endings. Most agents build a cart, create a checkout, and send the buyer to the merchant continue_url. Trusted agents with completion permission can call complete_checkout when the session is ready. Shop Pay delegated payments sit on that second path: the platform shows Shop Pay, the buyer picks a saved method, and the platform submits a Shop Token. The merchant stays merchant of record.
Platform builders keep asking Shopify for a Shop Pay client_id and for permission to complete. Token-tier authentication on a hosted UCP profile is enough to talk to checkout tools, and it still leaves completion locked until Shopify grants the client and the merchant enables that agent channel. Your admin work is the merchant half of that gate.
What the community is reacting to
Buyer-agent teams want a native UCP checkout that keeps the shopper inside their own interface. Those teams describe the same intended flow: find the variant, build a cart with a delivered total, show Shop Pay so the platform never stores card data, then submit the token. They also ask for a sandbox that can test declines, retries, and authentication challenges.
A second cluster is already further along on authentication and still blocked on completion. Those teams hosted a UCP profile, obtained Global API credentials, and wait on Shopify to approve complete_checkout on the client. A checkout that reports ready_for_complete is only a session state, so the agent still needs a separate grant before it can place the order.
Catalogue access, Agentic direct checkout, Shop Pay on the storefront, and UCP completion permission are four different switches, and the merchant gap is a missing owner for each one. If you treat "we have Shop Pay" as the whole answer, you will promise a partner a token path your store cannot honour, or you will leave Allow Shopify to manage for me on while an Other channels group starts reading your catalogue.
Record whether Shop Pay is on
Open Settings > Payments and confirm Shop Pay is active as part of Shopify Payments. Shop Pay stores the buyer's email, payment method, and shipping details so a returning shopper can finish faster. Shopify Help also says activating Shop Pay turns on Sign in with Shop when the store uses customer accounts, which is a storefront identity path rather than a UCP token.
Shopify's Shop Pay payment handler is the UCP side of the same product. For a Shopify merchant, Shopify automatically advertises UCP payment handlers, including Shop Pay, so you do not paste a shop_id into a JSON file. External merchants who want the same handler must register for Shop Pay and obtain that shop_id themselves.
Write three columns on the Shop Pay row:
- Storefront Shop Pay: on or off under Shopify Payments, plus a live test order on a phone.
- Sign in with Shop: present or absent next to New Customer Accounts. Login rebuilds belong in Shopify New Customer Accounts vs Classic: A Decision Framework; keep that work on a separate owner so a wallet token and a login template do not share one ticket.
- Handler advertised: assume Shopify publishes
dev.shopify.shop_payfor you once Shop Pay is live, then verify with a partner or a UCP checkout response that the handler appears. You do not register a platformclient_id. That id belongs to the buyer-agent that wants Path A.
Path A is a one-time Payment Request. The platform constructs totals, fulfilment options, and line items, hands the buyer to the Shop Pay interface, and receives a single-use Shop Token scoped to that checkout. Path B is identity linking: the platform links one buyer's Shop identity and may reuse a scoped token across checkouts for that buyer only. Both paths submit payment_data with credential.type set to shop_token. Path B tokens must stay scoped to one identity, and platforms must not share them across users or sessions.
If Shop Pay is off, stop the inventory there and decide whether you will turn it on before any agent conversation. Delegated payment has nothing to submit without Shop Pay. If Shop Pay is on, move to Agentic settings before you answer the partner email.
Record which Agentic channels allow direct checkout
Open Sales channels > Agentic. Eligible stores start with Allow Shopify to manage for me on, which gives agentic channels Shopify Catalog access, activates direct checkout where the channel supports it, and auto-enrols you in new storefronts.
Record each named channel as catalogue, direct checkout, or storefront handoff:
| Surface | What Shopify documents today | What you write on the sheet |
|---|---|---|
| ChatGPT | ChatGPT is a discovery referrer, so buyers finish on your online store checkout in the in-app browser or a new tab, and Shopify documents no ChatGPT direct-checkout toggle. | Record catalogue access for ChatGPT, and write the completion path as your own checkout every time. |
| Google AI Mode and Gemini | Direct checkout can stay inside the conversation when you leave that Google setting on for eligible stores. | Record catalogue access, whether direct checkout is on, and the named owner who approved that setting. |
| Microsoft Copilot | Copilot follows the same pattern: Shopify Catalog access plus an optional direct-checkout setting for the conversation. | Record the same three cells you used for Google: catalogue, direct checkout, and approving owner. |
| Meta surfaces such as Muse | Meta surfaces also combine Shopify Catalog access with an optional direct-checkout setting inside the conversation. | Record the same three cells you used for Google: catalogue, direct checkout, and approving owner. |
| Shop app | Shop is a Shopify-owned agentic channel, Shopify Catalog access cannot be turned off from Agentic, and checkout behaviour lives in the Shop sales channel instead. | Record the Shop selling method, and keep Agentic toggles off the Shop checkout row so owners stay distinct. |
| Other channels | This grouped option covers smaller and emerging AI agents, including independent developers who are testing Shopify Catalog. | Record whether the group may read Shopify Catalog, and assume completion still needs a later Shopify entitlement. |
| Independent UCP platform with Shop Pay tokens | That platform needs a Shop Pay client_id, completion permission on the client, and your merchant channel enabled for that agent. | Record the partner name, whether you can see a channel to enable, and whether you have already promised a token path. |
If you turn Allow Shopify to manage for me off, Shopify Help says you can manage catalogue access, auto-enrolment, and per-channel direct checkout yourself. Turning catalogue access off also turns direct checkout off, and product data can take up to seven days to leave Shopify Catalog. Turning Allow Shopify to manage for me back on reactivates every agentic setting, including direct checkout.
Write the date you last opened this screen. Auto-enrolment means a new channel can appear after a quiet week, and the sheet is stale the moment you skip that date.
Record which buyer-agent purchases still need continue_url
Shopify's cart and checkout docs for agents keep the merchant as merchant of record. After discovery, an agent can iterate on a Cart MCP session, convert that cart with create_checkout, then either send the buyer to continue_url or, when eligible, call complete_checkout. Every non-terminal checkout response includes continue_url. Status values include incomplete, requires_escalation, and ready_for_complete.
Treat ready_for_complete as "the session has the fields Shopify needs," and treat completion permission as a separate grant. Shopify must approve the client, and you must enable that onboarded agent channel. Until both are true, the honest merchant answer is a handoff to your checkout, even when Shop Pay is on.
Some carts will never be a clean token submission. Checkout WebMCP, which runs in the buyer's browser on the checkout page, does not register tools for standard three-page checkout unless the buyer uses Shop Pay, and it also skips B2B checkout, embedded checkout, mobile checkout SDKs, draft orders, order edits, and app-defined checkout extension interactions. In-tab storefront tools are a different door, covered in Shopify WebMCP: What In-Browser AI Agents Can Do on Your Store. Put those limitations on the inventory so a gift-with-purchase extension or a delivery-date field does not surprise you on the first agent order.
Walk one live SKU that a partner would actually buy. Place a guest checkout and a Shop Pay checkout yourself, and if either path already fails, fix that with How to Fix Shopify Checkout Abandonment When Your Funnel Looks Healthy before you discuss tokens. List checkout UI extensions on that SKU, including gift notes, delivery slots, custom attributes, and any Function that changes totals, then mark each one as agent-safe or human-only. Confirm marketing pixels still read Customer Privacy after a Shop Pay or wallet redirect, using How to Fix Shopify Checkout Consent When Marketing Pixels Stay Denied if the thank-you page is already dark. Write the fallback in one sentence: this SKU completes on continue_url until you remove the extension or Shopify entitles the agent.
Hype vs reality
The conversation around buyer-agents often jumps from "Shop Pay is on" to "agents will check out for the customer." The platform is more precise than that, and the sheet should be too.
| Claim in the air | What Shopify documents | Merchant action |
|---|---|---|
| Shop Pay being live means every agent can pay on the store. | Shop Pay is an accelerated checkout and a UCP handler, while completion still needs entitlement and, for most agents, a continue_url handoff to your storefront. | Record Shop Pay on or off, then write the completion path for each named channel on its own row. |
| A ready_for_complete checkout can be finished by any authenticated agent. | Checkout tools need a signed or token request, and complete_checkout still needs an extra Shopify grant on that specific client. | Tell the partner that a green session status records readiness, and that it still leaves the order unplaced until Shopify grants completion. |
| Agentic settings are one switch that covers every AI surface the same way. | ChatGPT stays a discovery referrer, Google Copilot and Meta can offer in-conversation checkout, Shop is managed in its own channel, and Other channels is a catalogue group. | Give each surface its own row on the sheet, and write the date of the last review next to the setting. |
| Merchants must register a Shop Pay client_id before tokens can land. | Platforms register for Path A, and Shopify advertises the Shop Pay handler for Shopify merchants once Shop Pay is already on. | Close that ticket on the merchant side, and ask the partner for their Shopify intake status instead of a store setting. |
| Identity linking replaces customer accounts on the storefront. | Path B links one buyer's Shop identity for delegated tokens, while Sign in with Shop is a storefront login that appears when Shop Pay and customer accounts are on. | Keep login rebuilds and token scope on two rows so accounts work and payment tokens stay with different owners. |
What merchants should do now
Fill the sheet in one sitting, then assign owners. Ignore the partner pitch until the first three rows are written. Watch named Agentic channels weekly while auto-enrolment is on. Act when a partner names a client you can actually enable, or when a checkout extension would block the SKU they want to sell.
Copy this as the working table:
| Row | What you record | Owner |
|---|---|---|
| Shop Pay | Write on or off, plus the date of a live Shop Pay test order on a phone. | Payments and checkout owner |
| Sign in with Shop | Write present or absent, and point to the customer-accounts decision so login work stays on that ticket. | Accounts and theme owner |
| Allow Shopify to manage for me | Write on or off, and the date someone last opened Sales channels > Agentic. | Ecommerce lead |
| Named AI channels | Write catalogue and direct-checkout state for ChatGPT, Google, Copilot, Meta, and Shop on separate lines. | Ecommerce lead |
| Other channels | Write whether the emerging-agent group may read Shopify Catalog after you turned manage-for-me off. | Ecommerce lead |
| Handoff SKUs | List checkout extensions or B2B paths that still force a continue_url handoff for that product. | Theme and checkout owner |
| Partner token path | Name the agent, whether a channel exists to enable, and whether you have already promised a token path. | Ecommerce lead with the technical partner |
If the partner cannot show a Shopify intake or a channel you can toggle, keep their traffic on continue_url and Shop Pay on your checkout. That is still a working agentic sale. Discovery and a prefilled cart already move demand; completion rights arrive later, and they arrive per client.
Conclusion
You can now record whether Shop Pay is on, which Agentic channels allow direct checkout, and which buyer-agent purchases still need a continue_url handoff versus a Shop Pay delegated payment. Shop Pay is the payment method. Agentic settings decide who may finish inside a named AI channel. UCP completion is a grant Shopify issues to a specific client, and most carts will still land on your storefront until that grant exists.
When checkout extensions, Markets, and Agentic settings disagree about who can place the order, a Shopify stack audit lists the owner of each switch before you promise a token path. Checkout UI extensions that force a human step can be scoped through Shopify UI Extensions and Functions. Book a stack assessment if the sheet already has two owners and no date for the next review.
