OpenAI launches ChatGPT Wallet, letting agents pay only with user approval

OpenAI introduced ChatGPT Wallet on November 13, describing it as a secure way for agents inside ChatGPT Work, Codex and dots to complete purchases with user approval while existing card protections stay in place.

Two phrases carry most of the announcement's weight: user approval and existing card protections. The first means an agent cannot spend on its own authority and each transaction needs the user's confirmation. The second places the flow inside the banking system's familiar security and dispute framework — OpenAI's wording does not present this as a new payment network.

TechCrunch adds the rollout detail: the wallet begins as a limited release for U.S. Pro subscribers, with agents able to shop and check out on a user's behalf. Both sources agree on the division of labor — the agent executes the purchase, the human authorizes it.

The wallet is wired into entry points that already exist. ChatGPT Work handles task execution inside workstreams, Codex serves coding and development work, and dots is the third product line named in OpenAI's description. Attaching payments to those surfaces gives action-taking agents the one capability they were missing.

The real design question is scope of permission, not the checkout button. Once an agent can place an order, a mistake costs money rather than credibility, so approval granularity, an auditable trail and reversibility matter more than which payment rail carries the transaction. OpenAI leading with user approval suggests it understands that trust is the gating factor for the whole feature.

Several things remain undisclosed in the material available: which merchants are supported, whether limits apply per transaction or in aggregate, how refunds and disputes are assigned, and when the wallet moves beyond U.S. Pro subscribers. Those details decide whether this is a demo-grade capability or a usable checkout channel.

Three things are worth watching: the first merchant mix, the actual approval interaction users will see, and how liability is split among OpenAI, the merchant and the card issuer when the first disputed purchase arrives. For teams building agent products, the signal is that the payment authorization layer is becoming something you either build or integrate.