Agents at Checkout: ChatGPT Wallet and the New Trust Problem in Agentic Payments
Agents are reaching the payment step. The harder question is not whether they can check out—it is who approves, and what the agent is allowed…

Shopping agents used to stop at a shortlist. On 13 November 2026, OpenAI published Introducing ChatGPT Wallet, a product that lets a ChatGPT dot complete a purchase after the user reviews the items, the total, and the selected card, then approves with a security check such as Face ID or a fingerprint scan. OpenAI says the payment uses a network payment token, so the user’s actual card details are not shared with the business or the agent, and that the product was “built in partnership with American Express, Mastercard, and Visa.”
That is a concrete move into agentic payments. The same day, Google launched a very different Wallet feature in the Gemini app—one that answers questions about spending and cannot move money. SpaceXSI’s Grok Bot, in official product documentation rather than a same-week launch post, already describes a checkout path of its own, with Vault-stored cards, order cards, and connected wallets.
The three approaches differ on how authorization works, what the agent can see, and who can use the feature, and each vendor has published its own account of those points. Google’s Gemini integration, for its part, is a read-only finance tool rather than an agentic payment product. The broader productization of always-on assistants such as dots and Grok Bot is covered in Always-On Agents Arrive: Claude Duet, Muse Wonder, Perplexity Teammates, and Grok Bot.
ChatGPT Wallet: a token, and a check on every purchase
OpenAI’s 13 November announcement describes a tight loop. The user adds a card once. Before each purchase, the user “reviews the items, total, and selected card, then approves it with a security check such as Face ID or a fingerprint scan.” After that approval, “the payment network provides a payment token—a substitute for the user’s actual card details—with a card number, security code, and expiration date.” The charge lands on the selected card, OpenAI says, “without ChatGPT Wallet sharing their actual card details with the business or agent.”
The company’s headline claim should be labeled as such. OpenAI calls ChatGPT Wallet “the first wallet that lets agents pay without access to users’ actual card details and that requires a security check for every purchase, while also preserving existing card rewards and protections for eligible disputes.” That sentence is OpenAI’s, dated 13 November 2026. Neither the “first” claim nor the scope of those rewards and protections has been independently verified.
OpenAI’s Help Center article Making purchases with ChatGPT Wallet, fetched on 16 November 2026, fills in the operational detail. Card numbers, expiration dates, and security codes are entered in a secure form, “not in chat.” After approval, the Help Center says, “your dot uses a virtual card number linked to your selected card to complete checkout,” and “the number entered at checkout may differ from the number on your physical card.” A status of “Ready to check out” means approval is complete; “It does not confirm that the merchant has placed your order.” Users are told to check for a merchant confirmation before trying again. If they agree to a recurring or continuous payment plan, “the merchant may store the payment credential and charge it again under the terms you agreed to.”
OpenAI also describes a later step it has not shipped as a default. “Over time,” the 13 November post says, the company 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.” That is a stated expectation, not a feature in the launch.
Who can use ChatGPT Wallet today
Availability is narrow, and OpenAI says so in both the announcement and the Help Center. The wallet “begins rolling out today in dots,” initially to “ChatGPT Pro subscribers aged 18 and older in the US with eligible US-issued cards.” The Help Center adds that even eligible U.S. Pro users “might not have access yet,” that Wallet “isn’t available in Chat, Work, or standalone Codex threads,” and that approving a purchase “requires biometric verification, such as Face ID or Touch ID, on a supported device.” Eligible cards, it says, are “US-issued American Express, Chase, Mastercard and Visa cards.” The user must be 18 or older, live in the United States, and have a U.S. billing address. For a Chase card, the user “must be the primary cardholder, not an authorized user.” The Help Center’s FAQ states two further limits at launch: “ChatGPT Wallet doesn’t support debit cards,” and “Virtual cards are not supported at launch.” It also says Wallet “may not be able to complete checkout at every store.”
Those constraints make the launch a bounded experiment, not a general-purpose checkout layer. OpenAI’s launch post is frank about the merchant side of that problem. “Some sites may unintentionally block purchases through ChatGPT Wallet or other agentic payment products.” Alongside the wallet, OpenAI says it is publishing a Commerce Partner Playbook covering product information, agent access, and payment-and-risk systems. The post names several of the issues businesses are asked to address: configuring a CDN or firewall to recognize signed requests using Web Bot Auth, and working with payment and risk providers so legitimate agent purchases are not declined. It also lists fraud-prevention and payment-service partners “to help their systems recognize legitimate purchases made by agents.” Those are OpenAI’s statements about its partner program, not evidence of how often checkouts currently succeed.
Google Wallet in Gemini is read-only
The same calendar day can be misleading. On 13 November 2026, Google published Connect Google Wallet to Gemini for personal finance insights. The feature is rolling out “for all Gemini app users in the U.S.” Users can connect Google Wallet and, optionally, “securely link your financial accounts from your credit cards and banks to Wallet via Plaid.” In the Gemini app they can tag @Google Wallet and ask about spending, subscriptions, and budgets.
Google’s control section is unambiguous: “If you choose to connect your Wallet (under Connected Apps in Personal Intelligence settings), Gemini can only read information from your accounts; it can’t move, manage, or invest your money.” The connection is opt-in and can be turned off at any time.
That is a finance-insights feature, not an agentic payment rail. It belongs in this article only as a boundary: as of the official post, Gemini cannot pay.
Grok Bot’s checkout path, as the official docs describe it
SpaceXSI did not publish a wallet launch post in the week of 9–16 November 2026. What it does publish is product documentation for Grok Bot. The description below is limited to those pages.
Vault and secure sign-in says Vault holds logins, cards, and contact information “so your Bots can sign in to websites and check out for you without seeing your passwords.” A Bot “never sees a saved password.” Contact information and which logins were saved are visible to the Bot, so it can pick the right entry. Cards are treated differently in one important respect. The same page says: “In chats in the Grok Bot app, a Bot can also see a saved card’s number and security code. It types them into a checkout after you tap Pay on the order card, and tells you a card’s details when you ask.” The approvals documentation repeats that the Bot can see those details “so it can type them at checkout.”
Authorization follows a different default from ChatGPT Wallet. Vault’s “Pay for things” section states: “A card saved in Vault fills in at checkout without asking you each time, and no setting requires your approval for each use.” The documented way to approve every payment yourself is not a toggle; it is to avoid saving the card. Users are told to leave “Securely save to Bot’s vault” unchecked on a Secure Form at checkout, or to remove a card already saved in Settings → Vault. A Secure Form, the same page says, fills values “straight into the page” and they “are never shown to the Bot.” If a card is entered on a Secure Form and not saved, “the card is used only in that chat.” When a Bot buys something through an order card and no card is saved, “the Bot first asks for a card with a Secure Form.” If that card is not saved, “the card gets no order card; the Bot asks you to approve the exact total in the chat instead.”

