OpenAI Launches ChatGPT Wallet With Per-Purchase Biometric Approval

OpenAI launched ChatGPT Wallet on November 13, 2026, a payment system that lets users approve agent-assisted purchases without exposing card details to merchants or to the AI agent itself. The wallet was built with American Express, Mastercard, and Visa, and is rolling out first through dots to US ChatGPT Pro subscribers aged 18 and older holding eligible US-issued cards. The scope is deliberately narrow, and OpenAI is explicit about why: it wants to learn from real-world use before widening access.

The stakes are considerable. OpenAI reports that 1.2 billion people use ChatGPT each week, many of them to research products, compare options, and decide what to buy. Wallet extends ChatGPT from shopping research into transaction completion — a shift that puts OpenAI on the payment rail alongside the networks and banks that currently evaluate every transaction. In plain words: the assistant that recommends the product can now, with your fingerprint, buy it.

How does a user actually pay?

The flow requires a decision on every single transaction. Users add a card once. Before each purchase, they review the items, the total, and the selected card, then approve with a security check such as Face ID or a fingerprint scan. Each approval creates a record of what the user authorized the agent to buy. There is no fully delegated spending at launch.

After approval, the payment network supplies a payment token — a substitute credential containing a card number, security code, and expiration date. The selected card is charged without the actual card details reaching the business or the agent. OpenAI's payment documentation says merchants receive a network token rather than the full card number, and can use the Payment Account Reference to associate the token with the underlying payment account.

Consent is transaction-specific. Merchants must not reuse or save the payment credential for a separate purchase. Recurring billing remains possible only when the existing checkout supports it, the customer consents to recurring charges, and the merchant follows its processor's guidance for merchant-initiated transactions. The takeaway: Wallet's security model rests on one-time tokens, not on trusting the merchant.

What protections survive the move to agents?

Cardholders keep their existing rewards and protections for eligible disputes with businesses, including disputes involving defective items. Banks and payment networks continue to evaluate transactions. Users still transact directly with businesses, which retain the customer relationship and control over pricing, fulfillment, returns, and customer service.

Merchants also remain responsible for order handling and fraud decisions, and they can continue using an existing authorized card-on-file flow separately from Wallet. OpenAI has not removed the incumbent payments stack; it has inserted an approval layer in front of it.

Why do approved purchases still fail?

This is the part of the launch that OpenAI's announcement spends the most time qualifying. ChatGPT Wallet works with existing checkout pages and payment forms without a Wallet-specific integration, though optional compatibility checks can improve reliability. But websites can still block agents inadvertently, and risk systems tuned to detect bots can be set off by ChatGPT's cloud browser, leading to failed, declined, or canceled purchases.

To address this, OpenAI is rolling out support for relaying user signals in the Forwarded HTTP header. The signals can include:

• the observed IP address
• estimated IP country
• masked network prefix
• locale
• time zone
• autonomous-system number (the numeric identifier of the network operator routing the traffic)
• browser or app details

These signals give merchants and risk providers additional context for assessing a transaction. OpenAI notes the available signals may vary during the rollout.

The company is also working with fraud-prevention partners Forter, Riskified, Sardine, and Signifyd, and payment service providers Adyen, Checkout.com, and Stripe, to help their systems recognize legitimate agent purchases. That work addresses a problem distinct from payment acceptance: a checkout can process Wallet's token while its risk controls still reject the transaction. In short, tokenization solves the credential problem, not the bot-detection problem.

What is OpenAI telling merchants to do?

The Commerce Partner Playbook describes a purchase journey that starts with discovery and comparison, then moves to either the merchant's existing website in a browser or a plugin. Browser use follows the existing site flow and requires less integration work. A plugin exposes structured actions and lets the business control backend validation and execution.

The playbook also lists practical steps for merchants:

• submit current product feeds
• check whether their CDN or firewall blocks verified ChatGPT browser visits
• integrate Sign in with ChatGPT when an account is required
• manage a Business Profile

The burden of compatibility sits largely with merchants, not with OpenAI — a point the documentation makes clear even if the marketing does not.

What are dots, and why do they matter?

Wallet's initial host is dots, which OpenAI introduced on September 29, 2026 as always-on agents with their own cloud computer and browser. Dots can connect to more than 4,000 apps through plugins, while users control app permissions, review activity, and set approval requirements. Wallet adds a payment step to that supervised operating model.

The pairing is instructive. Dots already required a permission-and-review architecture; Wallet slots a biometric checkpoint into it rather than inventing a new trust model.

When can agents spend without asking?

Not yet. OpenAI expects eventually to let users delegate purchases entirely by setting spending limits, purchase categories, or time periods, and pre-approving them with enhanced safeguards that build on biometric checks and authorization records. At launch, though, the agent cannot complete a Wallet purchase without the user's review and security check. That promise has no attached date, and OpenAI's own framing — that it is starting with limited availability to learn — signals how much depends on what the early transactions reveal.

The limited launch separates payment authorization from merchant acceptance. OpenAI has defined how a user approves and pays. Whether Wallet becomes anything more than a Pro-tier convenience depends on whether business websites and risk systems can consistently accept those approved transactions — a variable OpenAI does not control.