Skip to content
CrawlfolioSourced research on web data for AI
Menu

Explainer

ChatGPT Wallet is live. Will sites let your agent check out?

ChatGPT Wallet lets OpenAI's own agents pay on merchant sites. How sites spot them, what your agent needs to get in, and why I'd leave payment to humans.

Corner of a white marble slab with grey veins and a thin gold edge, pointing up into a dark blue-black background
Photo: Ambitious Studio* | Rick Barrett / Unsplash · Unsplash License

OpenAI’s ChatGPT Wallet started rolling out on November 13, 2026, per news coverage, and lets OpenAI’s own agents, called dots, pay on merchants’ sites. Cointelegraph. If you build a different agent, you have two decisions: what it needs so those same sites let it in, and whether it should touch payment at all.

My answer, as of November 16, 2026: give your agent a signed, registered identity, and hand the pay step back to the person. This is research on public docs and terms, not legal advice.

Short on time?

Short on time? Here's my take.

You're building a shopping or checkout agent at scale
Your own Web Bot Auth key, then Cloudflare's Bot Submission Form
It's the documented route to a named, allowable identity. High confidence on the route; Cloudflare publishes no review time.
You want signing without running key infrastructure
AgentCore Browser if you're on AWS, otherwise Browserbase
Both sign requests for you. AgentCore's signing is in Preview and names five bot vendors; Browserbase's is a beta by request. Medium confidence: docs only.
Your agent needs to pay
Hand the final pay step to the human
Deep-link to the merchant's checkout. Don't store or type card numbers. OpenAI itself requires approval for every purchase, and Wallet is OpenAI-only.
You run a store
Allow only verified ChatGPT agent signatures
Use OpenAI's per-vendor steps for Cloudflare, Akamai, HUMAN or Vercel, and keep your fraud rules running separately.

Prices verified . Sponsors cannot buy a verdict or a position.

What is ChatGPT Wallet, exactly? #

A payment step for OpenAI’s own agents, called dots. OpenAI says Wallet “begins rolling out today” in dots, for ChatGPT Pro users aged 18 or older in the US with eligible US-issued cards. OpenAI. The page carries no date; Cointelegraph and 9to5Mac both put the launch on November 13.

Before each purchase, you review the items, total and card, then approve with a security check such as Face ID or a fingerprint scan. Each approval creates a record. The card network issues “a payment token” that stands in for the card, and Wallet doesn’t share card details with the business or the agent.

Here’s what OpenAI announced, in one table.

What OpenAI announcedVerified
TopicWhat OpenAI says
Launch"Begins rolling out today"; November 13, 2026 per news coverage
Who can use itChatGPT Pro, 18+, US, eligible US-issued cards
Where it worksInside dots, OpenAI's own agents
ApprovalReview items, total and card; approve with a check such as Face ID or fingerprint; each approval creates a record
Card detailsNetwork issues "a payment token"; card details not shared with the business or agent
Card networksAmerican Express, Mastercard, Visa
Fraud partnersForter, Riskified, Sardine, Signifyd
Payment processorsAdyen, Checkout.com, Stripe
Merchant's roleKeeps pricing, fulfilment, returns and service; users buy directly from the business
Not live yetDelegated purchases with spending caps, categories or time periods, expected "over time"

Source: OpenAI announcement (read via a reader service), Cointelegraph and 9to5Mac. All read 16 Nov 2026. Scroll sideways for more columns.

The purchase happens on the merchant’s own site. OpenAI says “Browser access does not require a plugin or product feed”, and its browser-access guide says the cloud browser “can use your existing purchase or booking flow”.

One naming trap: an OpenAI help article with “wallet balance” in its URL describes a USD account balance for ChatGPT purchases. OpenAI Help. That’s a different feature from the agent Wallet.

How do sites recognize the ChatGPT agent? #

By signature, not by user agent. OpenAI’s Agent Access page says its signed cloud-browser requests use Web Bot Auth (RFC 9421), with Signature, Signature-Input and Signature-Agent: "https://chatgpt.com" headers. The public keys sit at https://chatgpt.com/.well-known/http-message-signatures-directory.

That guidance covers signed cloud-browser requests, not web crawlers. Whatever you’ve decided about GPTBot in robots.txt is a separate question.

OpenAI then tells merchants where its agent already appears in each major bot manager:

Bot manager How the ChatGPT agent is listed What OpenAI tells merchants to do
Cloudflare Personal Agents entry “dots, OpenAI” Set it to Allow, or write a WAF rule on detection ID 129220581 (tag chatgpt-agent)
Akamai Verified Bots entry “ChatGPT Agent” Allow it
HUMAN Sightline “ChatGPT Agent” Allow it
Vercel Existing “ChatGPT Agent” entry, identified as chatgpt-operator Nothing extra, unless your own rules block it

Source: OpenAI Agent Access, verified 2026-11-16.

