On November 13, 2026, OpenAI began a phased rollout of ChatGPT Wallet, a payment feature that supports purchases made by AI on a user's behalf. The initial rollout is limited to ChatGPT Pro subscribers in the United States who hold an eligible US-issued card. Once users have set up the AI agent "dot," it can search for and compare products and use Wallet when it makes a purchase. After the user approves each purchase with biometric authentication, a payment token that stands in for the actual card details is entered into the merchant's existing checkout page. However, approval does not guarantee that an order goes through. Purchases may fail to complete depending on whether the agent can access the merchant's site and on fraud-detection checks at payment.
Rollout starts with US Pro subscribers and eligible cards
ChatGPT Wallet is the payment feature the AI agent "dot" uses when buying products on a user's behalf. OpenAI launched it in cooperation with American Express, Mastercard, and Visa. Users must set up dot beforehand, and the feature cannot be used from regular Chat, Work, or standalone Codex threads. Availability for eligible users will expand in stages. Details are explained in OpenAI's official announcement and user help page.
The initial rollout covers ChatGPT Pro subscribers aged 18 or older who live in the US, and the card's billing address must also be in the US. Eligible cards are US-issued credit cards from American Express, Chase, Mastercard, and Visa; for Chase, only primary cardholders qualify. Debit cards and virtual cards that users create themselves are not supported at launch.
During initial registration, users enter the card number, expiration date, and security code in a secure dedicated form. Additional identity verification is required if the card issuer asks for it. OpenAI warns users not to type card details or bank verification codes directly into the chat.
Even after a card is registered, the user must approve every purchase. Users review the merchant, item, total amount, and card to be used, then approve with biometric authentication such as Face ID or Touch ID. If the device in use does not support biometrics, users can proceed via a link or QR code and approve on a compatible device logged in to the same ChatGPT account.
After approval, the payment network issues a payment token that replaces the actual card information. The token contains substitute values for the card number, expiration date, and security code, and dot enters it into the merchant's existing checkout page. The charge goes to the card the user selected, and according to OpenAI, the actual card details are never shared with the merchant or the AI agent. This differs from an approach in which users create and register their own virtual cards.
Approval and order confirmation are separate steps
What matters when using ChatGPT Wallet is that registering a card, approving a purchase, and the merchant confirming an order are distinct stages. The "Ready to check out" message on the purchase screen means the user's approval is complete, but it does not guarantee that the merchant has accepted the order. Based on OpenAI's official help documentation, the checkout process can be summarized as follows.
| Stage | What it confirms | What to check next |
|---|---|---|
| Card registration | The payment method has been registered | Review each purchase and approve it with biometrics |
| Purchase approval / Ready to check out | The user has approved this purchase | Whether the merchant accepted the order |
| Merchant order confirmation | The merchant's result for the order | Guidance from the merchant on shipping, returns, and similar matters |
Summary based on OpenAI's official help documentation at the time of launch.
If it is unclear whether an order went through after approval, users need to check the merchant's confirmation notice or order history. Even if an error appears or a pending charge shows up on the card, users should not immediately retry the purchase. To avoid duplicate orders, OpenAI recommends checking the order status with the merchant before trying again. Approval by the user does not necessarily mean the merchant has finished processing the order.
Recurring charges also call for attention. If the user agrees, a merchant can store payment information and bill on an ongoing basis under the agreed terms. Removing a card from Wallet does not cancel orders already placed or recurring charges. For order changes, returns, and refunds, users must contact the merchant; for declined or pending payments and unrecognized charges, they must contact the card issuer. OpenAI is the point of contact for problems with Wallet itself and for purchases that differ from what the user approved.
According to OpenAI, transactions take place directly between the user and the merchant, and the merchant remains responsible for pricing, shipping, returns, and customer support. Benefits attached to existing credit cards and protections for eligible transaction disputes are also said to remain in place. Wallet is positioned less as a new payment method than as a mechanism for using existing card payments safely through an AI agent.
From search to completed purchase, merchants also need to be ready
The tools OpenAI offers merchants fall broadly into two types: those that support product search and comparison, and those that handle actual purchases and bookings. The official developer guide describes two approaches: retailers can supply product feeds to support AI-driven product search, or they can have purchases and bookings handled through browser access to their existing sites or through plugins. The scope of what AI handles extends beyond ordinary goods to restaurants, travel, tickets, and more, and for supported services users can move from conversation to purchase or reservation.
For browser-based purchases, merchants are not required to adopt a dedicated plugin or product feed. They do, however, need an environment in which the AI agent can access the site normally. OpenAI asks merchants to review their CDN and firewall settings so that they can support "Web Bot Auth," which identifies signed requests. Even if the AI finds a product, it cannot proceed to purchase if it cannot access the merchant's site.
Furthermore, even if the AI agent can use a token on an existing checkout page, the merchant's fraud-detection system may reject the transaction or cancel the order. To address such issues, OpenAI said it is working with fraud-prevention companies Forter and Riskified and payment providers Adyen and Stripe, among others. In other words, for an AI-driven purchase to succeed, several conditions must be met: the product must be searchable, the merchant's site must be accessible, and the payment must be accepted.
As a future direction, OpenAI has also outlined a mechanism in which users set spending limits, purchase categories, usage periods, and similar parameters in advance and let the AI buy without individual approvals. However, it has not disclosed when availability will expand to other regions, including Japan, or when a feature allowing full delegation of purchases will arrive. Performance data such as purchase success rates across multiple merchants is also not published in the materials reviewed here. Beyond expanding supported cards and regions, how smoothly merchants can accept legitimate purchases made by AI agents will be a key factor in how widely the feature spreads.