The order card itself is described in Message and collaborate, in the section “Shop with a Bot.” When the user is ready to buy, “the Bot sends an order card with the store, the items, Ship to, Pay with, and the Total.” A gift order adds a Gift row. The user is told to check those fields, then “choose the pay button, which shows the total, or choose Cancel.” “If you cancel, nothing is charged.” “Only a Bot’s owner can pay its orders.” If the order card expires, the same page says, “ask the Bot to check the price again.” SpaceXSI’s Grok Bot changelog entry dated 11 November 2026 confirms a matching product change: “An expired order card offers Check price again, which asks the Bot for a fresh order card.”
Vault also lists connected payment accounts. The documentation names wallets “you can connect, such as Link, X Money, or Shop Pay,” plus a “Default payment method, which Grok Bot pays with first.” A Bot “can also send one order card for a batch of up to 500 card payments, paid with a saved card.” After approval, “the Bot makes the payments one at a time and stops if a card is declined,” then reports what was paid and what failed. “One approval covers payments for 24 hours; after that, the Bot sends a new order card for the rest.” “Wallets such as Link or X Money need one order card per payment, and a batch ships to one address.” With Link connected, a Bot can ask the user to approve a one-time card for a single purchase; after Pay, authorization is finished on the Link page that opens, and “Nothing is charged if you decline or the request expires.”
Two scope limits in the same Vault page are part of the trust picture. “Vault covers your whole account: everything you save is available to every Bot on your account, and you can’t limit an item to one Bot.” And “Your Vault isn’t available on Team Bots: a Team Bot can’t use the logins, cards, or contact info you saved.” A Team Bot can have logins of its own, added by an owner or manager.
None of that documentation frames the flow as a network payment token hidden from the agent. It describes a checkout path in which a saved card can be reused without a fresh approval, an order card or chat total is the control point when one is shown, and, in Grok Bot app chats, a saved card’s number and security code are visible to the Bot.
Three questions, three published answers
The useful comparison is not “which wallet is safer.” It is what each official page actually says about the same three questions.
Authorization. OpenAI’s Wallet requires the user to review the purchase and pass a biometric check on every payment, at launch; pre-delegated spending is described as a future expectation. Google’s Gemini integration has no payment authorization step, because Gemini cannot move money. Grok Bot’s docs say a card saved in Vault fills in at checkout without a per-use approval setting; the documented way to require approval every time is to keep the card out of Vault, and to use the order card’s Pay or Cancel buttons, or a chat approval of the exact total, when those flows apply.
What the agent sees. OpenAI says ChatGPT Wallet does not share the user’s actual card details with the agent or the business, and that checkout uses a payment token or virtual card number. Card details, the Help Center says, are entered in a secure form, not in chat. Google’s Gemini feature can read connected Wallet and, if linked, bank and card account information, and cannot transact. SpaceXSI’s docs say a Bot never sees a saved password, that Secure Form values are not shown to the Bot, and that in Grok Bot app chats a Bot can see a saved card’s number and security code in order to type them at checkout and to recite them when asked.
Availability. ChatGPT Wallet is rolling out to eligible U.S. ChatGPT Pro users, 18 or older, with eligible U.S.-issued credit cards, in dots only, and not at every store. Google’s Wallet connection is for all Gemini app users in the United States, as a read-only personal-finance feature. Grok Bot’s checkout documentation describes product behavior for Bots that shop and pay; the pages fetched for this article do not state a country-by-country payments eligibility list comparable to OpenAI’s Help Center, and no such list is invented here.
Those are differences in published design, not a score. The trust problem in agentic commerce is not that agents have reached the payment form. It is that “the agent paid” can now mean three incompatible things: a tokenized charge the agent never saw, after a biometric check; a read-only look at a spending history; or a checkout completed with a saved card, under the approval rules the vendor has actually written down. The only reliable way to tell them apart is to read those rules, dated and in the vendor’s own words, before any agent is allowed near a total.
References
- Introducing ChatGPT Wallet — OpenAI, 13 November 2026; payment-token flow, per-purchase security check, Amex / Mastercard / Visa partnership, U.S. Pro / dots availability, Commerce Partner Playbook, future delegated-purchase expectation.
- Making purchases with ChatGPT Wallet — OpenAI Help Center, fetched 16 November 2026 (the page displayed a relative “Updated” stamp, not a calendar date); eligibility, biometric approval, secure form, virtual card number, “Ready to check out” is not a merchant confirmation, debit and virtual-card limits, support paths.
- Connect Google Wallet to Gemini for personal finance insights — Google, 13 November 2026; U.S. Gemini app availability, Plaid option, read-only restriction (“can’t move, manage, or invest your money”).
- Vault and secure sign-in — SpaceXSI Docs, fetched 16 November 2026 (no calendar “last updated” date on the fetched page); Vault contents, card visibility in the Grok Bot app, saved-card checkout without per-use approval, Secure Forms, Link / X Money / Shop Pay, batch payments, Team Bot scope.
- Message and collaborate — SpaceXSI Docs, fetched 16 November 2026 (no calendar “last updated” date on the fetched page); “Shop with a Bot,” order-card fields, Pay / Cancel, owner-only payment, expired order card.
- Approvals, security, and privacy — SpaceXSI Docs, fetched 16 November 2026 (no calendar “last updated” date on the fetched page); saved-card number and security code visible in Grok Bot app chats; saved card fills in without a separate approval each time.
- Grok Bot Changelog — SpaceXSI, entry dated 11 November 2026; “An expired order card offers Check price again, which asks the Bot for a fresh order card.”
Images: original illustrations generated for AndBeyond.Tech; no logos or real people depicted.
