Field noteNov 14, 20266 min read1 source

OpenAI is introducing ChatGPT Wallet

In one minute

OpenAI is introducing ChatGPT Wallet, which lets an agent make purchases without exposing a user’s actual card details and requires the user to approve each purchase with a security check. The limited US rollout pairs a new payment flow with merchant guidance on product data, agent access and fraud controls—an early test of how agent commerce fits existing systems.

What happened

OpenAI announced ChatGPT Wallet on November 13, 2026. It is initially rolling out through dots, a ChatGPT agent, to ChatGPT Pro subscribers aged 18 or older in the United States who have eligible US-issued cards. OpenAI says the launch is limited so it can learn from real-world use and work with businesses, banks and payment networks on compatibility and reliability. It gives no price for the wallet beyond the Pro subscription requirement.

The payment flow starts with a user adding a card once. Before every purchase, the user reviews the items, total and selected card, then approves the transaction through a security check such as Face ID or a fingerprint scan. OpenAI says each approval creates a record of the purchase the user authorized. After approval, the payment network supplies a payment token—a substitute for the actual card details, with a card number, security code and expiration date. The charge goes to the selected card; the wallet does not share the actual card details with the business or agent.

OpenAI says users retain their card’s existing rewards and protections for eligible disputes with businesses, such as a defective item. The customer transacts directly with the business, which keeps control of pricing, fulfillment, returns and customer service. American Express, Mastercard and Visa are named as partners. OpenAI also says it is working with fraud-prevention companies Forter, Riskified, Sardine and Signifyd, and payment service providers Adyen, Checkout.com and Stripe, to help distinguish legitimate agent purchases from risky transactions.

The accompanying Commerce Partner Playbook outlines ways businesses can prepare. OpenAI recommends keeping business details and product feeds current, allowing ChatGPT agents to access websites rather than inadvertently blocking signed requests, and talking with payment and risk providers about declines or cancellations. Browser access does not require a plugin or product feed. Businesses can also build plugins for actions such as checking availability or managing carts, or add WebMCP tools. OpenAI says wallet tokens work with existing checkout flows, though risk systems may still flag agent purchases.

OpenAI describes fully delegated purchases as a future direction, not a current capability. It expects users may eventually set parameters such as spending limits, purchase categories or time periods and pre-approve purchases with enhanced safeguards, including biometric checks and clear authorization records.

What the archive adds

New Runtime’s earlier coverage reported OpenAI’s November 13 ChatGPT Wallet launch, including per-purchase checks and tokenized payments for US ChatGPT Pro subscribers. This announcement adds merchant-facing guidance and more detail on the purchase flow; it is a new fact on a known story, not a wholly new event.

Trend signal

This supports agent-ready software exposing capabilities: OpenAI frames agent commerce as a combination of accessible product information, permitted website access and composable actions such as cart management, rather than payment alone. The pattern is only partially demonstrated here; the announcement describes a rollout and merchant recommendations, not measured adoption or a broadly settled integration standard.

Why now

OpenAI says 1.2 billion people use ChatGPT each week and that many already use it to research products, compare options and decide what to buy. Wallet is its step toward completing those purchases, while the limited rollout gives the company and payment partners time to assess compatibility and reliability with businesses.

Connections to other events

New Runtime’s earlier coverage described Stripe Link Wallet for Agents as a proxy between an agent and real payment credentials. OpenAI’s announcement similarly separates the agent from the actual card number, but specifies approval for each purchase at launch and names the card networks involved. The products should not be treated as identical: their respective flows and availability may differ.

Why it matters

For merchants, an agent’s ability to browse and submit a checkout is not enough if a firewall blocks it or a risk provider treats the transaction as suspicious. OpenAI’s playbook makes those operational dependencies explicit: product data must be current, access must be deliberate, and payment systems must recognize an authorized agent purchase. Teams can use the guidance as a checklist for assessing their current storefront and provider relationships, without assuming that they need to rebuild checkout.

For builders, tokenization and a recorded user approval illustrate a boundary between delegated action and payment authority. The current design leaves a person in the loop for every purchase, which limits convenience but provides a clear authorization point. The more autonomous model OpenAI describes—pre-approved categories, spending caps or time windows—would make policy design and auditing more consequential. It is a stated future direction, not a capability teams can rely on today.

Limits and uncertainty

The rollout is restricted to eligible US ChatGPT Pro users, and OpenAI does not report transaction volume, approval or decline rates, fraud outcomes, merchant adoption, or how many businesses can currently accept wallet purchases. It does not quantify the effect of agent traffic on existing checkout systems. The announcement describes future delegated purchasing in general terms and does not specify launch dates, detailed controls or an independent evaluation of the safeguards. The payment partners’ participation does not by itself establish broad compatibility across merchants or cards.

Skill to build now

If you operate an online store, test whether your CDN or firewall inadvertently blocks signed requests from ChatGPT agents, then review one checkout journey with your payment and risk providers. Compare how a legitimate agent-initiated purchase is identified against a normal purchase and document where it might be declined. OpenAI’s playbook also points to a low-cost first step: verify product details and pricing before building a plugin or changing checkout.

Reader takeaway

ChatGPT Wallet launches with a human approval for every purchase and tokenized card details, while OpenAI asks merchants to prepare their data, access controls and risk systems. The immediate opportunity is not hands-off agent spending: it is making existing commerce systems able to recognize and process authorized agent activity.

Evidence / sources

  1. 1openai.com/ru-RU/index/introducing-chatgpt-wallet
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicSecurityExplore the security topic hub.
  2. 02archiveField NotesOpen the latest editorial analysis.
  3. 03sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract