OpenAI’s ChatGPT Wallet gives an agent a payment token, not your card number

OpenAI launched ChatGPT Wallet on 13 November, letting agents in dots complete purchases for ChatGPT Pro subscribers in the US after a Face ID or fingerprint check, with the payment network issuing a token in place of the card number. It is a clean consent record and a real limit on credential exposure — and a clear illustration of the difference between identifying a payment credential and identifying an agent.

What happened

OpenAI built the wallet with American Express, Mastercard and Visa. A user adds a card once; before each purchase the agent shows the items, total and selected card, and the user approves with a biometric check. Each approval creates a record of the purchase the user authorized the agent to make. After approval, the payment network returns a payment token — card number, security code, expiry — that is charged to the selected card without the real details reaching the business or the agent.

Availability is narrow: ChatGPT Pro subscribers, 18 and over, with US-issued cards, inside dots, rolling out from 13 November. OpenAI says card rewards and protections for eligible disputes are preserved, and that customers transact directly with businesses, which keep their pricing, fulfilment and returns.

OpenAI also published merchant guidance. Sites need to avoid blocking agents inadvertently, configure CDN or firewall rules to recognise signed requests using Web Bot Auth, and work with payment and risk providers so legitimate agent purchases are not declined. It names Forter, Riskified, Sardine and Signifyd on the fraud side, and Adyen, Checkout.com and Stripe on payments, as partners helping their systems recognise agent-initiated purchases.

The sentence to keep is the roadmap one. OpenAI expects users eventually to delegate purchases entirely, setting spending limits, purchase categories and time periods in advance and pre-approving those purchases with what it calls enhanced safeguards.

Why it matters for KYA

Two identity problems sit inside one checkout, and the wallet solves one of them. The payment token identifies a credential derived from a card. It says nothing about which agent is spending, which operator runs it, or whether the user meant this purchase at this merchant. The authorisation record answers that last question for a single transaction, and that is genuinely valuable: a per-purchase consent artifact is the thing disputes and audits have been missing.

The agent question is handed to Web Bot Auth. OpenAI’s own merchant guidance tells sites to configure infrastructure to recognise signed agent requests — that is agent identity at the edge, not payment identity. A merchant that accepts wallet payments but cannot verify the signature is accepting a token from an unidentified client, and cannot tell a customer’s authorised agent from a scripted card-testing run that has obtained a token.

Delegated spending is where it gets hard. A limit of a set amount in a category until a date is delegated authority, and delegated authority needs the three things KYA keeps asking for: a named principal, an enforceable scope, and a revocation path. The announcement describes the parameters a user will set. It does not say where they will be enforced, or what happens when an agent’s request falls outside them. A limit held inside the agent’s own loop is a suggestion. A limit enforced by the wallet or the network at authorisation time is a control. That is the distinction to test when the feature ships.

There is an accountability question underneath. When a purchase is disputed, the record will show that a human approved a purchase an agent assembled. That is better than the alternative, but it does not establish that the agent described the purchase accurately. A consent artifact is only as good as the summary the user was shown.

What to watch

  • Where spending limits are enforced, and whether a merchant or network can see the policy that applied.
  • Whether the payment token ever carries an agent identifier, or stays a card credential with no agent binding.
  • Whether Web Bot Auth becomes a condition of accepting wallet payments or remains a recommendation.
  • How dispute rules treat agent-assembled carts that a customer approved on a summary screen.

Sources

  • OpenAI, “Introducing ChatGPT Wallet”, 13 November 2026 — openai.com
  • OpenAI, Commerce Partner Playbook — developers.openai.com
  • CNBC, “OpenAI’s ChatGPT Wallet allows ‘dots’ AI agents to make purchases”, 13 November 2026 — cnbc.com

Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.