Article · AI agents · ChatGPT Wallet · agentic commerce · payments

ChatGPT can now pay on your site for some US users

On 13 November 2026 OpenAI launched ChatGPT Wallet, so a ChatGPT agent can pay on your existing checkout. At launch it is limited to ChatGPT Pro subscribers aged 18 or older in the United States, with an eligible US-issued card; OpenAI's release notes also require a US billing address and say the rollout is gradual. OpenAI published guidance on signed agent requests, payment risk, and a Forwarded header that may carry the user's IP, country, locale and time zone. Those extra header fields match an 11 November author draft that says it has not been submitted to the IETF's draft repository or adopted by a working group. What changed, the limits, and what to check.

The question
Can ChatGPT pay on my website, and what should I check?
The short answer
On 13 November 2026 OpenAI launched ChatGPT Wallet. After a user adds an eligible card, a ChatGPT agent can pay on your existing checkout once the user reviews the merchant, items, total and card and approves the purchase with a security check such as Face ID or a fingerprint. OpenAI says it does not share the user's actual card details with the business or the agent. At launch this is limited: it is rolling out gradually to ChatGPT Pro subscribers aged 18 or older in the United States, with an eligible US-issued card, through what OpenAI calls dots, the ChatGPT agents that complete the purchase. OpenAI's release notes also require a US billing address, and say some websites may not support agent purchases and that approval alone does not confirm an order. Our read: treat this as an early, limited rollout, and check whether your firewall, risk tools, analytics, product information and privacy notices can handle an agent paying on a customer's behalf.

TL;DR: On 13 November, OpenAI launched ChatGPT Wallet. A ChatGPT agent can pay on your existing checkout after the user reviews the purchase and approves it with a security check. OpenAI says the payment uses a token, without sharing the actual card details with you or the agent. This is a limited rollout: ChatGPT Pro subscribers aged 18 or older in the US, with eligible US-issued cards, through what OpenAI calls dots, the agents that complete purchases on a user's behalf. OpenAI's release notes add a US billing address, say the rollout is gradual, and warn that some websites may not support agent purchases and that "approval alone doesn't confirm an order." Our read: check whether your firewall, risk tools, analytics, product information and privacy notices can handle the agents that can pay.

The likely default: hear that "AI agents can now buy on your website" and either open the gates to every bot, or tighten the firewall and wait.

Neither is what OpenAI is asking you to do. The guidance is narrower: let verified ChatGPT agent visits through, and help your payment and risk tools recognize a user-approved purchase completed by an agent.

What changed

OpenAI's announcement, dated 13 November 2026, introduces ChatGPT Wallet as a way for agents to pay on a user's behalf. A user adds a card once, reviews the items, total and selected card, and approves the purchase with a security check such as Face ID or a fingerprint scan. The payment network then provides a payment token — a substitute for the user's actual card details — and the charge goes to the selected card. OpenAI says it does not share those actual details with the business or the agent. OpenAI's payments guide says no Wallet-specific integration is required, and that Wallet works with existing checkout pages. You keep pricing, fulfillment, returns and customer service.

This is not a general release. The announcement says OpenAI is "starting with limited availability to ChatGPT Pro users," initially "through dots for ChatGPT Pro subscribers in the US," aged 18 and older, with eligible US-issued cards, beginning to roll out "today." The release notes add a US billing address, say the rollout is gradual, and warn that "some websites may not support purchases made by agents" and that "approval alone doesn't confirm an order." The release notes say "an eligible US-issued card" without naming which cards qualify.

To accept Wallet payments, OpenAI says, websites need to make sure agents are not blocked by accident, and payment and risk systems need to recognize legitimate agent purchases. Claim your business and, once verified, upload a product feed with current pricing and availability. Configure your CDN or firewall to recognize signed requests using Web Bot Auth; "browser access does not require a plugin or product feed." Work with your payments and risk providers, because risk systems may still flag, decline or cancel legitimate agent purchases. A plugin or WebMCP tools are optional extras.

