ChatGPT Wallet: what stores should check at checkout

ChatGPT Wallet starts with eligible US Pro users. Check agent access, payment risk signals and customer approval before changing your store’s workflow.

Will Slatton3 min read

OpenAI has launched ChatGPT Wallet so its dots agents can complete purchases through a store’s existing checkout. The 13 November rollout starts with US ChatGPT Pro subscribers aged 18 or older who have eligible US-issued cards.

For merchants, the immediate task is to check whether legitimate agent visits can reach checkout and whether risk systems understand them. OpenAI’s payment guidance says no Wallet-specific integration is required. That does not guarantee every attempted order will succeed.

The shopper still approves each purchase

According to OpenAI’s announcement, the shopper reviews the items, total and selected card, then completes a security check such as Face ID. The payment network supplies substitute card details, keeping the actual card information from the agent and merchant. American Express, Mastercard and Visa are launch partners.

OpenAI describes broader pre-approved delegation, such as purchases within a spending limit, as a future direction. It is not the launch workflow. Customers buy from the business, which retains responsibility for fulfilment, returns and service.

Check access without opening the door to every bot

ChatGPT uses a cloud browser to interact with websites. Its access guide says an allowlist is unnecessary unless security settings block those visits. Akamai, Cloudflare, HUMAN and Vercel can verify ChatGPT request signatures automatically.

For a store using Cloudflare, the documented control is under Security → Settings → AI Crawler and Agent access policies: Personal Agents lists “dots, OpenAI”. Review that specific setting with whoever manages the site’s protection. Keep other security controls in place; an agent’s identity is not a reason to approve every order it attempts.

Ask your fraud provider about the signals it receives

Cloud-browser traffic can trigger rules built around a shopper’s normal browser and IP address. OpenAI is rolling out user signals through the Forwarded HTTP header, including location and browser context. The available fields may vary during rollout.

Our recommendation is to ask your payment or fraud provider whether those signals reach its decision system and how it verifies their source. Compare a failed purchase with the relevant access and payment logs before changing a rule. A header value alone should not become proof that an order is safe.

Assign an owner to review declined agent orders, and keep the ordinary customer support route visible. Successful payment still needs accurate stock, delivery promises and a usable returns process. This is a documentation-based launch review, not a completed test purchase from a Shopify store.

ℹ️
Launch access is limited. Every Wallet purchase requires the shopper’s approval; fully delegated buying is a future direction.

Product discovery is a separate part of the journey. See our ChatGPT Business Hub guide for business information and feed access.

14 November: Google Wallet connection is read-only

The similarly named Google Wallet connection in Gemini is a different capability. In its 13 November announcement, integration partner Plaid describes an opt-in US rollout that uses linked account information for personalised financial insights. It explicitly says Gemini has read-only access and cannot move, manage or invest money through this connection.

For a merchant, that announcement does not establish another agent checkout integration to enable. Keep spending insights separate from the user-approved purchases described above; a shared “Wallet” name does not make the two purchase paths equivalent.

19 November: a Muse test shows a future purchase rule

A 17 November report by Juozas Kaziukėnas illustrates a different approval pattern in Meta Muse. He requested new AirPods 4 sold by Best Buy for no more than $97 including charges. His screenshot shows the assistant rejecting a $109.99 marketplace listing as outside the seller and price conditions, then presenting a daily watch with a defined buying window and Shop Pay as the proposed payment method.

Kaziukėnas reports being asked to confirm the specification and approve a future payment. The supplied evidence shows setup of a conditional purchase, not a completed order. It does not establish general availability, payment success or that every shopper receives the same workflow.

The practical distinction is between approving an order now and authorising a rule for later. Merchants and app teams evaluating agent purchases should record the exact seller, product condition, all-in limit and expiry of that authorisation. This observation does not change the ChatGPT Wallet launch workflow described above.

Filed underAI

More from AI

See all →