ChatGPT Wallet: ChatGPT agents can now pay with a token and your Face ID (US only)
ChatGPT Wallet lets ChatGPT agents pay on your behalf without ever seeing your card: the network issues a token for that single purchase and you approve with Face ID or a fingerprint. US only, ChatGPT Pro only.
What ChatGPT Wallet is, and what it is not
OpenAI introduced ChatGPT Wallet on Friday, November 13, 2026, in partnership with American Express, Mastercard and Visa. It describes it as the first wallet that lets agents pay without access to real card data and that requires a security check on every purchase, while keeping the rewards and dispute protections the user already had.
A token per purchase, not a balance or an account
OpenAI's terms are explicit: Wallet does not create a bank account or a stored balance, does not extend credit and does not move funds. It is not a bank, not a stablecoin, and it does not change the relationship with your card issuer. One clarification in case the name misleads you: it has nothing to do with the token wallet that will merge the ChatGPT and Codex allowance in December. That is consumption billing; this is a payment credential.
Who can use it today: Pro, the US, 18 and over
The rollout starts with ChatGPT Pro subscribers, 18 or older, in the United States, holding an eligible card issued in the US with a US billing address. It is gradual and OpenAI gave no date for expanding it. If you are in Chile, Spain or anywhere else, it does not apply yet.
Read also
How a purchase works, step by step
The agent builds the order, you approve with Face ID or a fingerprint
You add the card once. After that, on every purchase, the agent builds the order and Wallet shows you four things before closing: merchant, items, total amount and the selected card. You approve with biometric verification, Face ID or a fingerprint. The terms allow you to give ChatGPT authority to approve in advance, but that is an option you switch on, not the default behavior.
The token rides the checkout the merchant already has
After approval, the card network generates a payment token with substitute data valid for that purchase, and the agent sends it through the merchant's existing checkout system. The merchant never sees the real number. According to OpenAI's commerce guide, ChatGPT Wallet works out of the box with existing checkout pages and payment forms: no Wallet-specific integration is required.
What changes if you run a store
No new integration, but two jobs: do not block it, do support it
Nothing to code does not mean nothing to do. The first job is not breaking it: risk systems that mistake ChatGPT's cloud browser for a bot make these purchases fail. The second is owning support: refunds, returns and customer service stay with the merchant, and so does your own fraud stack. The token changes who knows the card number, not who answers when something goes wrong.
Read also
When fraud tooling mistakes the agent for a bot
The friction is already documented and it is the most actionable part of the announcement: agent purchases fail when a merchant's risk system classifies the cloud browser as automated traffic. If you sell online and you are seeing agent traffic, the test that matters this week is a real purchase from an agent, not a click-through on your laptop. For the broader picture, the guide on how to block or allow AI agents on your site covers signatures, robots and Nginx rules.
What changes if you build agents
Approval as a required state in the flow
The pattern taking hold is not "card stored in the prompt" but a single-use token with limits. That forces you to model approval as a state in the flow rather than an optional screen: the agent builds, waits, gets the green light and only then pays. Anyone shipping agents that buy things needs to pause and resume, and to record what was approved.
Where this fits: agentic checkout, x402 and the other protocols
Wallet is the payment credential layer, not the checkout. Agentic checkout already has parts: the Agentic Commerce Protocol OpenAI opened with Stripe, whose delegated payment is single-use and bounded, Google's Universal Commerce Protocol and x402 for machine-to-machine payments. Wallet's difference is that it asks the merchant to change nothing: it arrives as traffic, not as an SDK.
The limits left open
Refunds, disputes and who answers when something goes wrong
If an agentic purchase goes wrong, the merchant handles the refund and the dispute stays with the card issuer, exactly as today. What is still undefined is the experience: who tells the user what their agent ordered, and how easily it can be undone. That part is not written in any guide yet.
Pricing, fees and a rollout date: what OpenAI did not say
The announcement carries no published fee for Wallet and no date for leaving the United States. There is also no detail on how it will behave with merchants that do not accept the cloud browser. Any commission figure circulating belongs to other agentic commerce products and should be attributed before it is repeated. This week made the contrast obvious: the same day OpenAI opened a wallet, United shut the door on AI agents on its site. Same problem, two opposite answers.
Conclusion
ChatGPT Wallet does not make AI buy on its own: it makes approval a required step and keeps the card number from traveling to the merchant. If you run a store, this week's job is testing your checkout against agent traffic; if you build agents, it is modeling the single-use token. The context for the `dots` that debut the wallet is in the DevDay 2026 recap.


