🇫🇷 Cet article est aussi disponible en français.

ChatGPT Wallet: The Human Approval Layer Behind Agent Payments

ChatGPT Wallet: The Human Approval Layer Behind Agent Payments
🇫🇷 Cet article est aussi disponible en français.
📑 Table of Contents

TL;DR

OpenAI’s ChatGPT Wallet uses network-issued payment tokens and requires a user security check for each purchase. The initial rollout is limited to eligible US adult Pro subscribers using dots. The interesting question is not whether an agent can click checkout, but whether banks, merchants and users can agree on what the agent is authorized to do.

Introduction

An agent that finds a product and fills a shopping cart can be useful without being trusted to spend. Crossing that final boundary requires more than attaching a card number to a model. It requires a record of the user’s intent, a payment method a merchant accepts, and a way to handle errors after the transaction.

OpenAI’s November 13 announcement places a human confirmation step in the middle of that process. Rather than announcing unrestricted agent spending, it describes a narrower product that works through existing card networks and begins with a limited rollout. (Source : OpenAI — Introducing ChatGPT Wallet)

A token is not a permission slip

The user adds a card once. Before each purchase, OpenAI says the user sees the items, total and selected card, then completes a security check such as a fingerprint or Face ID. After approval, the payment network supplies a token with card-like fields as a substitute for the actual card details. The agent and merchant do not receive the user’s actual card details through this flow. (Source : OpenAI — How a purchase works)

That design separates two problems that are often collapsed. Tokenization reduces exposure of the original card credentials. Approval establishes that the user agreed to a particular transaction. Neither guarantees that the product was described correctly, that delivery succeeds, or that a compromised account cannot initiate a misleading request. Payment security and shopping correctness are separate layers.

OpenAI says existing card rewards and protections for eligible disputes remain available. That matters because a consumer does not need to replace a familiar card relationship with a new closed payment balance. The business still controls fulfillment, returns and customer service. Those claims describe the intended product; actual protections depend on the card and the dispute. (Source : OpenAI — Introducing ChatGPT Wallet)

The rollout is smaller than the headline

OpenAI says 1.2 billion people use ChatGPT weekly, but that figure is not a Wallet adoption metric. Wallet initially rolls out inside dots to US-based Pro subscribers aged 18 or older with eligible US-issued cards. It would be a mistake to treat the entire ChatGPT audience as a population already paying through agents. (Source : OpenAI — Availability)

The distinction is important for measurement. The size of the installed audience is a distribution advantage, not evidence of completed purchases. A useful future scorecard would separate people offered Wallet, users who add a card, attempted transactions, approvals, successful orders, declines and subsequent disputes. Without those denominators, a headline user count says little about commercial conversion.

The limited launch also leaves international coverage, other cards and other agent surfaces open. Product teams building commerce flows should check current eligibility rather than assuming a general API or universal support.

The merchant remains a gatekeeper

A valid payment token does not ensure an agent can reach checkout. OpenAI notes that site defenses can block agent traffic and payment-risk systems may flag legitimate agent transactions. Its guidance suggests signed requests, current product information, and coordination with payment and fraud providers. It also points to plugins and WebMCP as potential ways for businesses to expose functions. (Source : OpenAI — Equipping businesses for agentic commerce)

This shifts the bottleneck from model intelligence to ecosystem coordination. A merchant may reasonably be unwilling to allow an unfamiliar automated client to browse inventory, submit forms or trigger orders. An agent that cannot reliably distinguish a stale price from a current one may still create support costs even if its payment is legitimate.

For operators, the right experiment is a funnel: can the agent find an item, verify stock, preserve the full price including shipping, present a coherent approval, complete checkout and confirm the order? Record the failure at each boundary. A successful authorization is not the same as a successful order.

Approval now, delegation later

OpenAI describes a future in which users could set spending limits, purchase categories or time periods and pre-approve purchases with additional safeguards. That is a direction, not a feature to assume exists in the initial launch. (Source : OpenAI — How a purchase works)

A standing mandate would change the risk profile. A limit of $50 per transaction, for example, is not necessarily a $50 total budget if repeated purchases are permitted. A meaningful policy would need cumulative caps, merchant and category restrictions, expiration, revocation and clear records. Those are design considerations, not features OpenAI has committed to in this announcement.

The immediate product is therefore a supervised checkout assistant, not an independent procurement department. That may be the sensible first step: it lets participants observe failure modes while preserving a deliberate point of human control. The harder test comes when approval is no longer required for every purchase.

FAQ

Does the agent receive my actual card number?

OpenAI says the payment network supplies a substitute token and that actual card details are not shared with the agent or business through Wallet.

Can Wallet make purchases without asking me?

The announced flow requires a security check for each purchase. Fully delegated purchasing is described as a possible future direction.

Does 1.2 billion mean Wallet users?

No. It is OpenAI’s stated weekly ChatGPT user figure, not a count of Wallet users or completed orders.

Why might a purchase still fail?

A site can block automated traffic or a risk system can decline an otherwise legitimate agent-initiated transaction. Inventory, price changes and merchant rules can also interrupt checkout.

Further Reading

— The Agent Report