ChatGPT Wallet lets a shopper pay on your website from inside ChatGPT, and you do not have to build anything to accept it. That is also the risk. OpenAI’s own developer docs say that risk systems tuned to detect bots can be set off by ChatGPT’s cloud browser “by accident and cause purchases to fail.” Below is what the docs say, read at the source on November 18, 2026, and what a merchant can check this week.
How ChatGPT Wallet pays on your store
According to OpenAI’s Accept payments guide:
- The customer reviews and approves the purchase in ChatGPT, and your checkout processes the payment.
- Wallet “works out of the box with existing checkout pages and payment forms.” No Wallet-specific integration is required.
- Your business handles the order, fulfillment, customer support and fraud decisions.
- You receive a network token, not the full card number. OpenAI says to use the Payment Account Reference (PAR) to link the token to the underlying account.
So there is no new endpoint to stand up, unlike a checkout protocol. The purchase arrives through the same page a human uses, driven by ChatGPT’s cloud browser.
Where the purchase can fail
Two layers sit between that browser and a completed order.
1. Your CDN or firewall. OpenAI’s
agent access page says the
cloud browser can already use your site without an allowlist, but that your
“security settings may unintentionally block these visits.” Akamai, Cloudflare,
HUMAN and Vercel verify ChatGPT’s request signatures automatically. On Cloudflare,
the traffic appears as dots, OpenAI under Personal Agents, or as detection ID
129220581 in WAF custom rules.
2. Your risk engine. This is the newer problem. A bot-blocking rule rejects the
visit; a fraud model can let the visit through and then decline the payment.
OpenAI’s answer is to relay user signals in the Forwarded HTTP header, rolling
out site by site. The parameters it lists:
for: the IP address observed for the ChatGPT userip-prefixandasn: the masked network prefix and the autonomous system numberip-country: a two-letter country estimatelocaleandtz: the user’s configured language and time zoneuser-agent: the user’s own browser or app
OpenAI’s instruction is short: if you use a third-party risk provider, ask them
whether your configuration ingests these signals; if you run your own, start
observing the Forwarded header. The guide adds that “the signals you receive may
vary” during the rollout.
What to check this week
- Ask your fraud vendor one question: does our setup read the
Forwardedheader from verified ChatGPT browser traffic, or does it score the cloud browser’s own IP? - Look for declines, not only blocks. A firewall block shows up in edge logs. A risk decline shows up as a failed payment from a session that looked normal.
- Verify before you exempt. Signed requests carry a
Signature-Agentheader set to"https://chatgpt.com", with public keys atchatgpt.com/.well-known/http-message-signatures-directory. OpenAI’s instruction is to verify signatures (RFC 9421) before applying any allowlist exception. Our Web Bot Auth checkout explainer covers the mechanism. - Do not reuse the credential. OpenAI says the customer consents only to the specific transaction. Recurring billing is allowed only if your checkout already supports it and you collect the customer’s consent.
FAQ
Do I need to integrate anything to accept ChatGPT Wallet?
No. OpenAI’s developer docs say ChatGPT Wallet works with existing checkout pages and payment forms, with no Wallet-specific integration. The optional steps are making sure your CDN or firewall does not block verified ChatGPT browser visits, and making sure your risk system can read the user signals OpenAI relays.
Why would a ChatGPT Wallet purchase be declined?
OpenAI says risk systems are often tuned to detect bots and rely on signals such as
IP addresses and browser details. ChatGPT’s cloud browser can trigger those systems
by accident, so the payment fails even though a real customer approved it. OpenAI
is rolling out a Forwarded header carrying the user’s IP, network, country,
locale, time zone and browser so risk tools can score the person, not the cloud
browser.
Does the merchant see the customer’s card number?
No. According to OpenAI, the merchant receives a network token instead of the full card number. The Payment Account Reference (PAR) lets the merchant associate that token with the underlying payment account. The token covers only the transaction the customer approved.
Sources
- OpenAI, Accept payments (Commerce developer docs), fetched 2026-11-18
- OpenAI, Help ensure cloud browser access to your site, fetched 2026-11-18
- OpenAI, Partner Playbook Overview, fetched 2026-11-18
- IETF, RFC 9421: HTTP Message Signatures, as referenced by OpenAI’s agent access page
A shopper approving a purchase is not the same as the purchase going through; the transaction is where agent readiness is won or lost.