ChatGPT Wallet puts an approval step between an agent’s suggestion and your money

ChatGPT Wallet lets an agent complete a purchase using a substitute payment credential, while keeping the customer’s actual card details out of the agent’s view. The initial rollout is limited to eligible adult ChatGPT Pro users in the United States, using dots and supported US-issued credit cards. It is a payment feature with a deliberately narrow starting point, not worldwide shopping autonomy.

OpenAI’s November 13 announcement describes a system built with American Express, Mastercard and Visa. Before a purchase goes ahead, the customer reviews its details and completes a security check. The network then supplies a token linked to the selected card. The merchant still handles the order, delivery and returns.

The approval is the important handover

An assistant that finds an item and an assistant that buys it cross different boundaries. A mistaken recommendation can be ignored. A mistaken purchase creates an order, may reserve money and can leave the customer with cancellation work. Wallet’s approval step makes that transition explicit.

The token protects the underlying card number from the agent and merchant. It does not establish that the selected item is suitable, that its seller is trustworthy or that its delivery terms match the customer’s needs. Those questions remain part of reviewing the transaction. A secure payment mechanism and a good purchasing decision are related, but neither guarantees the other.

That distinction comes directly from OpenAI’s purchase guidance. It matters particularly when an agent loses its place, a page stops responding or a conversation ends during checkout. Repeating an action may feel like fixing a stalled interface, while the merchant may already have accepted the first request.

A saved card is not permission for every purchase

Adding a card and approving a transaction are separate actions. Card details belong in the secure enrollment form rather than the conversation. The launch guidance also excludes debit cards and user-added virtual cards, despite Wallet itself generating a virtual payment credential during checkout. The same word can describe two different parts of the system.

Recurring payments deserve their own reading. If a customer agrees to a merchant’s subscription terms, the merchant may retain the payment credential for later charges. Removing a card from Wallet does not itself cancel an existing order or merchant subscription. The cancellation belongs with the business that operates that agreement.

This makes the merchant receipt valuable beyond bookkeeping. It identifies who sold the item, which terms were accepted and where to resolve fulfilment problems. Hiding a card number does not remove the commercial relationship between buyer and seller.

The next constraint is the checkout around the payment

OpenAI acknowledges that some websites and risk systems may block or reject agent purchases. A token can fit an existing payment form while the surrounding checkout still objects to how the buyer reached it. Product availability, addresses, fraud checks and order confirmation remain parts of the transaction.

For businesses, that means accepting an agent is more than publishing a product description. Accurate stock and pricing need to survive the path from search to cart. For customers, it means a confident conversational answer should not be treated as a substitute for the final amount and merchant confirmation.

The launch also leaves a clear boundary around geography: eligibility is tied to the US rollout and supported cards. Broader availability and more extensive pre-authorized delegation are future plans, not capabilities to assume today. Wallet’s immediate contribution is smaller and more useful: it gives the moment when advice becomes spending an explicit, reviewable checkpoint.