ChatGPT Wallet: tokenized agent payments launch
Tokenized card payments keep OpenAI's agents from seeing your card, but they don't vet the merchant.
Scope and setup
Tokenization solves the card-exposure problem
Merchant risk is still the user's job
Autonomous purchases need more than a token
## Scope and setup OpenAI has switched on ChatGPT Wallet for paying Pro users in the US, and only for its always-on dots agents. Users must be 18 or older, add an eligible US card once, and the agent can then prepare a purchase for approval. The launch is deliberately narrow: OpenAI built it with American Express, Mastercard and Visa, and it is a long way from the 1.2 billion weekly ChatGPT users OpenAI cites.
## Tokenization solves the card-exposure problem The mechanics are sensible. Before a purchase, the user sees the items, total and card, then approves with Face ID or a fingerprint. The card network then issues a payment token — a stand-in number, security code and expiry — so neither the merchant nor the AI agent handles the real card. Rewards and chargeback protections still apply. For anyone who has hesitated to hand card details to an autonomous browser agent, that is the right architectural boundary: the agent gets a scoped payment credential, not your primary account number.
## Merchant risk is still the user's job Tokenization protects the credential, not the decision. A brand-protection firm's September test asked ChatGPT, Gemini and Perplexity where to buy from 151 brands; across 6,795 answers, ChatGPT surfaced a risky site — a fake shop or dead URL — in 8% of answers, versus 15% for Perplexity and 4% for Gemini. It is the firm's own methodology and it sells brand-protection services, so treat the numbers as directional. Still, the lesson stands: a secure payment to a fraudulent shop is still a fraudulent purchase. Some merchants also block agent traffic outright, so expect failed checkouts even when the wallet works.
## Autonomous purchases need more than a token OpenAI says future agents may buy without per-purchase approval, governed by spending caps, product categories or time windows, but it has not set a date. That is where the hard work begins. Developers building agent-commerce flows need merchant verification, idempotent order handling, clear dispute paths and spend controls that are enforceable outside the model's context. For now, the approval screen is the control plane: read the merchant, the item and the total before you authenticate. Convenience is real; delegated trust is not automatic.
Treat tokenization as a credential safeguard, not a substitute for checking the merchant before you approve.