OpenAI Gives ChatGPT Dots a Wallet for Approved Purchases
ChatGPT Wallet lets eligible U.S. Pro users authorize purchases through their dots using linked payment cards. OpenAI's launch guidance requires purchase review and biometric approval.
Last updated

OpenAI's ChatGPT Wallet lets eligible users have their dots complete approved purchases.
The feature connects an AI assistant's shopping work to a payment card. OpenAI's launch instructions describe a review-and-approve process, with biometric verification before checkout continues. For people following AI payments, the development makes the handoff from finding an item to paying for it more concrete.
How the purchase works
OpenAI says Wallet is available to U.S. Pro users with eligible U.S.-issued American Express, Chase, Mastercard and Visa cards. Users must be adults with a U.S. billing address. The feature works in conversations with a dot; the help page says it is unavailable in Chat, Work and standalone Codex threads.
A user adds a card through a secure form, then checks a purchase request before approving it with a supported biometric method such as Face ID or Touch ID. The dot can continue checkout after approval. A merchant confirmation is still needed to establish that an order actually went through.
This separates permission to use a card from permission to buy a particular item. Saving payment details makes future checkout possible, but the documented launch flow still asks the customer to review the transaction. That approval step is central to understanding what the agent is being allowed to do.
A card payment behind the conversation
Wallet uses a substitute payment credential linked to the customer's card. The number used at checkout can differ from the number on the physical card. In this context, tokenization refers to protecting card credentials; it does not establish a cryptocurrency payment or a blockchain transaction.
OpenAI's terms say Wallet does not create a bank account or stored balance, extend credit or hold the customer's purchase funds. The card issuer decides whether to authorize the charge, and the merchant decides whether to accept and fulfil the order.
The terms also require a new approval if a material purchase detail changes before submission. That matters when an assistant encounters a different final price, delivery arrangement or other significant term during checkout. The initial request should not become open-ended permission to accept whatever appears later.
Payment privacy still involves transaction data
OpenAI's Wallet privacy notice says the card service provider collects the full card details through the secure form. OpenAI receives a tokenized credential and limited information about the card, rather than the full credit-card number or security code.
The company still collects purchase and activity records, including merchant details, amounts, order information and whether a payment action was approved or rejected. Its notice also describes sharing information needed for checkout with merchants, payment providers, issuers and networks.
OpenAI says it does not sell Wallet information or share it for targeted advertising. Merchants and payment companies can have their own privacy terms. Using a substitute card number therefore protects one category of sensitive information without making the wider purchase anonymous.
That is a useful distinction for AI commerce. An assistant needs enough information to carry out the order and establish what the customer authorized. Keeping an approval record can help investigate a disputed action, while the information shared to fulfil an order still deserves the same attention as any online purchase.
What this means for agent payments
The practical change is that a conversational assistant can move further into a purchase workflow while using existing card infrastructure. That gives AI commerce a route to checkout without requiring shoppers to fund a new cryptocurrency wallet first.
For crypto investors, it is evidence that agent payments can develop through several payment systems. This announcement does not identify a token that must be bought to use the feature, nor does it establish new demand for a particular blockchain.
The user experience will depend on whether the assistant can complete the intended order reliably and keep the approval clear. Finding the right product, submitting the correct purchase and receiving confirmation remain separate steps. Wallet connects them more closely, but the documented launch process keeps the customer involved at the point of payment.

