Sunday, November 15, 2026 Independent reporting on artificial intelligence Newsletter
AI News Beats
AI Companies

OpenAI launches ChatGPT Wallet with approval for every purchase

The initial rollout covers eligible US adults on ChatGPT Pro, with payment tokens replacing actual card details during agent-assisted checkout.

A person holds a payment card while sitting behind a laptop
Photo: Vitaly Gariev / Unsplash

OpenAI began rolling out ChatGPT Wallet on November 13, giving its dots assistants a payment method that requires customers to approve each purchase. Access initially covers US ChatGPT Pro subscribers aged 18 or older with eligible US-issued cards.

The company developed the service with American Express, Mastercard and Visa. Customers review their items, total and selected card, then complete a security check. A network payment token substitutes for the actual card credentials. OpenAI says existing card rewards and protections for eligible disputes remain available.

A payment option, not a new storefront

OpenAI Developers’ payment documentation says Wallet can work with existing checkout forms without a dedicated integration. The merchant still processes the order and handles fulfillment, customer support and fraud decisions. A card already saved with a retailer can remain a separate authorized payment option.

The documentation also draws a boundary around reuse: approval applies to the particular transaction, not an unrelated later purchase. Subscription purchases are supported when the merchant’s checkout supports recurring billing and obtains the customer’s consent. That distinction matters because completing one checkout and authorizing an ongoing charge are different commitments.

Existing fraud tools can still reject legitimate activity from a cloud browser. OpenAI says it is rolling out user signals through an HTTP header, a piece of information sent with a web request. Those signals can include a country estimate, locale or time zone, but availability varies during rollout. The payment guide does not promise that every authorized transaction will succeed.

Website access remains a separate hurdle

OpenAI Developers’ agent-access documentation explains that a merchant does not need a product feed or plugin for ChatGPT’s browser to navigate its website. Those integrations serve different purposes from permitting a verified browser visit. The browser can use the site’s existing purchasing or booking process.

Where security systems block that traffic, the documentation describes narrowly recognizing signed requests rather than removing general protections. Akamai, Cloudflare, HUMAN and Vercel can verify request signatures automatically. Other providers can validate signatures using published public keys and the HTTP Message Signatures standard.

That access is distinct from permission for search crawlers. OpenAI says an exception for verified browser visits does not alter the treatment of other bots, and existing page-level access controls should remain in place. A merchant can therefore evaluate browser compatibility without treating every automated visitor as a customer. The access guidance ties verification to signed requests and published keys, not merely a visitor claiming to be an OpenAI agent. That separates identity verification from a blanket exception for automated traffic.

What the rollout does not yet establish

OpenAI describes purchasing within preapproved limits as a future direction, not the launch behavior. Wider international availability has no announced timetable. Merchant compatibility remains a separate question from eligibility to use the wallet.

Stay on top of AI

Get the stories that matter in artificial intelligence, straight to your inbox.

Free. One email with the stories that matter. Unsubscribe any time. See our privacy policy.