OpenAI's agent-access guide says ChatGPT's cloud browser can already use your site — you do not need to add it to an allowlist — but your security settings may block the visits by accident. Those visits are identified with Web Bot Auth, which the guide says uses HTTP Message Signatures (RFC 9421). A signed request includes Signature, Signature-Input, and a Signature-Agent header set to "https://chatgpt.com", including the quotation marks. Akamai, Cloudflare, HUMAN and Vercel, the guide says, verify these signatures automatically; other providers can verify them before creating an exception. These visits "happen on a user's behalf and are separate from OpenAI's web crawlers, including OAI-SearchBot for search." Existing page-level access controls should stay in place. OpenAI says it does not yet let specific site owners control what actions users can take, but that "across all our users, we require human review before any consequential action."

The payments guide says risk systems are often tuned to detect bots and rely on signals such as IP addresses or browser details. ChatGPT's cloud browser "can set off these systems by accident and cause purchases to fail." That is why OpenAI is "rolling out support for relaying user signals through the Forwarded HTTP header." If you use a third-party risk provider, it says to make sure your configuration "properly ingests these new signals." If you run your own risk systems, "start observing the Forwarded header." Then this limit, in OpenAI's words: "The signals you receive may vary as we roll out support for every site." The parameters that may be included are the user's IP address (for), a country estimate, a masked network prefix, the origin AS number, locale, time zone, and a name for the user's browser or app.

The Forwarded header itself is defined in RFC 7239, and for is already one of its parameters. The extra fields for country, locale, time zone and the rest match an author draft whose two authors are listed with OpenAI. It was shared with the IETF HTTP working group mailing list on 11 November 2026. That draft defines six optional extension parameters for the existing header. Its own note says it "has not been submitted to the IETF Internet-Draft repository or adopted by an IETF working group." The mailing-list post says the draft would be submitted "once submissions reopen after November 14." Those extra fields are, as of that draft, a proposal, not an adopted standard.

What it means for your business

This section is our read, not OpenAI's.

The useful change is not that "agents can buy now" in general. It is that one company has started a limited way for a user-approved agent to complete checkout on an ordinary website. Most of your customers will not be in that group yet. The ones who are can still fail at your firewall or your fraud check.

The same mismatch can show up in analytics. OpenAI's two developer guides do not discuss analytics, but the risk problem they describe — a cloud browser that does not look like the user's own device — is the same kind of signal your reports and bot filters use. A signed agent visit can be hidden, counted as a bot, or given the wrong country.

The Forwarded header also has a privacy consequence that OpenAI's two developer guides do not spell out. If you start reading a user's IP address, country estimate, locale and time zone out of that header, that is information about the customer, passed by an intermediary. Whether your privacy policy already covers it is a question for you and your counsel.

A product feed is still worth doing, but not because checkout depends on it. OpenAI says the feed helps ChatGPT show accurate pricing and availability, and that browser access does not require one. This also sits next to a problem we have already covered: what happens when an AI agent submits a form on your site. The customer still needs your order confirmation, not only the approval screen in ChatGPT.

What to do this week

  1. Treat the rollout as limited. Wallet is starting with ChatGPT Pro subscribers aged 18 or older in the US, with an eligible US-issued card, through dots. The release notes also require a US billing address and say the rollout is gradual. Don't brief a manager as if every ChatGPT user can already pay.
  2. Check your firewall or WAF for verified ChatGPT agent traffic. Follow OpenAI's agent-access guide so signed Web Bot Auth requests are not blocked by accident. Keep this separate from your rules for OpenAI's search crawlers, and leave existing page-level access controls in place.
  3. Talk to your payments and risk providers. Ask how they treat agent-completed checkouts and whether they read the Forwarded header OpenAI describes. If you run your own risk checks, start logging that header. Remember OpenAI's caveat: the signals you receive may vary.
  4. See how agent visits appear in your analytics. This is our advice, not OpenAI's. Look at whether signed cloud-browser sessions are filtered out, marked as bots, or given the wrong location.
  5. Review your privacy notices. This is also our advice. If you will use IP, country, locale or time-zone signals from the Forwarded header, check whether your privacy policy already describes that use.
  6. Claim your business and upload a current product feed. OpenAI suggests this so customers see accurate pricing and availability. It is not required for the cloud browser to open your site.
  7. Use your own order confirmation as the source of truth. The release notes say approval in ChatGPT does not, by itself, confirm an order.

Sources

Want to know what AI says about your business?

We check it for you.