OpenAI Rolls Out ChatGPT Wallet for Agent Purchases | Zeniteq
Loading
Zeniteq is now available on mobile for iPhone, iPad and Apple Watch.Download nowLearn more
OpenAI Rolls Out ChatGPT Wallet for Agent Purchases
ChatGPT Wallet lets eligible U.S. Pro users approve agent purchases with a security check, while merchants must prepare their websites and payment systems to accept them.
OpenAI launched ChatGPT Wallet for eligible U.S. Pro subscribers, enabling AI agents to facilitate purchases using tokenized payment credentials. Rather than autonomous spending, the system requires users to review agent-selected items and authorize each transaction via biometric security checks like Face ID. This process uses network-supplied tokens to protect actual card details while ensuring compatibility with existing merchant checkout flows.
For businesses, implementation requires more than accepting payments. Merchants must update product feeds, configure firewalls to recognize signed agent requests, and coordinate with fraud providers to prevent legitimate agent-initiated transactions from being incorrectly flagged or declined.
OpenAI announced ChatGPT Wallet on November 13, 2026, starting a gradual rollout of card payments through its dots agents. The launch is limited to U.S. ChatGPT Pro subscribers aged 18 and older with eligible U.S.-issued cards. Users can add a card once and let an agent work toward completing a purchase, but each purchase still requires their approval through a security check such as Face ID or a fingerprint scan. OpenAI’s announcement describes the payment flow; The Verge reports the age and card eligibility requirements.
Wallet moves OpenAI’s shopping features from finding and comparing products into paying for them. Its most consequential detail, though, is the separation between an agent preparing a transaction and a person authorizing it. The launch gives agents a way to submit approved card payments, not an open-ended spending allowance.
For businesses, accepting those payments involves more than having a working checkout page. Website access controls and fraud systems can each stop an otherwise legitimate purchase.
Who Can Use ChatGPT Wallet at Launch?
ChatGPT Wallet initially operates through dots, OpenAI’s agent platform. Eligibility is narrower than simply having a paid ChatGPT subscription, and qualifying users may still have to wait for access during the rollout.
Launch requirement
What it means
ChatGPT Pro subscription
The announced rollout is for Pro subscribers.
U.S. location
Initial availability is in the United States.
Age 18 or older
The launch is restricted to adults.
U.S. billing address
The Verge reports this as an eligibility requirement.
Eligible U.S.-issued card
The Verge names eligible American Express, Chase, Mastercard and Visa cards.
Access through dots
OpenAI’s announced starting point is its dots agent experience.
Rollout access
Meeting the requirements does not guarantee immediate availability.
The named card providers should not be read as a promise that every card carrying one of those brands will work. The opened launch materials do not provide a complete card-by-card eligibility list. supplies the billing-address requirement and named card options.
OpenAI built Wallet with American Express, Mastercard and Visa. It says the limited release will help it learn from real-world use and improve compatibility with businesses, banks and payment networks. That makes gradual availability an operational part of the launch, not simply an account-access detail. OpenAI
I’d distinguish two checks before relying on Wallet for a purchase: whether your account and card have access, and whether the intended merchant supports an agent completing checkout. Passing the first does not guarantee the second.
How an Approved Purchase Works
OpenAI describes a payment process that keeps a human decision immediately before the agent receives usable payment credentials:
Add an eligible card once. Users do not need to re-enter their underlying payment details for each Wallet purchase.
Ask the dot to find something to buy. The agent can move from the shopping task toward checkout.
Review the proposed purchase. OpenAI says the user reviews the items, total and selected card before approval.
Complete the security check. Each purchase requires approval using a check such as Face ID or a fingerprint scan.
Let the network supply a payment token. After approval, the payment network provides substitute payment credentials for the agent to use.
OpenAI says each approval creates a record of the purchase the user authorized. The company’s announcement also says users transact directly with the business, which retains responsibility for pricing, fulfillment, returns and customer service.
The review screen is therefore an important control. A successful security check confirms approval; it does not tell the user whether the agent selected the correct product, quantity or price. My view is that the purchase summary deserves the same attention as an ordinary checkout screen. Delegating the shopping work makes the final review more consequential, because the user may not have personally made every selection along the way.
Approval also cannot guarantee a completed order. OpenAI explicitly warns that agent access restrictions and payment-risk systems can produce failed purchases, declines or cancellations.
What Tokenization Protects
The payment network supplies a tokenized substitute credential after the user approves a purchase. OpenAI says that credential includes a card number, security code and expiration date, allowing the payment to fit existing checkout flows without giving the agent or merchant the user’s actual card details. The charge still goes to the selected card. OpenAI
The distinction is between the underlying card credentials and the substitute credentials used to make the payment. The agent receives something usable at checkout, but OpenAI says it does not receive the real card details.
CNBC further reports that the network-provided credential is scoped to a given transaction. That detail helps explain how the launch combines automation with a specific authorization: the user approves a purchase, and the network supplies credentials for that transaction.
OpenAI says users retain their card’s existing rewards and protections for eligible disputes, including an example involving defective goods. “Eligible” matters here. The announcement preserves existing card protections; it does not promise a new blanket refund policy for every agent purchase.
Tokenization addresses one particular exposure: sharing the underlying card credentials with the agent and merchant. It does not establish that every other part of the shopping task will be correct or reliable. The available evidence describes the intended payment design, with no independent testing of Wallet’s security, checkout reliability or fraud outcomes.
For consumers, the practical benefit is a payment credential that an agent can use after approval without needing access to the actual card details. For merchants, the benefit is compatibility with familiar checkout fields. Those benefits still depend on the surrounding purchase process working.
Why Wallet Is Not Autonomous Spending
OpenAI describes fully delegated purchasing as a future direction. It expects users eventually to set parameters such as spending limits, purchase categories or time periods, then pre-approve purchases with additional safeguards. That is a roadmap statement, not a generally available launch feature. OpenAI
At launch, the documented model is simpler: an agent prepares a purchase, the user reviews it, and the user approves that purchase through a security check.
That distinction changes which tasks Wallet can handle. A dot may help find an item and bring the transaction to an approval step. The launch does not offer the documented permission model needed for an agent to keep buying supplies unattended under a standing budget.
I’d judge the initial release as assisted transaction completion. It reduces payment entry and lets the agent carry out more of the checkout task, while leaving the spending decision with the user each time.
What Businesses Can Do to Accept Agent Purchases
OpenAI released a Commerce Partner Playbook alongside Wallet. Its announcement summarizes several practical steps businesses can take, covering product information, website access and payment-risk handling.
These are separate areas of compatibility. A merchant can have accurate product listings but block the agent at its firewall. It can allow the agent to browse but have a risk provider reject the payment.
Keep Product Information Accurate
OpenAI advises businesses to claim their business in ChatGPT and, after verification, update their business details and upload a product feed with current pricing and availability. OpenAI
A useful feed gives the discovery stage information that matches what customers can actually buy. The practical implication is that feed maintenance belongs with normal catalog operations. A stale price or unavailable item can create a mismatch between an agent’s recommendation and the eventual checkout.
OpenAI also says browser access does not require a plugin or product feed. A feed supports product discovery and accuracy; it is not a universal prerequisite for an agent to visit a merchant’s website.
Check CDN and Firewall Access
OpenAI tells merchants to configure their content delivery network or firewall to recognize signed requests using Web Bot Auth, and to check whether general site security measures inadvertently block ChatGPT agents. OpenAI
The documented mechanism is recognition of signed agent requests. OpenAI’s announcement does not provide enough implementation detail to give a universal configuration recipe, and the relevant setup will depend on the merchant’s infrastructure.
My recommendation would be to use verified agent identity as a specific input to access controls, while keeping protections for abusive traffic. Simply relaxing bot defenses across an entire site would be a much broader change than the launch guidance supports.
Review Payments and Fraud Handling Together
Wallet’s tokens can work with existing checkout flows, according to OpenAI. The company also warns that risk systems may flag legitimate agent purchases, causing declines or cancellations. It recommends working with payment and risk providers to understand how they recognize these transactions. OpenAI
That warning contains the most important merchant-side distinction: payment-format compatibility is not the same as transaction acceptance.
A checkout can accept a card number, security code and expiration date while another system rejects the order. Businesses should therefore involve both payment operations and fraud teams when assessing agent purchases.
Useful questions for those providers include:
Can the website distinguish authenticated agent requests from unidentified automation?
How does the risk provider recognize legitimate purchases made through an agent?
Where are failures occurring: website access, payment processing or order review?
Can the business track agent-related declines and cancellations without weakening controls for other transactions?
These are practical checks derived from the failure points OpenAI identifies, not a claim that Wallet requires one particular fraud-policy configuration.
Preserve the Merchant’s Customer Responsibilities
OpenAI says the business retains its customer relationship and control over pricing, fulfillment, returns and service. Wallet changes who carries out parts of checkout; it does not move those responsibilities to OpenAI. OpenAI
Businesses should keep order confirmation and support processes understandable for customers whose purchases were agent-assisted. A tokenized payment still leads to an ordinary set of merchant obligations: deliver the order, handle problems and apply the relevant return policy.
Merchant Support Remains a Separate Hurdle
Some businesses deliberately restrict agents. CNBC reports that United Airlines said it would block agents from accessing its systems to book tickets, while Amazon prevents agents from purchasing products on its platform. Those policies show why possessing an approved payment credential cannot, by itself, make every merchant accessible. CNBC
CNBC also reports that OpenAI is not taking a cut of transactions at launch. That describes OpenAI’s initial approach; it should not be read as a claim that ordinary card processing is free or that future commercial terms are fixed.
The launch’s practical test is whether three parts can work together: agents reaching checkout, users authorizing the intended purchase, and merchant payment systems accepting it. Tokenization supplies the payment mechanism. Merchant access and risk controls determine how often that mechanism can finish the job.
Frequently Asked Questions
4 questions
1
Who Is Eligible for ChatGPT Wallet?
The gradual launch covers U.S. ChatGPT Pro subscribers aged 18 and older, with a U.S. billing address and eligible U.S.-issued cards, through dots. An eligible user may not have access immediately.
2
Can a Dot Spend Without Asking Each Time?
Not under the documented launch model. Every purchase requires user approval through a security check. OpenAI describes purchases pre-approved under spending limits and other parameters as a future direction.
3
Does the Merchant Receive the Actual Card Details?
OpenAI says the merchant and agent receive tokenized substitute credentials, not the user’s actual card details. The purchase is charged to the selected card, with its existing rewards and eligible dispute protections.
4
Do Merchants Need a Plugin to Allow Agent Browsing?
OpenAI says browser access does not require a plugin or product feed. Merchants may still need to adjust access controls and work with payment and risk providers to support legitimate agent purchases.