OpenAI is introducing ChatGPT Wallet for shopping through dot, its agentic checkout experience. The idea is to let an agent assemble a cart and prepare checkout while a person uses a saved payment method. The important boundary in the initial product is that the person still reviews and approves the purchase; a tokenized card credential handles the payment handoff after that approval.
The rollout is limited: OpenAI describes access for ChatGPT Pro subscribers in the United States, and its Help Center says availability is gradual. Users must meet Wallet eligibility requirements, including being an adult with an eligible US account and card. Wallet works in dot conversations, not in ChatGPT, Work, or standalone Codex. It is not a promise that every merchant or checkout flow will work.
What happens between the cart and the charge?
In the current Help Center flow, dot presents the merchant, items, total, payment card and any recurring-charge terms for review. The user approves and completes a biometric check on a supported device. Only then does checkout proceed. The payment network supplies a tokenized credential for the transaction in place of sending the physical card number as the checkout credential. This reduces exposure of the card number at the merchant checkout; it does not make the transaction anonymous or remove the need to protect the account and device.
OpenAI’s terms and privacy notice add an important detail: the payment provider collects card details through a secure form. OpenAI says it receives a token and limited card information such as network, issuer, card type and last four digits, rather than the full number or security code. The merchant still needs information to place and fulfill the order, which can include contact, billing and shipping details, order contents and the payment credential. OpenAI also describes transaction and fraud-prevention data flows. Tokenized therefore means the sensitive payment number is substituted in the checkout flow, not that no company handles payment or purchase data.
An approval is not a fulfilled order
The merchant remains the seller. It sets prices and availability and handles fulfillment, returns and customer support. The card issuer decides whether to authorize a charge, while the merchant decides whether to accept and complete the order. An approval in dot does not guarantee that a payment will clear or that an order has been accepted, so users should look for the merchant’s confirmation and use the merchant’s normal support channel if something goes wrong. Existing card terms and issuer dispute rights still matter.
There is a nuance between the launch experience and the legal terms. The Wallet terms provide for authority that can allow ChatGPT to approve purchases in advance. But the product announcement and current Help Center describe per-purchase review and approval; OpenAI presents broader automated purchasing controls, such as limits by category or amount, as future plans. Users should not infer that a general unattended shopping mode is already available from the terms alone.
What merchants and makers should prepare
OpenAI’s Commerce Partner Playbook points merchants toward accurate, structured product information and checkout compatibility. The launch materials also discuss Web Bot Auth and coordination with CDN, firewall, payment and risk providers so legitimate agent activity can be recognized. That work sits beside ordinary safeguards: clear product and recurring-payment terms, reliable inventory, authorization checks, fraud controls and a confirmation path that the agent can relay without pretending a pending transaction is complete.
For makers building shopping agents, the useful design pattern is a visible approval boundary: show the exact seller, items, total and payment choice before any charge, then report whether the merchant actually accepted the order. Keep credentials out of prompts and logs, and explain which details leave the agent for checkout. ChatGPT Wallet is a consumer-commerce payment flow; it answers a different question from infrastructure such as Brave’s x402 Search API, where a software client pays per API request.
OpenAI announcement: rollout, approval flow and tokenized payments
OpenAI Help Center: eligibility and current purchase steps
OpenAI Wallet Terms: eligibility, purchase authority and merchant roles
OpenAI Wallet Privacy Notice: payment and purchase data handling
OpenAI Commerce Partner Playbook