OpenAI launched ChatGPT Wallet on Friday, November 13, a payment feature that lets its dots agent complete purchases for users and asked site owners to stop blocking those agents. Access starts with US-based ChatGPT Pro adults whose cards were issued in the US and qualify. For search and ecommerce teams, the stake is simple: a shopper’s agent that cannot load a checkout page never reaches the payment step.
According to OpenAI’s announcement, a user enters a card one time, then checks the cart contents, the total, and the chosen card ahead of every purchase. A biometric check confirms each approval, such as a face scan or a thumbprint. The payment network then issues a token that stands in for the real card details, so the agent never sees them. OpenAI says cardholders keep their current rewards and dispute coverage where eligible. It names four partners on the build: Visa, Mastercard, Chase, and American Express.
Merchants keep the customer relationship. OpenAI states that the sale runs between shopper and business, and the business still decides pricing, shipping, refunds, and support. The company also says it expects users to eventually delegate purchases fully by setting limits on spending, categories, or time periods. That delegation is described as a future step, not part of the current release.
The part that matters most to site owners is the Commerce Partner Playbook published alongside the product. It lists four areas of work:
- Accurate product data: register the business inside ChatGPT, and after verification supply a product feed carrying live prices and stock status.
- Agent access: set the CDN or firewall to accept requests signed with Web Bot Auth, and check that no security rule turns ChatGPT agents away. Browser access needs no plugin or feed.
- Payments and risk: the fraud-prevention names are Forter, Riskified, Sardine, and Signifyd. On the processing side it lists Adyen, Checkout.com, and Stripe.
- Deeper integration: write a plugin, or expose WebMCP tools.
OpenAI itself concedes that certain sites could block wallet purchases by accident, along with those from rival agentic payment products. That admission shifts the problem from search visibility to bot management. Many teams tuned their firewalls to cut scraper traffic and have not revisited those rules for agents acting on a customer’s behalf.
The announcement leans on OpenAI’s own figures. It puts weekly ChatGPT usage at 1.2 billion people and says many of them research products and weigh options there. That number is the company’s claim, and the post offers no data on how many of those users hold a Pro subscription or how many will route purchases through an agent. It also gives no conversion or revenue figures from any merchant.
The rollout is narrow, so near-term sales volume is likely small. The preparation cost, though, is front-loaded and mostly sits with teams that already own the relevant systems. Product feeds, CDN rules, and fraud tooling are separate workstreams, often held by separate teams, and a signed-request rule takes far less time to add than to coordinate.
Before the wallet reaches a wider audience, ecommerce and SEO leads should check CDN and web application firewall logs for blocked requests from ChatGPT agents, then agree with their fraud and payments vendors on how an agent-initiated, tokenized purchase will be scored.
OpenAI, “Introducing ChatGPT Wallet,” published November 13, 2026.