ChatGPT Wallet lets dots complete approved purchases

What OpenAI released

OpenAI announced ChatGPT Wallet [1] for purchases completed through dots. The first rollout covers eligible US-issued American Express, Mastercard and Visa cards for ChatGPT Pro subscribers aged 18 or older in the United States.[1][4]

Users add a card once. For each purchase, the interface shows the items, total and selected card before asking for a security check. The payment network then issues substitute card details for the transaction, so OpenAI says the dot and merchant do not receive the user’s actual card details.[1][4]

The merchant still owns pricing, fulfillment, returns and customer service. Existing rewards and eligible dispute protections continue through the selected card.[1]

What the wallet changes

Dots already have a cloud computer, browser and access to connected apps. Wallet gives an eligible dot a supervised path from product research to checkout, while OpenAI’s launch rules keep final purchase approval with the user.[1][2]

This approach differs from Brave’s new x402 search route. Brave asks software to sign a small USDC payment for each API request, while ChatGPT Wallet uses a user’s existing payment card and requires approval for a retail order. Both put spending inside an agent workflow, but their credentials, settlement systems and risk boundaries differ.[7]

OpenAI previously supported Instant Checkout through its Agentic Commerce Protocol. Mastercard describes that system as an embedded checkout using agentic tokens. Wallet extends the purchase path to dots working with existing merchant sites, subject to site access and risk controls.[1][6]

Where purchases can still fail

Tokenization protects the underlying card number, but it does not prove that the dot chose the right item, quantity, delivery address or merchant. Users should verify those fields before authentication.

OpenAI says some sites block agent browsers and some payment or fraud systems may reject legitimate agent purchases. The company published a commerce playbook and named payment and fraud partners that are working to recognize these transactions.[1]

Businesses can also claim a profile, upload current product feeds and create a separately labeled Business Agent through OpenAI’s Business Hub. Those tools improve product information and customer conversations, but they do not guarantee Wallet acceptance.[3]

TechCrunch reports that merchant coverage remains a practical constraint and notes that Amazon blocks outside shopping agents while developing its own shopping system. A working wallet therefore does not imply broad retailer acceptance.[5]

A safe first purchase

Treat the first transaction as a test of the full order, payment and support path. Use a low-cost item from a merchant you already trust, then inspect every field before approving it.

• Use a card with transaction alerts and familiar dispute controls.
• Ask the dot for one exact item, variant, quantity, maximum total and delivery deadline.
• Confirm the merchant domain, item, tax, shipping fee, address, delivery date and return terms before authentication.
• Reject substitutions or changed totals unless you review them again.
• Save the approval record, merchant confirmation and final order number outside the chat.
• Check that cancellation and return instructions work through the merchant, because the merchant remains responsible for fulfillment and service.[1]
• Do not treat planned autonomous spending limits as available until OpenAI ships and documents them.[1]

What remains uncertain

OpenAI has not published the number of users in the initial rollout, a complete merchant list or transaction success rates. The company describes the release as limited while it learns about compatibility and reliability.[1]

OpenAI says future users may pre-approve purchases within spending, category or time limits. The announcement does not give a release date or the final control design.[1][4]

The launch post explains tokenization and approval, but it does not publish an independent security assessment of the full shopping flow. Tokenized card data addresses one risk, while product choice, account access, delivery data, merchant fraud and prompt injection need separate controls.

Reuters reported the launch details, and TechCrunch documented the merchant-access constraint. Neither report supplies measured reliability or fraud outcomes from the limited rollout.[4][5]

Frequently asked questions

• Can a dot buy something without approval today?[1] OpenAI says every purchase in the initial rollout requires the user to review it and complete a security check.
• Who can use ChatGPT Wallet first?[1][4] The rollout starts with ChatGPT Pro subscribers aged 18 or older in the United States who have eligible US-issued cards.
• Does the merchant receive the real card number?[1] OpenAI says the payment network supplies substitute card details, so the merchant and dot do not receive the actual card details.
• Who handles returns and disputes?[1] The merchant handles returns and customer service, while eligible card dispute protections remain available through the selected card.
• Will every website accept a dot purchase?[1][5] No. Agent blocking and fraud controls can still prevent checkout, and OpenAI describes merchant compatibility as work in progress.