OpenAI introduced ChatGPT Wallet on 13 November 2026, giving a user’s dot a way to pay during a shopping task after the user reviews and approves the purchase. The initial rollout is limited to ChatGPT Pro subscribers aged 18 or older in the United States with eligible US-issued cards. It is gradual, so an eligible account may not have access yet.
Wallet works in conversations with a dot. It is not available in Chat, Work or standalone Codex threads. That distinction matters for teams evaluating agent commerce: this release is a specific consumer checkout flow, not a general payment capability for every OpenAI agent.
Approval comes before checkout
A user adds an eligible card through a secure setup form, with bank verification when required. Before each purchase, the user reviews the merchant, items, total and selected card, along with any shipping or recurring-payment terms shown. Approval requires biometric verification on a supported device. OpenAI’s purchase guidance says the dot then continues checkout and reports the result.
The payment network supplies a substitute credential linked to the selected card, rather than giving the agent or merchant the user’s actual card details. OpenAI says eligible purchases retain the card’s existing rewards and protections for eligible disputes. The applicable card and issuer terms still matter.
Approval is not an order receipt. OpenAI explicitly distinguishes a “Ready to check out” state from merchant confirmation that an order was placed. If the result is unclear, the merchant’s confirmation is the relevant check before another attempt.
What merchants need to handle
OpenAI’s Commerce Partner Playbook says an agent can use a business’s existing website flow; a Wallet-specific checkout integration is not required. Product feeds can improve retail discovery, while plugins offer a separate, more structured integration path. Neither is a prerequisite for browser-based checkout.
The existing path still has failure points. A CDN or firewall can block the agent’s browser, and payment or fraud systems can decline an otherwise authorized transaction. OpenAI’s payment guidance says merchants retain responsibility for the order, fulfilment, customer support and fraud decisions. Operators therefore need to distinguish user approval, payment authorization and merchant order confirmation when investigating failed or duplicate-looking checkouts.
Delegated spending remains a future plan
The launch requires the user to approve each purchase. OpenAI describes possible future delegation through limits on spending, categories or time periods, but those controls are not part of this initial release. Wider availability and merchant compatibility remain open questions as the rollout proceeds.
