The claim
On 13 November OpenAI launched ChatGPT Wallet, a way for agents in ChatGPT to complete purchases with the user’s approval. OpenAI says agents pay without access to the user’s actual card details, every purchase needs a security check, and existing card protections for eligible disputes still apply. It is built with American Express, Mastercard, and Visa, and starts through dots for ChatGPT Pro subscribers in the US (OpenAI, vendor; TechCrunch, independent).
For merchants, the line that matters is this one: existing checkout pages should work without a Wallet-specific integration (OpenAI, vendor). That is true for the payment. It is not automatically true for the visit.
What reaches your store
The agent shops through ChatGPT’s cloud browser. In the same announcement, OpenAI lists what merchants can do to make these purchases reliable (OpenAI, vendor):
- Allow verified ChatGPT cloud-browser requests using Web Bot Auth, a signed-request standard.
- Configure fraud systems to recognise legitimate agent purchases and the relevant
Forwardedheader signals. - Build an MCP plugin for product discovery, availability, carts, and checkout.
- Return a
continue_urlwhen a transaction has to move from the plugin into the browser.
Read together, OpenAI is telling you where the purchase can fail: at the bot layer and at the fraud layer, before the payment ever runs.
Where the purchase can stop
An agent checkout completes only if every layer lets it through. No integration is needed for the last layer. The first two are yours.
| Layer | What can stop the agent | Check | Owner |
|---|---|---|---|
| Bot and edge rules | A challenge, CAPTCHA, or headless-browser rule meets the cloud browser first | Does your CDN or WAF verify Web Bot Auth signatures, or does it only match IPs and user agents? | Platform or security engineering |
| Fraud screening | A new device, a new IP range, and a fast session look like account takeover | Do your fraud rules see the Forwarded signals OpenAI names, and what score does a test agent order get? | Fraud and payments |
| Checkout flow | Steps a browser agent cannot finish without the shopper | Can a guest checkout run end to end in a fresh browser session? | E-commerce engineering |
| Payment | Card network checks | OpenAI says no Wallet-specific integration is needed here | Payments provider |
The result: “works without integration” holds for a store whose defences treat a verified agent like a shopper. A store tuned hard against automated traffic can turn away exactly the buyer it wants, and the shopper only sees that the agent could not finish.
On Salesforce B2C Commerce
Salesforce’s bot management guide for B2C Commerce describes eCDN controls: custom firewall rules, Managed Challenge, rate limiting, and Under Attack mode, which presents a CAPTCHA to every unique user before they see the storefront (Salesforce, vendor). For legitimate automated traffic, the guide describes allowlisting by IP. It does not describe Web Bot Auth or signed agents.
So the question for a Commerce Cloud team is concrete: if a flash-sale rule or Under Attack mode is on, how does a verified ChatGPT agent get through? Ask your Salesforce account team before you widen an IP allowlist, and keep any change in log or monitor mode first, as the same guide recommends for new rules.
Where this breaks
- Volume is small for now. Pro subscribers in the US, through dots. Blocking a few agent orders this month costs little. The point is to find out before the rollout widens.
- Signatures, not strings. Allowing traffic because it claims to be ChatGPT invites anyone to claim it. Verify the signature or do not allow it.
- We did not read the merchant guides in full. OpenAI’s announcement page and its allowlisting help article were unreadable from our environment; the steps above come from OpenAI’s community announcement.
- Disputes. OpenAI says existing protections apply to eligible disputes. It does not say how a merchant should treat an agent purchase in a chargeback. Ask your acquirer.
Five steps before the rollout widens
- Step 1. Place a test order with an agent. Use a Pro account through dots against a low-value product. Record where it stopped, if it stopped. Owner: e-commerce engineering.
- Step 2. Read your edge rules. List every challenge, CAPTCHA, and headless-browser rule in front of product, cart, and checkout pages, and whether it can verify Web Bot Auth. Owner: platform or security engineering.
- Step 3. Score a test agent order in your fraud tool. Check whether it sees the
Forwardedsignals and what decision it returns. Owner: fraud and payments. - Step 4. Decide on a plugin. An MCP plugin for discovery, availability, carts, and checkout is optional. Build it only if agent orders become a channel worth owning. Owner: head of e-commerce.
- Step 5. Write the policy. Which agents you allow, how they are verified, and who signs off a change to the rule. Owner: CISO with the head of e-commerce.
Missing
- OpenAI’s merchant documentation read in full: the Commerce Partner Playbook and the allowlisting article.
- Whether any CDN or WAF in front of B2C Commerce verifies Web Bot Auth today.
- Spending limits, transaction caps, and enterprise controls for Wallet. The announcement does not mention them.
- A Prestanda test. We have not placed an agent order for this note.
Frequently asked questions
Do we need to integrate with ChatGPT Wallet to accept agent purchases?
OpenAI says existing checkout pages should work without a Wallet-specific integration. Its guidance still asks merchants to let verified ChatGPT cloud-browser requests through and to tune fraud systems for legitimate agent purchases, so the work moves to your bot and fraud rules.
Does the agent see the shopper's card number?
No, according to OpenAI. It describes Wallet as letting agents pay without access to the user's actual card details, with a security check for every purchase, built with American Express, Mastercard, and Visa.
Who can use ChatGPT Wallet today?
OpenAI says it is initially available through dots for ChatGPT Pro subscribers in the US. Volume will be small at first, which makes this the cheap moment to test your checkout with an agent.
Living page. Last updated 14 Nov 2026. We update this note when OpenAI widens the rollout, publishes merchant controls, or we run Step 1 ourselves. Want a second pair of eyes on your storefront rules? Talk to us.