OpenAI began rolling out ChatGPT Wallet on November 13, a service through which a personal agent can pay for website purchases after the user approves them. The gradual launch initially covers ChatGPT Pro subscribers aged 18 or older in the United States, with eligible US-issued credit cards and a US billing address. Payments are available in conversations with personal agents called dots.
Wallet works after a dot has been set up and is not available in ordinary Chat conversations, Work or standalone Codex threads. The documentation includes eligible American Express, Chase, Mastercard and Visa cards. Chase requires the primary cardholder. Debit cards and user-added virtual cards are excluded at launch. A card saved for Wallet is separate from the payment method used for a ChatGPT subscription.

The customer approves the purchase before payment
Before an order is submitted, the user reviews the merchant, items, quantity, total and selected card. Details may include taxes, shipping, deposits or recurring payments. Approval requires biometric verification, such as Face ID or Touch ID, on a supported device. If the current device cannot perform that check, the process can continue through a link or QR code on a compatible device signed in to the same account.
After approval, the payment network supplies a token that replaces the physical card's details. It contains a number, security code and expiration date that can be used at checkout, while the amount is charged to the selected card's account. The agent and merchant do not receive the real card number. OpenAI developed the service in partnership with American Express, Mastercard and Visa.
The path of a customer-approved payment
- 1. Approval
The customer reviews the offer, total and card, then confirms with biometrics. - 2. Token
The payment network supplies substitute details for the physical card. - 3. Checkout
The merchant processes the order; the dot reports the result.
Wallet confirmation and the store's acceptance of an order are separate stages. Ready to check out means that the user has approved the purchase, after which the dot continues checkout and reports the result. Commercial confirmation belongs to the store. Wallet's terms require a new approval if a material purchase detail changes before submission, keeping authorization tied to the offer presented to the customer.
The store retains checkout and the commercial relationship
According to OpenAI, Wallet can use existing checkout pages and payment forms without a dedicated Wallet integration. The store remains the seller and the entity managing the order, pricing, fulfillment, returns and customer service. The card issuer decides whether to authorize the transaction, while the merchant decides whether to accept the order. Card rewards and protections for eligible disputes follow the issuer's and payment network's rules.
For subscriptions, the commerce documentation allows the existing checkout to be used if it supports recurring billing and the customer consents to those charges. Accepting a specific transaction does not authorize reuse of the credential for another, separate purchase. A merchant can also retain its own previously authorized flow for cards saved in a customer's account. Wallet adds a payment option to that commercial journey.
Agent access depends on request verification
ChatGPT's cloud browser can navigate websites on a customer's behalf, including without a plugin or direct product feed. OpenAI recommends checking cases where a CDN or firewall inadvertently blocks those visits. Signed requests are identified through Web Bot Auth. Validating them enables recognition of legitimate agent traffic while preserving the website's other security controls.
Akamai, Cloudflare, HUMAN and Vercel automatically verify request signatures supported by this mechanism. For other infrastructure, the documentation describes HTTP signature validation using ChatGPT's published public key. Identifying an agent through a self-declared name alone does not replace cryptographic verification. Browser visits are separate from indexing crawlers, including OAI-SearchBot, and a rule for the verified browser does not change how other bots are treated.
Another condition concerns the fraud-prevention systems used by stores and processors. They may interpret the cloud browser as suspicious automated traffic. OpenAI is gradually rolling out the transmission of signals through the Forwarded header, such as IP-estimated country, network prefix, language, time zone or browser information. The signals actually received differ according to the rollout stage and the integration of the provider evaluating the transaction's risk.
The company says it is working with Forter, Riskified, Sardine and Signifyd, as well as Adyen, Checkout.com and Stripe, to recognize legitimate agent-made purchases. This collaboration concerns compatibility with risk assessment and payment processing. The website, its order system, the processor and the card issuer continue to participate in the transaction, each with its own checks and confirmations.
Plugins and structured commercial information
The commerce playbook published alongside Wallet also describes integration through plugins, consisting of an MCP server and agent instructions. A business can expose structured actions for stock, product variants, the cart or checkout, within its implementation's capabilities. The merchant's system retains control over availability, pricing and transaction state. When an integration cannot complete a step, it can return a continuation on the website. Direct third-party plugin interaction with Wallet is documented as under development.
Product discovery, customer authentication and payment are treated separately in the new documentation. Commerce feeds provide current product information, while the browser and plugins support subsequent actions. For websites requiring an account, Sign in with ChatGPT is intended for selected commercial partners, with OpenAI-approved access and manual review before launch. Component choices depend on the store's journey; browser access does not require installing every integration described in the playbook.
The privacy notice states that a payment provider handles the secure card form. OpenAI receives the tokenized credential and limited card information, rather than the full card number or its security code. Information needed about the customer, delivery, order and authorization is also processed to execute the purchase. Data required to place and fulfill the order is sent to the merchant and providers involved in the transaction.