Orbit: Card, wallet and commerce programs
ChatGPT Wallet
OpenAI's wallet for agents in ChatGPT, rolling out since 2026-11-13 in dots. The user approves every purchase with a biometric check, a payment token stands in for the card, and the dot pays on the merchant's existing checkout without the business or the agent seeing the card. As read 2026-11-21, OpenAI's post names American Express, Chase, Mastercard and Visa as partners.
- Steward
- OpenAI (company); its post names American Express, Chase, Mastercard and Visa as partners (as read 2026-11-21)
- Status
- Live in a limited rollout since 2026-11-13 (dots only, ChatGPT Pro, US)
- Latest version
- Launch in dots ()
- Primary source
- Introducing ChatGPT Wallet (external link)
What it is
is OpenAI’s way for an agent in ChatGPT to pay on a user’s behalf. OpenAI introduced it on 2026-11-13 and says it lets agents pay without access to the user’s actual card details while requiring a security check for every purchase. Source [1] As read 2026-11-21, the post says Wallet was built in partnership with American Express, Chase, Mastercard and Visa; its launch-day text and launch-day coverage named American Express, Mastercard and Visa only, and OpenAI did not mark the change. Source [1, 2] It launched in dots, the always-on agents OpenAI introduced on 2026-09-29, which live in the cloud with their own computer and browser. Source [3, 4] Wallet is not a new checkout protocol: the dot uses the merchant’s existing website checkout, and OpenAI’s merchant guide says no Wallet-specific integration is required. Source [1, 5]
How a purchase works
- The user adds a card once. Source [1]
- The dot finds the item and works through the merchant’s own checkout with its cloud browser. Source [1, 6] TechCrunch reported that, according to OpenAI, the merchant receives what it needs to fulfill the order, such as the shipping address and contact details, from the dot (reported). Source [7]
- Before paying, ChatGPT shows the items, the total and the selected card, and the user approves with a security check such as Face ID or a fingerprint scan. Each approval creates a record of the purchase the user authorized. Source [1]
- OpenAI’s post says the payment network then provides a , a stand-in for the card with its own card number, security code and expiration date, and that the card is charged without Wallet sharing the actual card details with the business or the agent. Source [1] OpenAI’s help article says the dot then uses a virtual card number linked to the selected card, so the number at checkout may differ from the physical card, and that Wallet generates a payment token for each use; CNBC also reported that the token is specific to the transaction (reported). Source [8, 9]
- The merchant’s checkout processes the payment like any card payment, and the business handles the order, fulfillment, customer support and fraud decisions. Source [5] When ChatGPT reports that a purchase is ready to check out, the approval is complete, but that does not confirm that the merchant placed the order, and Wallet may not complete checkout at every store. Source [8]
Users keep their card’s rewards and protections for eligible disputes, banks and networks evaluate the transactions, and businesses keep control of pricing, fulfillment, returns and customer service. Source [1] For help, OpenAI’s article sends users to the merchant for order status, cancellations, returns and refunds, to the card issuer for declined, disputed or unrecognized charges, and to OpenAI Support for Wallet errors or a purchase that differs from what they approved. Source [8] OpenAI says it expects, over time, to let users delegate purchases to their agent within spending limits, categories or time periods and pre-approve them with biometric checks and records of authorization. It gives no date, and on 2026-11-21 every purchase still needs the user’s biometric approval. Source [1, 8] The scenario From ChatGPT discovery to merchant checkout walks through the whole sequence, next to the plugin and paths.
Terms and data
OpenAI’s terms took effect on 2026-11-12. They make the merchant the seller and and say OpenAI is not a bank, card issuer, payment network, lender or merchant for Wallet purchases and holds no purchase funds. Source [10] OpenAI does not decide or fund merchant refunds or card chargebacks unless the law requires it or OpenAI separately promises otherwise, the cardholder agreement and issuer and network rules, including dispute rights, still apply, and OpenAI may set transaction, merchant, category, card, account, device or geographic limits. Source [10] After an approval, OpenAI may ask a payment service provider, card network or issuer to create or provide a tokenized, virtual or other credential linked to the card. Source [10] Under the Wallet Privacy Notice of the same date, a service provider collects the card number and security code, OpenAI receives a tokenized credential with limited card details, and OpenAI says it does not sell Wallet data or share it for targeted advertising. Source [11]
What merchants need
OpenAI published its Commerce in ChatGPT partner playbook alongside Wallet; it explains what a merchant can check, and browser access needs neither a plugin nor a product feed. Source [1, 12, 13]
- Let the cloud browser in. ChatGPT signs certain cloud browser requests with Web Bot Auth (OpenAI’s guidance covers these requests, not its web crawlers): a
Signatureheader, aSignature-Inputheader andSignature-Agent: "https://chatgpt.com", verified under RFC 9421 with keys fromhttps://chatgpt.com/.well-known/http-message-signatures-directory. Source [13, 14] Akamai, Cloudflare, HUMAN and Vercel verify these signatures automatically; the guide names the traffic ChatGPT Agent at Akamai and HUMAN,dots, OpenAIunder Personal Agents or bot tagchatgpt-agentwith detection ID129220581at Cloudflare, andchatgpt-operatorat Vercel. Source [13] As read 2026-11-21, the guide recommends adding ChatGPT’s agent profile to the firewall’s allowlist, while keeping other security controls in place, so that visits on a user’s behalf go through reliably, and verifying the signatures before applying an allowlist exception for signed requests. Source [13] That is advice, not a requirement: OpenAI’s companion page says to change settings only if security settings block verified visits, and a Vercel-hosted site whose rules do not block the traffic needs no extra configuration. Source [6, 13] On 2026-11-14 and again on 2026-11-21 the key directory held one Ed25519 key with an expiry a week ahead, so a verifier should fetch keys from it rather than hard-code them. Source [15] The Web Bot Auth page covers the Internet Engineering Task Force (IETF) working group behind the mechanism. - Accept the token in the existing checkout. The merchant receives a instead of the card number and can use the Payment Account Reference (PAR) to link it to the underlying account. Source [5] The customer consents to that one transaction, so the merchant must not reuse or save the credential for another purchase. Subscriptions need the customer’s consent for recurring charges and the processor’s merchant-initiated transaction practice, and Wallet sits beside any existing card-on-file flow. Source [5] OpenAI’s help article adds that if the user agrees to a recurring plan, the merchant may store the credential and charge it again under those terms. Source [8]
- Tune risk systems. Risk systems built to catch bots can flag legitimate agent purchases and decline or cancel them. Source [1, 5] OpenAI is rolling out user signals in the
Forwardedheader:asn,for(the IP address observed for the user),ip-country,ip-prefix,locale,tzanduser-agent. Source [5] Of these seven, onlyforis in the Internet Assigned Numbers Authority (IANA) registry of Forwarded parameters, RFC 7239 warns that any node on the path can change the header, and OpenAI does not say whether its signatures cover it. Source [13, 16, 17] The header also passes the shopper’s IP address, network, country, locale and time zone to the sites that receive it. Source [5]
OpenAI’s agent access FAQ adds that site owners cannot yet control which actions users take, that OpenAI requires human review before any consequential action, and that customers are ultimately responsible for the actions they take. The last point is OpenAI’s position, not a card network rule. Source [13] For plugins, OpenAI says it is still working on how third-party plugins and Wallet interact. Source [18]
Partners and availability
- Card networks and a card issuer. As read 2026-11-21, OpenAI’s post names American Express, Chase, Mastercard and Visa as Wallet’s partners. Its launch-day text, as captured at 2026-11-13T16:04:07Z, and launch-day coverage named American Express, Mastercard and Visa, and OpenAI did not mark the change. Source [1, 2] Chase takes part as a card issuer: OpenAI’s help article lists eligible Chase credit cards, accepts them only from the primary cardholder, not an authorized user, and has the user approve the connection in the Chase mobile app, by QR code when starting on a computer. Source [8] The post’s quotes come from American Express, Mastercard and Visa executives, and Chase appears only in the partner sentence. Source [1] OpenAI’s post quotes American Express’s Luke Gebb calling Wallet the first American Express Agentic Commerce Experiences (ACE) integration, but American Express itself had published nothing on Wallet as of 2026-11-21, so that status rests on OpenAI’s post (reported). Source [1, 19] Apart from that quote the post names no card network program. Source [1] Mastercard’s CEO said on 2026-10-29 that a broad partnership with OpenAI includes the use of Mastercard Agent Pay (reported), and Visa announced an OpenAI collaboration under Visa Intelligent Commerce on 2026-06-10, but no source says which program issues Wallet tokens. Source [1, 13, 20, 21]
- Fraud and payment partners. OpenAI names Forter, Riskified, Sardine and Signifyd among its fraud prevention partners and Adyen, Checkout.com and Stripe among its payment service providers, as examples rather than complete lists. Source [1] Forter says it identifies ChatGPT agent traffic for each Wallet transaction and feeds that into its fraud decisions, and Signifyd says it works with OpenAI so that legitimate agent orders are not declined. Source [22, 23]
- Who can use it. Wallet began rolling out on 2026-11-13 in dots, initially for ChatGPT Pro subscribers in the US aged 18 and older with eligible US-issued cards. Source [1] OpenAI’s help article (updated 2026-11-19) says it works in conversations with a dot, which the user sets up first: “Wallet isn’t available in Chat, Work, or standalone Codex threads.” Approving a purchase requires biometric verification, such as Face ID or Touch ID, on a supported device. Source [8] Eligible cards are US-issued American Express, Chase, Mastercard and Visa cards, and the user must live in the US and have a US billing address for the card. The bank may ask to verify the card during setup, some US-issued debit cards work but Chase debit cards do not, and virtual cards cannot be added at launch. Source [8] The dots-only limit was already reported on launch day (reported), while the post’s own page description and OpenAI’s RSS summary still name agents in ChatGPT Work, Codex and dots (as read 2026-11-21). Source [1, 2, 24] OpenAI’s Enterprise guide says Wallet is off by default for Enterprise workspaces and that admins will be able to grant a Use Wallet once the setting is available; it gives no date. Source [25]
- Fees. OpenAI’s post, help article and partner playbook state no fee for Wallet purchases, and CNBC reported that OpenAI is not taking a cut of transactions to start (reported). Source [1, 8, 9, 12]
What it is not
- Not the Agentic Commerce Protocol (ACP). OpenAI’s Wallet post and its partner playbook do not name ACP, and the post never mentions , or Shared Payment Tokens. Source [1, 12] OpenAI’s post says the payment network provides the token, and the Wallet terms let OpenAI ask a payment service provider, card network or issuer for the credential; none of these sources names an ACP Delegate Payment vault or a Stripe . Source [1, 10] OpenAI’s merchant page still says ChatGPT shopping is built on ACP, which supports product discovery today. Source [26]
- Not Instant Checkout. OpenAI’s plugin guidelines use that name for the , a beta for select marketplace partners that a plugin opens from its own interface. Source [27, 28, 29]
- Not Visa’s Trusted Agent Protocol (TAP) or Mastercard’s agent signature. ChatGPT identifies itself with plain Web Bot Auth and the
Signature-Agentvalue"https://chatgpt.com", and OpenAI’s docs do not mention TAP’sagent-browser-authandagent-payer-authtags or Mastercard’sAgent-pay-authtag. Source [13, 30, 31] - Not a merchant integration project. OpenAI says no Wallet-specific integration is required. Source [5]
- Not autonomous yet. OpenAI’s help article and dots controls page require a biometric approval for each payment, and the post describes delegated purchases as a future expectation without a date. Source [1, 8, 32] The Wallet terms, effective 2026-11-12, already provide for a user granting ChatGPT the authority to approve each purchase in advance, while those product pages still require the biometric approval each time. Source [8, 10]
How it relates to the eight
ACP shares a steward with Wallet, since OpenAI and Stripe are its founding maintainers, but OpenAI documents no role for ACP in Wallet. Source [1, 12, 33] Mastercard and Visa are among Wallet’s named partners, yet no source ties it to Mastercard Agent Pay or Visa TAP, and ChatGPT’s request signatures do not use either network’s tags. Source [1, 13, 30, 31] No relation to x402, the Machine Payments Protocol, the Universal Commerce Protocol, the Agent Payments Protocol or ERC-8004 is documented in OpenAI’s post or commerce docs. Source [1, 12]
Status history
- 2026-09-29: OpenAI introduces dots, always-on agents with their own computer and browser in the cloud. Source [3, 4]
- 2026-11-10: OpenAI introduces Businesses in ChatGPT in beta; its partner playbook of 2026-11-13 sends merchants to Business Hub to claim a profile and, after identity verification, upload product feeds. Source [34, 35, 36]
- 2026-11-12: the terms and the Wallet Privacy Notice take effect. Source [10, 11]
- 2026-11-13: ChatGPT Wallet introduced; it begins rolling out in dots for US ChatGPT Pro subscribers, and OpenAI publishes the Commerce in ChatGPT partner playbook. Source [1, 12]
- 2026-11-19: OpenAI updates its Wallet help article without a change note. As read 2026-11-21 it accepts some US-issued debit cards, though not Chase debit cards, without saying since when. Source [8] Chase cards among the eligible cards, the dots-only limit and the bar on adding virtual cards were already reported on launch day (reported). Source [2]
Relations at a glance
| Protocol | Relation | Note |
|---|---|---|
| Agentic Commerce Protocol (ACP) | Same steward | OpenAI maintains ACP with Stripe, but neither its Wallet post nor its commerce docs name ACP, and the Wallet payment credential is not an ACP delegated payment or a Shared Payment Token. OpenAI's merchant page still says ChatGPT shopping is built on ACP (read 2026-11-21). |
Sources
- Introducing ChatGPT Wallet (external link)
- OpenAI launches ChatGPT Wallet, allowing AI agents to make purchases on your behalf (external link)
- Meet dots (ChatGPT documentation) (external link)
- OpenAI News RSS feed (read 2026-11-14) (external link)
- Accept payments (Commerce in ChatGPT, OpenAI developer docs) (external link)
- Help ensure cloud browser access (Commerce in ChatGPT, OpenAI developer docs) (external link)
- ChatGPT's new Wallet lets AI agents shop and check out for you (external link)
- Making purchases with ChatGPT Wallet (external link)
- OpenAI launches ChatGPT Wallet, allowing its 'dots' AI agents to make purchases for users (external link)
- ChatGPT Wallet terms (external link)
- ChatGPT Wallet Privacy Notice (external link)
- Partner Playbook Overview (Commerce in ChatGPT, OpenAI developer docs) (external link)
- Help ensure cloud browser access to your site (Commerce in ChatGPT, OpenAI developer docs) (external link)
- RFC 9421: HTTP Message Signatures (external link)
- ChatGPT HTTP message signatures key directory (external link)
- Hypertext Transfer Protocol (HTTP) Parameters: HTTP Forwarded Parameters registry (external link)
- RFC 7239: Forwarded HTTP Extension (external link)
- Build a plugin (Commerce in ChatGPT, OpenAI developer docs) (external link)
- American Express newsroom: all news (external link)
- Mastercard (MA) Q3 2026 Earnings Call Transcript (external link)
- Visa Partners with OpenAI to Power the Next Generation of AI Commerce (external link)
- Working with OpenAI on Trusted Agent Checkout (external link)
- Signifyd collaborates with OpenAI to help protect ChatGPT Wallet transactions (external link)
- OpenAI News RSS feed (read 2026-11-21) (external link)
- Manage dots permissions and capabilities (ChatGPT Enterprise documentation) (external link)
- Power product discovery in ChatGPT (OpenAI merchant page) (external link)
- Plugin guidelines (ChatGPT plugins): commerce, prohibited goods and checkout (external link)
- Checkout API reference (ChatGPT plugins, formerly the Apps SDK): external checkout, saved payment methods and the ChatGPT payment sheet (external link)
- Add UI to your MCP server (ChatGPT plugins): components, extensions and checkout in the plugin UI (external link)
- Trusted Agent Protocol merchant specifications (external link)
- Level 1 Agentic Commerce: Enable Agent Support with Minimal Changes (external link)
- Control your dot (ChatGPT documentation) (external link)
- Agentic Commerce Protocol (ACP) Governance (external link)
- Introducing Businesses in ChatGPT (external link)
- Submit product feeds (Commerce in ChatGPT, OpenAI developer docs) (external link)
- Setting up your business on ChatGPT (external link)
- ChatGPT release notes (external link)