ChatGPT Wallet: Availability, Purchase Approval and Checkout Errors

OpenAI launched ChatGPT Wallet on November 13, allowing eligible US Pro users to approve purchases that their dots complete. The important limit is human approval: saving a card does not give the agent unrestricted permission to spend. Nor does approving a payment establish that a merchant accepted the order.

Those distinctions matter more than the demonstration of an agent filling a checkout form. A useful shopping assistant has to keep the item, authorization and order status aligned, especially when a browser hangs halfway through payment. This guide uses the published documentation, not a firsthand checkout test.

Who can use ChatGPT Wallet?

The launch announcement describes an initial rollout through dots for US ChatGPT Pro subscribers aged 18 or older with eligible US-issued cards. This is a limited rollout, not a promise of access for every ChatGPT account or compatibility with every store.

OpenAI's Wallet help guide adds practical restrictions: a US billing address is required, and Wallet does not work in ordinary Chat, Work or standalone Codex threads. Purchase approval needs biometrics on a supported device. Chase cardholders must be the primary cardholder; virtual cards cannot be added at launch.

Updated November 14: OpenAI now explicitly says eligible US Pro users may still lack access during the gradual rollout. Eligibility is necessary, not proof that Wallet is enabled. If it is missing, do not assume your card or the merchant is the problem.

Card setup is not purchase approval

OpenAI separates saving a payment method from authorizing its use. Each purchase involves reviewing the items, total and selected card, followed by a security check. After approval, a payment network supplies a tokenized payment credential rather than exposing the actual card details to the agent or merchant.

OpenAI discusses future delegation through spending limits and other parameters, but that is a stated direction, not the launch behavior. Do not mistake a saved card for a standing purchasing mandate.

For example, “find a good backpack” leaves size, delivery date and budget unresolved. A better instruction is: “Compare backpacks under $120 including delivery, show the chosen item and total, and stop for approval before purchasing.” This is a proposed task brief, not a tested prompt. Its value is that the approval can be checked against something concrete.

What to check when checkout fails

Enter card details only in the secure setup form, not the conversation. Enrollment, approval and order confirmation are separate stages. OpenAI explicitly says “Ready to check out” indicates completed approval, not a placed order.

If the conversation freezes or a pending charge appears without a clear result, check merchant confirmation before retrying. Contact the merchant about orders and refunds, the issuer about charges or bank verification, and OpenAI about Wallet failures. Merchant recurring-payment terms can authorize later charges; removing a saved card does not cancel an existing order or subscription.

The dangerous response to an unclear result is to repeat the purchase immediately. An interface timeout describes what you saw, not necessarily what the merchant processed. Keep the receipt or order reference and resolve the first attempt before starting another. That principle applies whether checkout was completed by a person or an agent.

What tokenization does and does not protect

The Wallet privacy notice says a service provider collects card details through the secure form. OpenAI receives a tokenized credential and limited card information, not the full card number or security code. It also collects purchase and transaction information, contact details, approval records and security signals, with relevant information shared with merchants and payment providers.

Tokenization therefore reduces exposure of the underlying card credential. It does not make the purchase anonymous, establish that the selected product is suitable, or replace a merchant's return policy. These are different problems and should remain separate in the user's mental model.

The same notice says removing a card does not erase all associated records immediately. Some information remains necessary for pending transactions, fraud prevention or legal obligations. Treat removal as stopping future use of that saved method, not as a universal undo button.

For agent products, the standard should be straightforward: a user must be able to tell what was proposed, what was approved and what actually happened. A smoother checkout is useful only if it does not blur those three states.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help AI teams explain product launches and technical workflows clearly enough that users understand both the capability and its limits.

Book a 30-minute call.