OpenAI asks merchants to allowlist only requests whose signatures they’ve verified and to keep their other controls on. Its help article adds that any proxy in front of the site must pass the three signature headers through. One merchant brief puts the reason plainly: “a user agent string alone proves nothing”. BERI.

OpenAI also admits some sites “may unintentionally block” Wallet purchases, and asks businesses to check they aren’t “inadvertently blocking” ChatGPT agents. Its commerce docs index lists the Agent Access page to “Help prevent unintended blocks of verified ChatGPT browser visits”.

What does your own agent need to get through? #

The same kind of identity, which you build and register yourself. OpenAI’s agent arrives signed and pre-named in the big bot managers. An unsigned third-party agent gives a merchant nothing comparable to allow.

Cloudflare’s Web Bot Auth docs, last updated October 8, 2026, set out the route:

  1. Generate an Ed25519 key pair.
  2. Publish your public keys as a JWKS at /.well-known/http-message-signatures-directory, over HTTPS.
  3. Sign each request and send Signature, Signature-Input and Signature-Agent. The last must be a double-quoted https URL.
  4. Check your setup at crawltest.com/cdn-cgi/web-bot-auth.
  5. Register in the dashboard’s Bot Submission Form with the Verification Method “Request Signature”.

Since July 1, 2026, signed agents sit inside Cloudflare’s Verified status, with a field marking each one as Direct or Intermediary. The requirements are honest identification (Web Bot Auth, an IP list or reverse DNS) and non-abusive behaviour, so Web Bot Auth itself isn’t mandatory. Submissions show Waiting For Review, Accepted, Rejected or Cancelled, and no review time is published. Signed agents docs.

Identity matters more since November 4, when Cloudflare gave sites a per-agent choice for personal assistants: “Allow (do not block)”, “Block on pages with ads” or “Block”. Cloudflare. A site can now single out one named agent. My post on Cloudflare’s per-agent controls covers that change, and the AI crawler categories explainer covers the buckets underneath.

OpenAI has a head start here. ChatGPT agent was in Cloudflare’s first signed-agents cohort in August 2025, alongside Goose from Block, Browserbase and Anchor Browser. Cloudflare, 2025.

Don’t copy ChatGPT’s user agent or Signature-Agent value. Merchants are told to allow only verified signatures, so a borrowed header gets you nothing and misrepresents who you are.

Sunlight falling across a pale veined marble floor, with broad diagonal shadows cutting it into bright and shaded bands
Light shows the stone and shade hides it: a signed, registered agent gives a site something it can see and check, while an unsigned one stays in the shadow. Photo: Augustine Wong / Unsplash · Unsplash License

Which browser layers sign for you today? #

I found two with documented Web Bot Auth support, and both are early access.

Browser layer Status (verified 2026-11-16) Bot vendors it names Caveat in its own docs
AWS AgentCore Browser Preview; off by default Cloudflare, HUMAN Security, Akamai, DataDome, F5 “Not all websites will recognize or allow signed agent traffic”
Browserbase Beta, by access request None named on its identity page; it was in Cloudflare’s first signed-agents cohort (2025) “A valid signature doesn’t grant access or sign your agent into a user account”

On AgentCore you turn signing on with browserSigning {enabled: true}. If you’re already on AWS, that’s the shorter path; otherwise request Browserbase’s beta. My cloud browser roundup and Browserbase alternatives cover the wider choice.

Both caveats say the same thing: a signature tells the site who you are, and the site still decides.

Should your agent handle payment at all? #

I’d say no. OpenAI, with network tokens and biometric approval, still makes the person approve every purchase, and its Agent Access page requires “human review before any consequential action”. OpenAI Agent Access. It also says it doesn’t yet have features that let site owners control which actions users take.

Wallet’s tokens are OpenAI-only. I found no API or programme that lets another company’s agent use them. A third-party agent that types a stored card number into checkout has no equivalent token or approval step in anything I read.

The sources disagree in three places, and I went with OpenAI’s own wording each time:

  • Payments at launch. OpenAI’s undated help article says “Cloud browser cannot sign in to websites or complete payments”, while the Wallet announcement has dots completing purchases. I trust the announcement and treat the help line as stale.
  • The token. BERI calls it a “single-use network token”; OpenAI says only “a payment token”, and PPC Land notes OpenAI hasn’t said whether it can be reused.
  • Price and cards. One merchant explainer states a Pro price and card restrictions I couldn’t find on any OpenAI page, so I left them out.

Delegated purchases with spending caps are coming “over time”, per OpenAI. They aren’t live, so plan as if every payment needs a person.

Close-up of white marble crossed by dark grey veins that branch, split and rejoin in a loose web
The fine veins wander across the slab but keep running into one dark line; however many steps your agent automates, the payment step should still lead back to the person. Photo: Content Pixie / Unsplash · Unsplash License

What I would do #

