OpenAI launched ChatGPT Wallet on November 13, 2026, giving its agents a way to complete purchases without receiving users’ actual card details. Built with American Express, Mastercard and Visa, the feature initially rolls out through dots to eligible U.S. ChatGPT Pro subscribers aged 18 or older. Each purchase requires the user’s review and a security check before the agent can pay, according to OpenAI’s announcement.
The boundary that matters is human approval. ChatGPT Wallet can handle the payment step after authorization; it does not currently give an agent permission to shop and spend independently within a standing budget.
For businesses, the launch creates a different challenge. A customer can authorize a legitimate purchase while a merchant’s firewall or fraud system still blocks the agent carrying it out. OpenAI’s accompanying commerce guidance addresses both website access and payment acceptance, two separate obstacles that merchants need to check.
Who Can Access ChatGPT Wallet
ChatGPT Wallet is a gradual rollout, so meeting the eligibility requirements does not guarantee immediate access. OpenAI’s Wallet support documentation sets out these conditions:
| Requirement | Current availability |
|---|---|
| Subscription | Eligible ChatGPT Pro accounts |
| Location and age | U.S. residents aged 18 or older |
| Card | Eligible U.S.-issued American Express, Chase, Mastercard and Visa cards |
| Billing address | A U.S. billing address for the card |
| Conversation | A conversation with a dot, which must be set up first |
| Purchase approval | Biometric verification on a supported device |
Wallet is not available in Chat, Work or standalone Codex threads. Card eligibility also matters beyond the brand printed on the card: OpenAI specifies eligible cards, and adding an eligible Chase card requires being the primary cardholder, not an authorized user.
Users with access can ask their dot to add a card or open the Wallet section in Settings. Card details belong in the secure enrollment form, not in the conversation. A bank may require an additional verification step before the card becomes usable.
For Chase cards, OpenAI instructs users to install the Chase mobile app and sign in with biometrics. The connection is approved through that app; users starting on a computer can continue through a phone using a QR code.
That setup approval is separate from purchase approval. Verifying a card does not give the agent ongoing permission to spend. Wallet cards are also separate from the payment method used for a ChatGPT subscription and from any ChatGPT gift-card or prepaid balance.
How Approval and Tokenization Work
OpenAI’s documented flow has three distinct stages: the user authorizes a specific purchase, the payment network supplies a substitute credential, and the agent continues through the merchant’s checkout.
Review the Actual Purchase
Once the user has chosen what to buy, they ask their dot to complete the purchase. Wallet presents a request showing the relevant details.
The user should check:
- The merchant and items.
- The total amount.
- The selected card.
- Any shipping details or recurring-payment terms shown.
This is the consequential review step. A biometric check confirms approval, but the user still needs to inspect what they are approving. An incorrect item, unexpected total or recurring charge should be caught before authorization.
Approve With Biometrics
The user selects approval and completes biometric verification, such as Face ID or Touch ID. If the current device cannot handle that step, OpenAI provides a link or QR-code path to a supported device signed in to the same ChatGPT account.
OpenAI says each approval creates a record of the purchase the user authorized. The approval is tied to that transaction, not a general instruction to buy anything the agent considers appropriate.
Pay With a Substitute Card Credential
After approval, the payment network provides a payment token containing a card number, security code and expiration date. The agent uses that credential to complete checkout, and the charge goes to the selected underlying card.
The token’s familiar card fields matter: they allow the payment to work through existing checkout flows. The number entered at checkout can differ from the number on the user’s physical card.
According to OpenAI’s launch documentation, neither the agent nor the merchant receives the user’s actual card details. Wallet stores the card information, while the purchasing workflow uses the substitute credential.
My view is that this separation is the most useful technical detail in the launch. It lets the agent perform the checkout task without needing the underlying card credential. It does not, by itself, guarantee that a merchant will accept the payment or that an order will be fulfilled.
Confirm That the Merchant Placed the Order
After authorization, the dot continues checkout and reports the result. Approval and order placement remain separate events.
The Help Center makes that distinction explicit:
“Ready to check out means your approval is complete. It does not confirm that the merchant has placed your order.”
If the result is unclear, check for confirmation from the merchant before trying again. That is a practical safeguard against submitting another purchase when the first attempt’s outcome is uncertain.
Rewards and Dispute Protections Remain Conditional
OpenAI says users retain their card’s existing rewards and protections for eligible disputes, including qualifying problems such as defective items. Those are attributed product claims, not a promise that every transaction earns a particular reward rate or qualifies for a successful dispute.
The purchase remains a direct transaction between the customer and the business. Under the arrangement described in the announcement, merchants retain control over pricing and responsibility for fulfillment, returns and customer service.
That means the normal post-purchase relationship still matters. A customer who wants to cancel a completed order should contact the merchant. Wallet’s role in initiating payment does not transfer the merchant’s delivery or returns obligations to OpenAI.
Recurring Payments Need Particular Attention
The support documentation includes an important exception to a casual reading of “approval for every purchase.” If a user agrees to a recurring or continuous payment plan, the merchant may store the payment credential and charge it again under those agreed terms.
Those later merchant charges are different from a dot independently initiating new purchases. The initial Wallet approval can authorize an ongoing billing arrangement, so users should inspect subscription terms as carefully as the immediate total. Managing or canceling those charges requires contacting the merchant, according to OpenAI’s guidance.
Tokenization should therefore not be read as a guarantee that every credential disappears after one use. The documented recurring-payment behavior makes that assumption unsafe.
What Merchants Must Check Before Accepting Agents
OpenAI’s Commerce Partner Playbook, introduced alongside Wallet, describes changes across product discovery, website access and payment-risk handling. The announcement summarizes the guidance; it does not suggest that a single integration switch solves every acceptance problem.
Keep Product Information Current
Businesses can claim their presence in ChatGPT and, once verified, update their details and upload a product feed with current pricing and availability.
This helps agents find accurate information before reaching checkout. For a merchant, stale availability or pricing can create a failed purchase even when website access and payment processing both work.
A product feed is not a prerequisite for browser access, however. OpenAI explicitly says agents can access websites without a plugin or product feed. Businesses should distinguish improving discovery from enabling access.
Recognize Signed Agent Requests
OpenAI advises merchants to configure their content delivery network or firewall to recognize signed requests using Web Bot Auth, then check whether general site-security measures inadvertently block ChatGPT agents.
The practical implication is targeted recognition, not switching off bot protection. I’d treat agent identity and transaction risk as separate checks: recognizing a signed request helps establish which agent is accessing the site, while the purchase still needs the usual payment and fraud assessment.
This distinction matters because an agent can be acting on a real customer’s instructions while looking like automated traffic to a site’s defenses.
Coordinate With Payment and Fraud Providers
OpenAI says Wallet tokens work with existing checkout flows, but risk systems may still flag legitimate agent purchases. The result can be a decline or cancellation even after the customer has approved the transaction.
Merchants should ask their payment and risk providers how they identify and evaluate these purchases. OpenAI also says it is working with fraud-prevention partners, including Forter, Riskified and Sardine.
The useful operational lesson is that agent access and payment acceptance are separate failure points. Fixing a firewall rule will not necessarily fix a payment decline. Conversely, a compatible payment flow is irrelevant if the agent cannot reach checkout.
Based on those documented failure points, I’d split a readiness review into three questions:
- Can the agent reach the relevant product and checkout pages?
- Can checkout process the substitute card credential?
- Do payment and risk systems recognize legitimate agent-led purchases without unnecessary declines or cancellations?
That sequence is an analysis of OpenAI’s guidance, not a reported test result. The supplied documents describe intended compatibility and known obstacles; they provide no independent measurement of checkout success rates.
Autonomous Spending Is Still a Future Capability
OpenAI describes a future version in which users could delegate purchases within parameters such as spending limits, purchase categories or time periods. It says that would require enhanced safeguards building on biometric checks and authorization records.
That capability is not part of the current launch. Today, a user must review and approve each purchase initiated through Wallet.
The distinction changes how this product should be evaluated. ChatGPT Wallet currently removes the need to expose underlying card details to the purchasing agent and repeatedly enter them at checkout. It does not remove the user from the buying decision. For merchants, the immediate task is supporting a human-authorized purchase carried out by an agent, while preserving the checks that make the transaction trustworthy.
Frequently Asked Questions
4 questions
1Is ChatGPT Wallet Available to All Pro Users?
No. Access is rolling out gradually to eligible U.S. Pro subscribers aged 18 or older. It currently works in dot conversations and requires an eligible card and supported biometric approval.
2Does the Merchant Receive My Actual Card Number?
According to OpenAI, the merchant receives a substitute payment credential. The purchase is charged to the selected underlying card without sharing its actual details with the merchant or agent.
3Can My Agent Spend Within a Budget Without Asking?
Not in the current launch. OpenAI describes delegated purchasing with spending limits as a future capability. Current agent-initiated purchases require review and biometric approval.
4Do Merchants Need a ChatGPT Plugin?
OpenAI says browser access requires neither a plugin nor a product feed. Merchants should still check signed-agent access, checkout compatibility and payment-risk handling.