Finding a forgotten subscription and paying for a new purchase are different jobs. Two launches on 13 November put both inside AI assistants. OpenAI’s ChatGPT Wallet brings an agent to checkout; Google’s Wallet connection gives Gemini a view of spending. The useful question is what permission each job actually needs.

Based on 9 reviewed sources · See sources

The purchase still stops for you

ChatGPT Wallet begins rolling out through dots, OpenAI’s personal agents, to US ChatGPT Pro subscribers aged 18 or over with eligible US-issued cards. American Express, Mastercard and Visa are the launch partners. The user reviews the items, total and selected card, then completes a security check such as Face ID or a fingerprint scan.

After approval, the payment network supplies a token: substitute payment details that keep the underlying card details away from the agent and merchant. OpenAI describes fuller delegation using spending limits or purchase categories as a future direction. The launch still requires approval for each purchase.

From the source · ChatGPT ·

OpenAI’s original demonstration presents purchase approval and tokenised payment in dots. It is a vendor demonstration, not a checkout test by Marketer Fizz.

View the original post on X ↗

Eligibility does not guarantee immediate access. Riley Strong, who works on Wallet at OpenAI, said on 14 November that the rollout would proceed gradually over the coming days while the team monitors traffic with its bank and network partners.

The spending view opens a different door

Google’s launch covers all Gemini app users in the US, across web and mobile. Connecting Google Wallet lets the assistant answer questions about transactions, recurring charges or changes in subscription prices. Plaid supplies optional linking for bank accounts, credit cards, loans and investments.

Gemini can read this information, but cannot move, manage or invest the money. The connection can be turned off in Personal Intelligence settings. These are distinct permissions: access to spending history does not authorise a purchase, and purchase approval does not itself grant a view of someone’s wider finances.

From the source · Google ·

Google introduces spending questions and optional linked-account data. Its follow-up specifies read-only access; the announcement does not give Gemini authority to transfer money.

View the original post on X ↗
The detail

What the launches let the assistant do

Documented launch scope, checked 14 November 2026. Both consumer rollouts begin in the US.

What the launches let the assistant do. Documented launch scope, checked 14 November 2026. Both consumer rollouts begin in the US.
ServicePermission and starting access
ChatGPT WalletComplete a user-approved purchase in dots. Pro, age 18+, eligible US-issued card.
Google Wallet in GeminiRead connected spending information. All US Gemini app users; optional Plaid account links.
Different jobs, not a ranking. Neither announcement establishes a Belgian or wider European consumer rollout.Source: OpenAI launch; Google launch linked in the service row · 2026-11-14

Read-only still leaves a data question

Google’s Connected Apps guide makes an important distinction. It says models are not trained directly on the entire Wallet service, but activity can include transaction summaries, excerpts and inferences used for training when Keep Activity is on. A subset of processed information can also enter human review; Google describes reducing personal information and disconnecting interactions from the account before service-provider review.

Turning off the Wallet connection does not delete earlier Gemini Apps Activity. That activity has separate deletion controls, with limits once trained reviewers have already reviewed it. The read-only promise concerns moving money; the activity settings govern another part of the relationship.

Approval is one step in a completed order

OpenAI’s merchant guide says Wallet can use existing checkout pages without a Wallet-specific integration. It also warns that automated fraud systems can mistake the cloud browser for unwanted bot traffic and decline purchases. The merchant continues to handle the order, fulfilment, support and fraud decisions.

The guide limits consent to the specific transaction: its credential cannot be saved or reused for another purchase. Subscriptions need consent for recurring charges. The wider playbook distinguishes product discovery, browser or plugin actions, and the business’s confirmation of the result. A payment approval is therefore a checkpoint, rather than evidence that an order was accepted.

For European readers, both consumer launches remain US-specific. For merchants, the immediate issue is a changing path from recommendation to order, with familiar responsibilities still attached. We have not tested a completed purchase or linked a financial account, so reliability and conversion effects remain open questions.

Sources

Written with AI assistance from the sources above. Analysis and practical implications are our interpretation. Our editorial approach.