ChatGPT Wallet lets OpenAI’s Dots agents make purchases for you

OpenAI launched ChatGPT Wallet on November 13, 2026, introducing a dedicated payment system that allows its Dots artificial intelligence agents to make online purchases on behalf of users. According to details outlined in The Verge's report, the rollout begins for ChatGPT Pro subscribers located in the United States who meet specific age and banking requirements. The platform integrates payment card storage directly into the assistant environment so agents can act on commercial requests.

This breakdown details the eligibility rules, security architecture, tokenization safeguards, and current retailer constraints governing the new payment tool. It is written for ChatGPT Pro account holders, digital commerce developers, and enterprise teams evaluating autonomous purchasing workflows. Readers will find the full operating requirements, verification procedures, and merchant integration challenges without needing to consult outside summaries.

01ChatGPT Pro rollout and card eligibility

The new payment feature is accessible exclusively to ChatGPT Pro subscribers residing in the United States. Eligible users must be at least 18 years old and possess a verified domestic billing address. This geographic limitation restricts the initial deployment to active premium members while OpenAI tests transaction flows and fraud detection systems under real market conditions.

Card compatibility covers eligible domestic accounts issued across major banking networks. Supported options include "eligible US-issued American Express, Chase, Mastercard and Visa cards" linked to a qualifying account. Users connect these approved payment methods directly to the assistant profile before assigning automated purchasing tasks to their Dots assistants.

Account holders must configure their card credentials inside the ChatGPT settings panel to activate the checkout capabilities. Once the card profile is verified, Dots agents gain permission to stage transactions during interactive conversations. The service remains unavailable to standard subscribers, international accounts, or unsupported regional payment cards during this launch phase.

02Prompt purchasing and biometric verification checks

Dots agents initiate transactions after receiving direct user shopping prompts within the conversational interface. When a user requests an item, the agent searches for the product, locates the store listing, and prepares the checkout basket. The autonomous software cannot complete a transaction on its own and must pause the session to request explicit human confirmation.

OpenAI requires a security check for every transaction through biometric verification before any money changes hands. Users confirm the order details using biometric sensors such as Face ID facial recognition or fingerprint scans on their hardware devices. This mandatory approval step ensures that background conversational tasks do not execute unintended financial charges.

Every individual checkout action requires an interactive sign-off from the primary account owner. The support documentation confirms that agents will check in every single time an order is ready for submission. Buyers review the itemized cart, delivery details, and final price before authorizing the purchase with their physical sensor.

03Payment tokenization and credit card privacy

OpenAI substitutes sensitive account numbers with digital payment tokens rather than exposing raw card credentials to the web. This mechanism functions similarly to mobile payment architectures used in Apple Pay, Google Wallet, and standard tap-to-pay terminals. The underlying payment details remain encrypted within the infrastructure and are never exposed in conversational memory.

Neither the Dots agent nor the external merchant receives the customer's actual credit card number during checkout. The tokenized transaction transmits only an encrypted surrogate value to the merchant processing system to satisfy banking requirements. This isolation barrier prevents third-party online stores and model context logs from collecting sensitive customer financial records.

Shielding payment numbers reduces exposure risks across public and private shopping platforms. Because the AI model only handles masked authorization tokens, session logs remain free of sensitive account data. Merchants settle orders through standard payment gateways without storing permanent credit card profiles for automated agent sessions.

04Delegated spending limits and category controls

OpenAI plans to expand the wallet platform by allowing users to delegate purchases entirely to autonomous software agents. Under this planned framework, customers will define custom operational boundaries instead of manually authorizing every transaction. Agents will operate within strict boundaries established prior to executing procurement tasks across the web.

Eventually, OpenAI says it expects "users to be able to delegate purchases entirely to their agent by setting clear parameters—such as spending limits, purchase categories, or time periods—and pre-approve those purchases." Account owners will establish these rules in advance, allowing assistants to buy recurring supplies independently. These controls will let users define boundaries before activating unattended shopping routines.

These delegation parameters aim to balance autonomous task execution with personal financial control. Setting strict budget caps ensures that automated workflows cannot exceed authorized spending thresholds during unattended web research. OpenAI expects these controls to unlock hands-free agent operations once testing confirms reliable policy compliance across common retail scenarios.

05Retailer restrictions and anti-fraud merchant barriers

The new checkout functionality faces technical barriers because many commercial websites currently restrict or ban autonomous web agents. Earlier this year, Amazon blocked Meta's Muse agents from navigating and scraping its retail platform. Retail infrastructure providers frequently deploy automated defenses to protect checkout channels from unverified automated crawlers.

OpenAI says that in order for agents to use the wallet, "websites need to ensure agents are not inadvertently blocked, and payment and risk systems need to recognize legitimate purchases made by agents." Retailers and payment networks must configure rules to separate valid agent transactions from unwanted automated traffic. Without merchant accommodation, automated shopping orders risk triggering fraud alarms or checkout failures.

Risk management systems must learn to recognize agent-driven orders as valid financial requests. OpenAI emphasized that payment processing gateways need to update fraud assessment logic so legitimate tokenized transactions can clear. Broader adoption of automated shopping depends on retailers adjusting security perimeters to permit verified agent interactions.