Underwing · Explainers · November 17, 2026

ChatGPT Wallet on your checkout: what your store receives, and what can block the sale

On 13 November OpenAI launched ChatGPT Wallet, which lets ChatGPT’s agent pay for things on your own website. You don’t have to integrate anything to accept it: OpenAI says it “works out of the box with existing checkout pages and payment forms.” What reaches your checkout is a card network token, not the shopper’s card number, and your store still owns the order, the refund and the fraud decision. Two things can stop the sale: a firewall that turns the agent away before checkout, and a fraud check that declines the order. When I sent one ordinary browser request from a cloud server to 700 WooCommerce stores, 25 turned me away at the door. Every one of them was on Cloudflare, where the fix is a single setting.

Watch this explainer (about 3 min).

What OpenAI launched, and who can use it

The launch post says ChatGPT Wallet “will initially be available through dots for ChatGPT Pro subscribers in the US”, specifically “ChatGPT Pro subscribers aged 18 and older in the US with eligible US-issued cards.” So if you don’t sell to US shoppers, nothing reaches you yet. If you do, the audience starts small: Pro subscribers only. OpenAI doesn’t say how many people that is, so I won’t guess.

The purchase itself works like this. The shopper “reviews the items, total, and selected card, then approves it with a security check such as Face ID or a fingerprint scan.” Then “the payment network provides a payment token”, which OpenAI describes as “a substitute for the user’s actual card details”, carrying “a card number, security code, and expiration date.” ChatGPT’s browser types that into your checkout like any card. The networks named are American Express, Mastercard and Visa.

The agent buys on your site, through your checkout, the same way the browser agents I wrote about in the post on agent orders already do. Wallet just gives OpenAI’s agent its own way to pay.

How a ChatGPT Wallet purchase reaches your storeFrom OpenAI's launch post and merchant guide, 13 Nov 20261. Shopperapproves inChatGPT with FaceID or fingerprint2. Card networkissues a token: itsown number, codeand expiry date3. Cloud browserChatGPT's browserfills in your owncheckout pages4. Your checkoutcharges the tokenlike any cardpaymentGate 1: your CDN or firewallCan turn the browser away before itreaches checkout. OpenAI says Akamai,Cloudflare, HUMAN and Vercel verifyChatGPT's signature automatically.Gate 2: your fraud checkSees a cloud computer, not the shopper.The shopper's country, time zone andnetwork can arrive in a Forwardedheader, if your fraud tool reads it."Your business handles the order, fulfillment, customer support,and fraud decisions." (OpenAI)
Figure 1. A Wallet purchase, from OpenAI’s launch post and its Accept payments guide. The two red boxes are where a sale can fail on your side.

What lands in your checkout

OpenAI’s merchant guide, Accept payments, is short and worth reading in full. The parts that matter for a store owner:

  • No setup. “No Wallet-specific integration is required.” To your checkout, it looks like a card payment.
  • You don’t get the card number. “You receive a network token instead. Use the Payment Account Reference (PAR) to associate the token with the underlying payment account.” Whether your processor shows you the PAR depends on the processor. I haven’t checked which ones do.
  • One purchase only. “The customer consents only to the specific transaction. Don’t reuse or save that payment credential for a separate purchase.”
  • Subscriptions are allowed “if your existing checkout supports recurring billing”, as long as you get the customer’s consent for the recurring charges.
  • Saved cards keep working. Wallet “is a separate payment option.”

Support works as normal too. OpenAI’s agent access guide says “any customer service or support should be handled in the same way you would if a customer took the action themselves”, and the launch post says shoppers keep “their card’s existing rewards and protections for eligible disputes.” In plain terms: an agent order is a customer order. Refunds and chargebacks follow your usual process.

Gate 1: your firewall

ChatGPT shops through “a browser running on a computer in the cloud.” OpenAI says that browser “can already use your site. You don’t need to add it to an allowlist. However, your security settings may unintentionally block these visits.” It signs its requests with Web Bot Auth, and “Akamai, Cloudflare, HUMAN, and Vercel verify ChatGPT request signatures automatically.” On any other provider you’d have to check the signatures yourself against OpenAI’s published keys, which is a developer job.

Those keys rotate. On 9 October the key directory held one key set to expire on 16 October. Today it holds a different key, set to expire on 24 November. If you verify signatures yourself, fetch the keys each time.

I wanted to know how often a small store’s front door refuses a visit that looks like a browser on a cloud computer. On 10 November I sent one request with a normal Chrome user agent to each of 700 WooCommerce stores from my server, the same sample I used for the AI crawler test. 659 answered. 634 served their home page. 25 refused, and all 25 were behind Cloudflare. I checked those 25 again this morning: 21 still refused. 14 asked for a browser check (“Just a moment…”), and 7 showed a block page.

700 WooCommerce stores, one browser-like visit from a cloud server10 Nov 2026, re-checked 17 Nov. Plain request, Chrome user agent, not signed, no JavaScript.The 659 stores that answered634 served the home page25 refused the visitWhere those 659 stores sit239 Cloudflare420 elsewhere (1 Vercel, 0 Akamai seen)Cloudflare, Akamai, HUMAN and Vercel verify ChatGPT signatures automatically. HUMANcan't be seen from response headers, so it may be hiding in the 420.The 25 refusals, checked again on 17 Nov21 still refused, and all 21 are on Cloudflare:14 browser checks ("Just a moment…" or "Checking your browser…")7 block pages (403 Forbidden or Cloudflare "Attention Required")4 now serve the page. 41 stores that never answered at all are left out.
Figure 2. My test, not OpenAI’s. A plain request can’t run JavaScript or carry ChatGPT’s signature, so this shows which stores challenge a cloud visitor, not which ones would block ChatGPT.

Read that carefully, because my request is not ChatGPT’s. It wasn’t signed, and it couldn’t run JavaScript, which a real browser can. A real cloud browser might pass some of those 14 browser checks, and Cloudflare may treat a signed ChatGPT visit differently. What the test does show is where the risk sits. Across the 420 stores that weren’t on Cloudflare, not one refused my visit at the page level. The refusals were all on the one provider where OpenAI gives a two-minute fix.

On Cloudflare, that fix is in Security > Settings > AI Crawler and Agent access policies. Under Personal Agents, set “dots, OpenAI” to “Allow (do not block).” Cloudflare’s own documentation says Personal Agents “inherit the Agents policy by default” and that “Cloudflare recommends Allow (do not block) for Personal Agents.” If you’ve ever set the Agents policy to block, check this one.

Gate 2: your fraud check

This is the gate I can’t test from outside, and OpenAI is direct about it: “Risk systems are often tuned to detect bots and rely on observed signals like IP addresses or details about the connected browser. ChatGPT’s cloud browser can set off these systems by accident and cause purchases to fail.”

The reason is simple. Your checkout sees the address of OpenAI’s cloud computer, not the shopper’s. To fix that, OpenAI is “rolling out support for relaying user signals through the Forwarded HTTP header.” The header can carry the shopper’s IP address, the country estimated from it, their network, their browser, their language setting and their time zone. OpenAI adds: “The signals you receive may vary as we roll out support for every site.”

OpenAI names the companies it’s working with: “fraud prevention partners including Forter, Riskified, Sardine and Signifyd and payment service providers including Adyen, Checkout.com, and Stripe.” If you use one of them, ask them how they handle Wallet orders. If you run your own fraud rules, look at any rule that compares the visitor’s IP country with the billing address. My inference, not OpenAI’s statement: that kind of rule will see a cloud server’s location unless it reads the Forwarded header, and it could decline a real customer.

What I’d do this week

  • If you don’t sell to the US, wait. Wallet is US-only for now.
  • If you’re on Cloudflare, open the AI Crawler and Agent access policies and check that “dots, OpenAI” is allowed. It’s one setting.
  • Ask your payment or fraud provider two questions: do you read the Forwarded header, and how do you treat ChatGPT Wallet orders?
  • Don’t store the token for reuse, and if you sell subscriptions, collect consent for recurring charges the way you already do.
  • Treat agent orders as customer orders for support, refunds and disputes.

Nothing here needs new code. The part that decides whether you get these sales is the security you already run, and it’s worth knowing what it does with a shopper who arrives through a cloud browser.

Written by Aman, founder of Elytron Labs: Pollen (agent commerce readiness) and DripSync (AI product image sync).

Leave a comment

Your email stays private. First-time comments are held for review.