OpenAI launched ChatGPT Wallet on 13 November 2026, giving its agents in ChatGPT Work, Codex and dots a way to pay for things with the user’s approval. The agent buys through the merchant’s existing checkout, with no integration needed, so an ecommerce brand only gets the sale if its firewall and fraud settings let the agent through.
Key takeaways
- OpenAI announced ChatGPT Wallet on 13 November 2026 as a way for agents in ChatGPT Work, Codex and dots to complete purchases with user approval.
- The customer approves each purchase in ChatGPT, and the merchant’s own checkout processes the payment, so no Wallet-specific integration is required.
- Merchants receive a network token instead of the full card number, with a Payment Account Reference (PAR) linking it to the customer’s account.
- OpenAI says bot detection can block ChatGPT’s cloud browser and cause purchases to fail, and Akamai, Cloudflare, HUMAN and Vercel verify its signed requests automatically.
- OpenAI’s merchant guides don’t say which countries or ChatGPT plans have Wallet, only that it supports payment steps “where available”.
How a Wallet purchase works
OpenAI’s Commerce overview describes the journey in four steps. A customer describes a need, ChatGPT finds options from the public web, private integrations and merchant product feeds, the customer picks one, and the journey moves to browser use or a plugin to finish the transaction. Wallet sits in that last step.
The Accept payments guide is plain about the split of work. The customer reviews and approves the purchase in ChatGPT, and your checkout processes it. Your business still handles orders, fulfilment, customer support and fraud decisions.
| Step | ChatGPT does | Your business does |
|---|---|---|
| Choosing | Finds options from the web, integrations and product feeds | Keeps the product feed and site accurate |
| Checkout | Its cloud browser uses your existing checkout pages | Lets verified agent visits through security tools |
| Approval | The customer approves the purchase in ChatGPT | Nothing extra |
| Payment | Wallet passes a network token, not the card number | Processes it and links the token to the account with the PAR |
| After the sale | Nothing in the guides | Orders, fulfilment, customer support and fraud decisions |
| Repeat billing | Customer consents to one transaction | Never reuses the credential, and gets consent for subscriptions |
Does my checkout need to change?
Your pages don’t, and that is the part a marketing team can miss. Because the agent uses the same forms a person does, every point of friction a human shopper tolerates (a forced account, a CAPTCHA, a bot challenge from your CDN) now sits between ChatGPT and a completed order. OpenAI’s guide says the cloud browser “can trigger bot-detection systems” and cause purchases to fail. A failed agent purchase may not look like a normal abandoned basket in your analytics, so it is easy to miss.
OpenAI is also rolling out a Forwarded header that relays user signals to the merchant. The parameters it lists include the user’s ASN, IP country and prefix, locale, time zone and user agent, which a merchant can use for geographic eligibility, local formatting and fraud scoring. OpenAI says the signals may vary during the rollout and asks merchants to have third-party risk providers ingest them.
What does the agent look like to a firewall?
The Agent access guide says ChatGPT’s cloud browser signs its requests with Web Bot Auth, built on HTTP Message Signatures (RFC 9421), and publishes its public keys at chatgpt.com. Four security vendors verify the signatures automatically.
| Provider | How ChatGPT’s cloud browser appears |
|---|---|
| Cloudflare | ”dots, OpenAI” under Personal Agents, bot tag chatgpt-agent, detection ID 129220581 |
| Akamai | ”ChatGPT Agent” in the AI Fetchers and Agents category |
| HUMAN | ”ChatGPT Agent” in Known Bots & Crawlers and AgenticTrust permissions |
| Vercel | ”ChatGPT Agent”, identified as chatgpt-operator |
OpenAI says an allowlist isn’t required because the cloud browser can already use sites without one. The exception applies site-wide when you add one, so keep page-level access controls, and it doesn’t change how other bots, including OAI-SearchBot, are treated. Your crawler decisions from the shared AI training opt-out stay separate from this one. OpenAI also says it requires human review before any consequential action, such as checkout.
What it means for marketing teams
OpenAI’s other brand launches this autumn were about being found. Businesses in ChatGPT gave brands a profile and a mention count, and dots gave users agents that work in the background. Wallet adds the payment, so the same agent that recommends a product can buy it on your site.
The work this creates sits between teams. The ecommerce manager owns conversion, the security or platform team owns the CDN rules, and the payments or fraud team owns risk scoring, yet none of them has a reason to look at agent traffic unless someone asks. A brand that blocks the agent can lose the order without anyone in marketing noticing. Our coverage of Lightspeed’s study showed smaller retailers already losing out in AI recommendations, so a challenger brand can’t afford to lose the few agent orders it wins.
Our view at Manual Focus is that every ecommerce brand selling into markets where Wallet is live should let verified ChatGPT agent visits through checkout before the Christmas peak, because the agent then shops the site like any customer while page-level controls and fraud checks stay in place. Then agree with finance how a Wallet order will be identified, using the network token and the Forwarded header, before the volume arrives.
Five checks before the Christmas peak
- Ask your security team one question. Do our CDN or bot rules block verified ChatGPT cloud browser visits? On Cloudflare, Akamai, HUMAN or Vercel the answer is a rule to check. Anywhere else it means manual signature verification.
- Walk the checkout as an agent would. List every CAPTCHA, forced sign-up and pop-up between product page and payment. The site audit and refresh playbook gives a structure for logging them.
- Brief your fraud provider. Send them OpenAI’s Accept payments guide and ask them to ingest the
Forwardedheader signals and score network-token orders fairly. - Check the feed and the profile. Wallet only pays for what ChatGPT chose, so claim your Business Hub profile and fix prices and availability in your product feed. Our ChatGPT Ads on Shopify post covers the catalogue route for Shopify merchants.
- Tag the orders. Decide how agent purchases appear in your order system and attribution reports, then add them to your model with the attribution teardown.
What OpenAI hasn’t said
The developer guides don’t give the countries, plans or age limits for Wallet, and they don’t say whether OpenAI takes a fee from merchants. Nothing in them explains how a merchant can tell a Wallet order from a normal card order beyond the token and the header, or how refunds and chargebacks flow back to ChatGPT. OpenAI also says the Forwarded signals may vary during the rollout, so fraud rules built on them now may need revisiting. We don’t yet know how many shoppers will let an agent pay, or whether checkout friction will count against a merchant when ChatGPT picks where to buy.
Further reading
- What OpenAI’s Businesses in ChatGPT means for brand teams, for the profile and product feed ChatGPT draws on before anyone buys
- What OpenAI’s dots and ChatGPT plugins mean for marketing teams, on the agents that now carry a wallet
- What Adobe’s AI shopping forecast means for Black Friday, for the traffic forecast behind the peak
- What the shared AI training opt-out means for brand websites, on the crawler rules that stay separate from agent access
If you want help getting your site and checkout ready for AI shopping agents, our services page explains how we work.
Frequently asked questions
What is ChatGPT Wallet?
ChatGPT Wallet is a payment option OpenAI announced on 13 November 2026 for agents in ChatGPT Work, Codex and dots. The agent completes a purchase on the merchant's own website after the customer approves it in ChatGPT. The merchant's checkout processes the payment and receives a network token instead of the full card number.
Do merchants need to integrate ChatGPT Wallet?
No. OpenAI's Accept payments guide says no Wallet-specific integration is required, because ChatGPT's cloud browser uses a merchant's existing checkout pages and payment forms. OpenAI calls checking cloud browser access optional but says it helps Wallet purchases go through, since bot detection can block the browser and cause purchases to fail.
How do I stop my firewall blocking ChatGPT agents?
OpenAI says ChatGPT's cloud browser signs its requests with Web Bot Auth, and that Akamai, Cloudflare, HUMAN and Vercel verify those signatures automatically. If your security settings block it, allow verified cloud browser visits and keep your other controls. On Cloudflare the traffic appears as dots, OpenAI under Personal Agents. Other providers need manual signature checks.
Can a merchant save the ChatGPT Wallet card for later?
No. OpenAI's guide says the customer consents to one transaction, so a merchant must not reuse or save the credential for a separate purchase. Subscriptions are allowed if the checkout supports recurring billing, with the customer's consent and the processor's practices for merchant-initiated transactions. A merchant's existing card-on-file flow can carry on alongside Wallet.
Sources
From the podcast
James and Hannah talk through ChatGPT Wallet, which OpenAI launched on 13 November 2026 so that its agents in ChatGPT Work, Codex and dots can complete purchases on a merchant’s own checkout once the customer approves. There’s no Wallet-specific integration, so the work lands with whoever runs the site’s bot rules and fraud scoring. They cover how a Wallet purchase works, how ChatGPT’s cloud browser identifies itself to firewalls, why the job sits between ecommerce, platform and payments teams, and three jobs to hand to AI before the Christmas peak.
Get AI on this
Paste these into whichever AI assistant you use. Swap the bracketed parts for your own details. The first needs an assistant that can browse the web, and the other two need file or link uploads.
1. Walk the checkout the way an agent would
I run ecommerce marketing for [brand], which sells [one line on what you sell]
at [website], mainly in [market].
AI agents can now buy on our site through ChatGPT's cloud browser, using our
normal checkout. Any step that blocks an automated browser can lose the sale.
Using web browsing, go through our purchase journey for this product: [product
URL]. Start on the product page and go as far as the payment step without
entering any payment details or placing an order.
Give me a table with the columns: Step | URL | What you had to do | Obstacle
(CAPTCHA, forced account, pop-up, bot challenge, cookie wall, other) | Could
you get past it (yes / no / not tested).
Then list the obstacles in the order I should fix them, with one line on why.
If a page didn't load, or you were blocked before a step, say so and don't
guess what that step looks like.
2. Draft the request to the security team
I need to ask our security or platform team whether our website blocks
verified visits from ChatGPT's cloud browser, which AI agents use to buy on
our site.
Attached is OpenAI's agent access guide for merchants. Our website is
[website] and our CDN or bot protection provider is [provider].
Write a short internal message (under 200 words) to [team or person] that:
1. explains in two sentences why this matters for sales,
2. asks whether verified ChatGPT cloud browser visits are currently blocked,
3. names the exact setting, category or rule to check for [provider], taken
only from the attached guide,
4. asks them to keep page-level access controls in place.
If the guide doesn't cover [provider], say so plainly and list what the guide
says a provider without automatic verification must do instead. Don't invent
setting names.
3. Brief the fraud provider
We sell through [website] and use [fraud or risk provider] for fraud
screening. Orders can now arrive from AI agents paying with ChatGPT Wallet.
Attached is OpenAI's merchant guide to accepting payments with ChatGPT Wallet.
Draft a one-page brief for [fraud or risk provider] that:
- explains what a Wallet order looks like to us, including the network token
and the Payment Account Reference, using only what the guide says,
- lists the user signals OpenAI says it relays in the Forwarded header, and
what the guide suggests each can be used for,
- asks them five specific questions about how they will score these orders and
how we'll tell them apart from other card orders in reporting.
Add a short "Not covered by the guide" section listing anything we'd need to
know that the guide doesn't answer, such as refunds or chargebacks. Don't fill
those gaps with assumptions. Read the episode transcript
James: Picture a shopper asking ChatGPT to buy a carry-on bag, the agent finding yours, and your own firewall turning it away at the checkout. Since the thirteenth of November, when OpenAI launched ChatGPT Wallet, that's a sale you can lose without anyone noticing. I'm James Vickers, this is Manual Focus, and Hannah's with me to work out who in the building needs to hear about it.
Hannah: Hi James. Probably not the people who usually read OpenAI announcements, which is half the problem.
James: Go on then. What is it?
Hannah: OpenAI describes Wallet as a secure way for agents in ChatGPT Work, Codex and dots to complete purchases with the user's approval. Dots, which we covered at the end of September, are the always-on agents OpenAI launched at its DevDay conference. We went through OpenAI's announcement and its merchant guides for developers, and those guides are where the useful detail is.
James: So how does a purchase actually happen?
Hannah: The shopper describes what they need, ChatGPT finds options from the web, from integrations and from merchant product feeds, and the shopper picks one. Then ChatGPT's cloud browser, which is a browser OpenAI runs on its own servers, goes to the merchant's site and uses the normal checkout. The customer approves the purchase inside ChatGPT, and the merchant's checkout processes the payment.
James: So the merchant doesn't build anything.
Hannah: No Wallet-specific integration at all, OpenAI says. The merchant gets a network token instead of the full card number, plus a reference that links it to the customer's account. And the merchant still owns orders, fulfilment, customer support and fraud decisions.
James: That's the part I'd underline for an ecommerce team. No integration sounds like no work, but it really means the work has moved somewhere else.
Hannah: It's moved into security. OpenAI's own guide says the cloud browser can trigger bot-detection systems and cause purchases to fail. So the CAPTCHA, the forced account, the bot challenge from your content delivery network, all of that now sits between the agent and the order.
James: And a failed agent purchase probably doesn't look like an abandoned basket in anyone's report.
Hannah: It may not look like anything. Which is why OpenAI has published a separate guide on agent access.
James: What does the agent look like to a firewall, then?
Hannah: It signs its requests, using a standard called Web Bot Auth, so a site can check the visit really comes from ChatGPT. OpenAI says four security providers verify those signatures automatically, Cloudflare, Akamai, HUMAN and Vercel, and each one labels the traffic. On Cloudflare it shows up as dots, OpenAI, under Personal Agents. Anyone on another provider has to check the signatures by hand.
James: And if a brand opens the door to it, does that open the door to every AI crawler too?
Hannah: No. OpenAI says the exception covers its signed cloud browser visits only, and doesn't change how other bots are treated, including its search crawler. So the training and crawling decisions we covered at the end of October, with the shared opt-out token, stay exactly where they were.
James: So where does this sit in a marketing team? Because I don't think it sits in one.
Hannah: That's my read too. Conversion belongs to ecommerce, the bot rules belong to the platform team, and fraud scoring belongs to payments.
James: Right. And none of them has a reason to look at agent traffic unless somebody asks. Earlier this week we talked about Businesses in ChatGPT, which was about being found and counted. This is the step after, where the same agent can buy. And the Lightspeed study we covered in September had AI assistants picking the big chain over the smaller retailer up to ninety-four per cent of the time, so a challenger brand can't afford to drop the few agent orders it does win.
Hannah: There's a fraud angle as well. OpenAI is rolling out a header that passes along signals about the user, things like their country, locale and time zone, so risk systems can score the order. It says those signals may vary while it rolls out.
James: Our view is simple enough. If you sell where Wallet's live, let verified ChatGPT agent visits through checkout before the Christmas peak, keep your page-level controls and fraud checks, and agree with finance how you'll spot a Wallet order before the volume turns up. So, Hannah, what do we hand to AI?
Hannah: Three jobs, I think.
James: Get AI on this. Walk your own checkout the way an agent would and list every obstacle.
Hannah: Give it your checkout URLs from product page to payment, and an AI that can browse. It hands back each step with every CAPTCHA, forced sign-up and pop-up it hit, and marks the ones it couldn't get past.
James: Get AI on this, too. Write the note to your security team.
Hannah: Give it OpenAI's agent access guide and the name of your security provider, and it drafts a short request asking whether OpenAI's verified cloud browser visits are blocked, with the exact rule to check for that provider.
James: And the third. Brief the fraud provider.
Hannah: Give it OpenAI's payments guide and it writes the brief, what a network token is, which header signals to ingest, and the questions to ask them about how they'll score those orders. The prompts are in the show notes.
James: What don't we know yet?
Hannah: Quite a lot. The developer guides don't say which countries or plans have Wallet, or whether there's an age limit. They don't say whether OpenAI takes a fee from merchants. They don't explain how refunds and chargebacks flow back to ChatGPT, or how a merchant tells a Wallet order from a normal card order beyond the token and that header. And nobody knows yet how many shoppers will let an agent pay.
James: So the takeaway. Your checkout is now a front door for AI agents, and the team holding the key probably isn't marketing, so go and ask them this week. The full article is on manual-focus dot co dot uk. If the show's useful, follow it in Apple Podcasts, Spotify or wherever you listen, and if you'd like a second pair of eyes on your checkout before peak, you can book a free working session with us on the site. Thanks, Hannah.
Hannah: Thanks, James. Go and try to buy something from yourself.