ChatGPT Wallet arrives in dots, with approval for every purchase
OpenAI introduced ChatGPT Wallet on November 13, beginning a rollout in dots for US ChatGPT Pro subscribers aged 18 or older with eligible US-issued cards. It lets an assistant prepare a purchase without requiring the customer to re-enter card details at every checkout. The customer still reviews and approves each purchase.
That last step defines this launch. OpenAI describes advance permission within spending, category and time limits as a future direction, not a capability shipping with Wallet today. The current product is a payment handoff for an assistant-led shopping task, not blanket permission to spend.
Who can use ChatGPT Wallet
The Wallet help page narrows the access requirements: a US billing address is required, and purchases work in dot conversations, not Chat, Work or standalone Codex. It lists eligible American Express, Chase, Mastercard and Visa cards. Chase users must be the primary cardholder rather than an authorized user. Availability is rolling out, so eligibility does not mean the feature will appear immediately.
Wallet is separate from the payment method used for a ChatGPT subscription. Virtual cards are not supported as saved cards at launch. That restriction concerns the card a customer adds, not the network token generated for an approved purchase.
What approval does, and what it does not
OpenAI says the approval flow displays the items, total and selected card, followed by a security check for each purchase. Its network partners supply a substitute payment credential rather than exposing the underlying card details to the agent or business.
The help page also makes an important distinction: “Ready to check out” means approval is complete, not that a merchant has confirmed an order. If the result is unclear, check the merchant’s confirmation before trying again. Removing a card from Wallet does not cancel a merchant subscription.
The Wallet terms leave acceptance and fulfillment with the merchant. A card, credential or transaction can still be rejected. OpenAI is not the seller, bank or card issuer, and does not hold purchase funds. Merchant terms govern the order, including shipping, returns and warranties.
That division matters after checkout. Order problems and refund requests go to the merchant; billing errors or unauthorized charges go to the issuer. Existing cardholder agreements and network rules still govern fees, rewards and dispute rights. Approval in ChatGPT is one stage of the transaction, not a replacement for those relationships.
Tokenization does not mean no transaction data
The Wallet privacy notice says a service provider collects card details through a secure form. OpenAI receives a tokenized credential and limited card information, not the full card number or security code.
It also describes collection of purchase details, contact and delivery information, approval records, device information and fraud signals. Information needed to place and fulfill a purchase is shared with merchants and their providers. Some records can remain after a card is removed for pending transactions, fraud prevention or legal obligations. Tokenization limits exposure of the original card credential; it is not a promise that shopping activity leaves no records.
Merchants can use existing checkout pages
OpenAI’s payment documentation says Wallet works with existing checkout pages without a Wallet-specific integration. The business keeps its checkout, fulfillment, support and fraud decisions. Existing authorized card-on-file flows can remain available as a separate option.
Compatibility is still practical, not universal. The documentation warns that risk systems can mistake the cloud browser for unwanted bot traffic. OpenAI is rolling out user signals through the Forwarded header to help risk providers assess those requests; the signals available can vary during rollout.
Merchants are told not to save or reuse the payment credential for a separate purchase. Recurring billing is supported when the existing checkout supports it and the customer consents to those recurring charges. A customer approving a subscription is therefore different from giving an assistant open-ended authority to place new orders.
The broader Commerce Partner Playbook separates product discovery, browser checkout and structured plugin actions. Product feeds can help discovery, while plugins expose supported operations to an assistant. Those are distinct integration choices, rather than prerequisites for every Wallet payment.
This builds on the permission questions covered in Amex’s Intent Intelligence framework: identifying an agent and authorizing a particular purchase are different checks. For users evaluating Wallet now, the useful boundary is concrete: inspect the proposed purchase, approve that transaction, then look for the merchant’s confirmed outcome.
Editorial illustration by ByteForward. OpenAI wordmark belongs to OpenAI. Independent coverage, not affiliated with or endorsed by OpenAI.