If I were shipping an agent that touches shopping pages this month:

  • Ship identity before checkout features. Publish a key directory and apply through Cloudflare’s Bot Submission Form, or build on a browser layer that signs.
  • Never borrow ChatGPT’s identity or spoof any user agent.
  • Stop at the pay step. Deep-link the person to the merchant’s checkout and let them pay; don’t store or type card numbers.
  • Log which sites block you, and route those tasks to an API or back to the user. My search vs fetch vs browser guide covers when a browser is the wrong tool anyway.
  • If you run a store, follow OpenAI’s per-vendor Allow steps, accept only verified signatures and keep fraud scoring separate.

If you’re still choosing an agent framework, Browser Use vs Stagehand compares two of them, and the agent browsers pillar maps the rest.

What I couldn't verify (as of November 16, 2026)

  • OpenAI’s pages, first-hand. openai.com and help.openai.com returned 403, so I read them through a reader service.
  • A third-party route into Wallet. Nothing found, and no stated plan.
  • Cloudflare review times for signed-agent submissions.
  • Other bot vendors and your key. Whether Akamai, HUMAN, DataDome or F5 accept arbitrary third-party Web Bot Auth keys.
  • Pro pricing and card limits reported by one explainer.

FAQ

Can my own AI agent use ChatGPT Wallet?

No, not as of November 16, 2026. OpenAI describes Wallet as working inside dots, its own agents, and I found no API or programme that lets another company's agent use Wallet's payment tokens.

Do merchants need to integrate anything for ChatGPT Wallet?

Not a Wallet-specific integration. OpenAI says 'Browser access does not require a plugin or product feed'. It asks businesses to let verified ChatGPT agent signatures through their CDN or bot manager. Product feeds are a separate, optional guide in its commerce docs.

What is Web Bot Auth?

A way for bots and agents to sign their HTTP requests, built on RFC 9421. The agent sends Signature, Signature-Input and Signature-Agent headers and publishes its public keys at /.well-known/http-message-signatures-directory, so a site can check who sent the request.

Will signing my agent's requests guarantee access?

No. AWS says 'Not all websites will recognize or allow signed agent traffic', and Browserbase says a valid signature doesn't grant access. The site's own policy still decides, and on Cloudflare a site can now block a named agent.

Does blocking GPTBot in robots.txt block ChatGPT Wallet purchases?

They're separate systems. OpenAI's Agent Access guidance covers signed cloud-browser requests, not web crawlers like GPTBot, and the BERI merchant brief advises keeping the two decisions apart. Wallet purchases depend on whether your bot manager lets the signed ChatGPT agent in.

Is ChatGPT Wallet available outside the US?

Not at launch. OpenAI says it is rolling out to ChatGPT Pro users aged 18 or older in the US with eligible US-issued cards.

Sources

17 sources, accessed .

Official pricing, docs, changelogs and status pages 12

  1. OpenAI: Introducing ChatGPT Wallet (read via a reader service) openai.com · accessed
  2. OpenAI developers: Agent Access developers.openai.com · accessed
  3. OpenAI developers: Commerce docs index developers.openai.com · accessed
  4. OpenAI developers: Enable browser access developers.openai.com · accessed
  5. OpenAI Help: cloud browser allowlisting (read via a reader service) help.openai.com · accessed
  6. OpenAI Help: ChatGPT balance, a separate feature (read via a reader service) help.openai.com · accessed
  7. Cloudflare docs: Web Bot Auth (updated 2026-10-08) developers.cloudflare.com · accessed
  8. Cloudflare docs: Signed agents (updated 2026-11-12) developers.cloudflare.com · accessed
  9. Cloudflare blog: signed agents (2025-08-28) blog.cloudflare.com · accessed
  10. Cloudflare blog: personal agents visibility and control (2026-11-04) blog.cloudflare.com · accessed
  11. AWS docs: AgentCore Browser Web Bot Auth (Preview) docs.aws.amazon.com · accessed
  12. Browserbase docs: agent identity overview (beta) docs.browserbase.com · accessed

News and press 3

  1. Cointelegraph: OpenAI launches ChatGPT Wallet (2026-11-13) cointelegraph.com · accessed
  2. 9to5Mac: ChatGPT Wallet lets dot agents make purchases (2026-11-13) 9to5mac.com · accessed
  3. PPC Land: OpenAI hands its AI agents a wallet (2026-11-14) ppc.land · accessed

Other blogs 2

  1. BERI: ChatGPT Wallet merchant brief (2026-11-15) beri.net · accessed
  2. eesel AI: ChatGPT Wallet explained for merchants eesel.ai · accessed

What readers say

Used one of the tools in this guide? Tell other readers how it went. I read every review before it goes up, and I never turn one down for being negative. How reviews work.

No reader reviews yet. Yours could be the first.

Write a review
Your rating

What did you use it for, what worked, and what didn't? 30 to 1500 characters. Please don't include links.

Your connection to the company

Your review appears with the name you enter, after I approve it. I don't ask for your email. Privacy.