OpenAI began rolling out ChatGPT Wallet on November 13, giving its Dots agents a way to complete online purchases after a user reviews and approves each order. The launch is limited to U.S. ChatGPT Pro subscribers who are at least 18 and have an eligible U.S.-issued credit card.
The feature closes a gap between asking an AI agent to find a product and actually paying for it. A Dot can navigate a merchant’s existing checkout, while Wallet supplies a tokenized payment credential instead of exposing the card stored by the user. The current version still requires a biometric check for each purchase. It is not a standing license for a Dot to spend whenever it chooses.
Who can use ChatGPT Wallet now
Wallet works only inside conversations with a Dot, OpenAI’s persistent agent product. It is not available in ordinary ChatGPT conversations, ChatGPT Work or standalone Codex threads, according to the company’s Wallet support documentation.
The launch requirements are narrow:
- A ChatGPT Pro subscription
- Residence in the United States and a U.S. billing address
- Age 18 or older
- An eligible U.S.-issued American Express, Chase, Mastercard or Visa credit card
- A supported device that can complete biometric verification
Debit cards and user-created virtual cards are not supported at launch. Chase customers must be the primary cardholder, rather than an authorized user, and may have to approve enrollment through the Chase mobile app. Banks can also require their own verification before a card is added.
How a Dot completes a purchase
Card enrollment and purchase approval are separate steps. The user adds a card through a secure form in Wallet settings or from a Dot conversation. Full card details go to OpenAI’s payment service provider; OpenAI’s Wallet Privacy Notice says the company receives a tokenized credential plus limited information such as the card network, issuer, type, last four digits, expiration date and eligibility signals. It does not receive the full card number or security code.
When the Dot reaches checkout, Wallet shows an approval request. The user should verify the merchant, items, total, selected card, delivery information and any recurring-payment language before approving with Face ID, Touch ID or another supported biometric check.
After approval, Wallet generates a substitute card number, security code and expiration date for the checkout. The merchant does not receive the number printed on the user’s physical card, and the Dot does not need to handle that number. OpenAI describes the credential as a payment token generated for each use.
A successful biometric check is not the same as a confirmed order. The merchant can still reject the transaction, its fraud system can flag the agent, or the checkout can fail after a pending charge appears. OpenAI advises users to check for a merchant confirmation before trying the transaction again.
The approval screen deserves close attention
Wallet’s biometric step verifies that the account holder approved the transaction displayed on the device. It does not independently establish that the product description is accurate, the seller is trustworthy or the agent selected the best option.
Recurring purchases also need extra scrutiny. A merchant may store the substitute credential and charge it again under the subscription or continuous-payment terms accepted by the user. Removing the card from ChatGPT Wallet later does not cancel an order, subscription or recurring charge already authorized with the merchant.
For the first purchases, users should treat the approval card like a checkout page they assembled themselves:
- Compare the merchant domain with the company you intended to buy from.
- Read the item name, quantity, price, tax and shipping details.
- Look specifically for trial, subscription and automatic-renewal terms.
- Use a card with transaction alerts enabled.
- Wait for the merchant’s confirmation before retrying a stalled checkout.
- Keep the merchant receipt and the Wallet approval record.
OpenAI keeps more than a payment token
Tokenization limits exposure of the underlying card number, but Wallet still creates a detailed transaction record. The privacy notice lists contact and delivery information; merchant, item, amount, tax, fee, discount and shipping data; authorization, fulfillment, cancellation, refund and chargeback status; the user’s approval or rejection; and the device, time and authentication result associated with the action.
OpenAI also collects security and fraud signals such as IP address, browser and app details, device identifiers, approximate location, passkey assertions and information about suspected misuse. The company says it does not sell Wallet information or share it for cross-context behavioral advertising, though merchants, issuers, networks and their providers process information under their own policies.
Removing a card does not immediately erase every Wallet record. OpenAI says credentials may remain for a limited period to finish pending transactions, deactivate the token, prevent fraud or meet legal requirements. Other transaction information is retained as reasonably necessary for the purposes described in the notice.
Who handles a bad order or disputed charge
Wallet does not make OpenAI the merchant, bank or card issuer. If an item is late, defective, canceled or needs to be returned, the merchant remains the first point of contact. The card issuer handles declined, pending, disputed or unrecognized charges. OpenAI Support is the route for a Wallet malfunction, suspected ChatGPT account compromise or a purchase that differs from what appeared on the approval screen.
The Wallet terms contain a broad liability disclaimer and direct users toward merchants, issuers, networks and other providers for most purchase and payment disputes. Existing cardholder rights still apply where they cannot be waived, and OpenAI’s launch announcement says users retain their card rewards and protections for eligible disputes with businesses.
Why this rollout differs from ChatGPT’s earlier checkout
OpenAI’s previous Instant Checkout product depended on participating merchants and was retired in March. The Associated Press reported that it charged merchants 4% of a transaction, limiting adoption. The newer card-network approach is designed to work with merchants’ existing websites and checkout systems rather than requiring every seller to adopt a ChatGPT-native checkout.
That broader compatibility is not automatic. OpenAI’s merchant guidance tells businesses to make product information machine-readable, recognize signed agent requests through Web Bot Auth and check whether fraud controls are rejecting legitimate agent purchases. Payment tokens can fit existing card forms, but bot defenses, outdated checkout flows and risk engines can still stop the order.
OpenAI is working with American Express, Mastercard and Visa, along with fraud providers including Forter, Riskified, Sardine and Signifyd and payment companies such as Adyen, Checkout.com and Stripe. In May, Visa described the underlying model as a way for agents to transact at merchants that already accept its cards, while keeping payment authorization and fraud monitoring in the card network. The Associated Press reported that the networks expect human approval to remain central during the early phase.
Fully delegated spending comes later
OpenAI says it eventually wants users to set spending limits, approved purchase categories and time windows, then pre-authorize an agent to buy within those boundaries. That is a future direction, not the behavior most users receive in this rollout.
For now, ChatGPT Wallet removes the need to type a card number into an agent-run checkout, but it does not remove the human decision at the end. Its most important control is still the moment when the user reads the transaction and decides whether to approve it.
Featured image: Bogdan Hoyaux / European Commission, via Wikimedia Commons, licensed under CC BY 4.0.
