Last week, agents gained new ways to pay your store. OpenAI started rolling out ChatGPT Wallet. Mastercard and partners completed a live agent flight booking. Rain launched scoped cards from a pre-funded vault. None of them asks you to build a new checkout. All of them can still fail if your site blocks the agent or your fraud rules treat it as a bot.
The useful question is not which wallet wins. It is: when an agent pays, who is the customer actually checking out with? You can stay the merchant of record and still not hold the card or run the approval screen.
Three words worth defining
- Network token. A substitute card number, security code and expiry issued by the card network. It charges the real card without giving the store or the agent the real card details.
- Merchant of record. The business the customer is buying from — the one that takes the payment, fulfills the order, and handles returns and support.
- Scoped card. A virtual card issued for one job, limited by amount, merchant and expiry. Then it stops working.
The layers in one purchase
These are not rival products. A single payment can use more than one layer.
| Layer | What it does | Examples in use now |
|---|---|---|
| Discovery and permissions | How an agent finds you and proves who it is | Feeds and Business Hub; Web Bot Auth; Visa Trusted Agent Protocol; Poppy |
| Checkout session | How the cart is built and completed | Your website, via Wallet or a plugin; UCP checkout on Google AI Mode or Gemini |
| Proof of intent | Evidence the user authorized this purchase | Wallet biometric approval; Mastercard Verifiable Intent; AP2 mandates |
| Money movement | How the funds actually move | Network token; Google Pay or Shop Pay in UCP; a Rain scoped card |
Four ways an agent can pay you right now
1. A platform wallet on your existing checkout. A US ChatGPT Pro user asks their dot to find a sweater and pay. They review the items, total and card, approve with Face ID or a fingerprint, and a network token is issued. The dot completes checkout on your website.
2. A network token, with you still running the payment. On 12 November, Booked AI booked a live flight through Travelport. The traveler approved the fare and amount, Mastercard Agent Pay paid with a token, card details stayed in Basis Theory’s vault, and the airline stayed the merchant. If details had not matched the approved intent, the payment would not have gone through.
3. A checkout session inside an AI surface. A shopper in Google AI Mode or Gemini buys through a UCP checkout session. You remain the merchant of record. PayPal’s Agent Ready docs (13 October 2026) describe payment via Google Wallet, with a single-use token you process through Braintree or PayPal. That is a checkout method on a Google shopping surface, not the Gemini insights connection, which cannot move money.
What about buying inside ChatGPT? OpenAI’s merchant page, under “Can users buy directly inside ChatGPT?”, says it is “moving away from a standalone Instant Checkout experience” and that purchases are completed on merchant sites or apps. The Partner Playbook now points to browser use or a plugin, with Wallet for payment. Former Instant Checkout developer URLs now redirect to the Wallet accept-payments guide. ACP is still described as discovery infrastructure today, and Stripe still documents the protocol. PayPal’s 13 October overview still mentions instant checkout in ChatGPT Apps; that may lag. We are not treating standalone Instant Checkout as a current consumer path.
4. A scoped card from a funded vault. Rain Agent Vaults (10 November) let an agent platform fund a vault and issue a scoped Visa or Mastercard card for one purchase — amount, merchant and expiry fixed, then retired. You see an ordinary card payment and do not need to accept stablecoins. Rain says it is enabling Visa Intelligent Commerce and Mastercard Agent Pay; that wording is forward-looking.
| ChatGPT Wallet | Agent Pay flight booking | UCP checkout (Google AI Mode / Gemini) | Rain Agent Vaults | |
|---|---|---|---|---|
| Who runs approval | Shopper, in ChatGPT, every purchase, with a biometric check | Traveler, for that fare and amount; Verifiable Intent binds approval to the payment | Shopper, on the Google AI surface, via the payment handler | Vault owner, via rules in the partner’s app; Rain enforces limits at authorization |
| Who holds the credential | OpenAI stores the card; network issues a token after approval | Card in Basis Theory’s PCI vault; agent never saw the number | Handler; PayPal describes a single-use Google Pay token | Rain issues a scoped, typically single-use card from the partner vault |
| Who is merchant of record | You, per OpenAI (pricing, fulfillment, returns, support, fraud decisions) | Airline, in this demo | You, per Google; you keep customer data and post-purchase | You, accepting a normal card payment |
| What the store receives | Network token, not the full card number. Use PAR; do not reuse | Tokenized credential on existing rails | Payment-handler token, via Google Pay / PayPal / Braintree where enabled | Ordinary Visa or Mastercard authorization |
| What the store must do | No Wallet-specific integration. Allow verified ChatGPT browser visits; check risk rules will not decline a legitimate agent purchase | Merchant processed the payment itself in this demo. Typical-retailer onboarding was not in the sources we opened | Implement UCP or use a platform default (Shopify: UCP is on by default); enable a payment handler | Accept Visa and Mastercard, as you already do |
| Status / availability | Rolling out to US Pro users, 18+, eligible US-issued cards, dots only. Help pages: no debit or customer virtual cards at launch | Completed live booking, not a general launch. No typical-store sign-up path in the announcement | Native checkout on AI Mode and Gemini web (app “coming soon” on the page we opened); waitlist still mentioned | Sold to agent platforms, not a mass consumer app. Rain cites 175 million Visa/Mastercard locations |
Not a wallet
Two easy mix-ups:
Google Wallet in Gemini (13 November, US Gemini app users) lets people connect Wallet, and optionally bank or card accounts via Plaid, so Gemini can answer spending questions. Gemini can only read this information; it cannot move money. That is separate from Google Pay as a UCP payment handler, which is a way to pay on Google’s shopping surfaces.
Poppy 1.0 (13 November) is an identity and permissions layer. A company publishes /.well-known/poppy.json so an agent can identify itself and learn what it may do. Shopify now publishes a Poppy file for every store by default. Meta’s Muse looks for it first on every site. Sierra’s split: Poppy handles arrival; UCP handles products, cart and checkout. Poppy does not move money.
Who owns the customer?
“You stay the merchant of record” is true in every live shape above. It does not tell you who runs the yes/no moment, who stores the card, or who the customer talked to first.
| ChatGPT Wallet | Agent Pay flight demo | UCP + Google Pay | Rain Agent Vaults | |
|---|---|---|---|---|
| Merchant of record | You, per OpenAI | The airline | You, per Google | You, as the card-accepting store |
| Approval UX owner | ChatGPT | The Booked AI conversation, with Mastercard Verifiable Intent | The Google AI surface and payment handler | The agent platform’s own app, per Rain |
| Credential holder | OpenAI stores the card; network tokenizes at purchase | Basis Theory vault; Mastercard token | Google Pay handler (single-use token, per PayPal) | Rain issues a scoped card from the partner vault |
| Statement descriptor | Not stated on the Wallet pages we opened | Not stated; the airline was merchant of record | Not stated on the UCP pages we opened | Rain says the partner’s name can appear on statements |
| What customer data you get | Whatever your checkout already collects; OpenAI’s help pages say you may need name, phone, email or address | Airline processed the booking in its own systems | Google: you keep customer data and post-purchase | Standard card transaction; the agent relationship sits with Rain’s partner |
Discovery and approval can live on someone else’s screen while fulfillment, returns and fraud decisions stay yours. If a Wallet charge looks wrong, OpenAI’s help pages send order issues to you and unrecognized charges to the issuer.
What to do this quarter
- Don’t block the agent by accident. OpenAI asks stores to let verified ChatGPT browser visits through, including signed Web Bot Auth requests. Browser access does not need a plugin or product feed. On Shopify, Poppy is already published — not a payment method.
- Check that fraud rules can accept a legitimate agent purchase. Tokens work with existing checkout forms, but bot-tuned risk systems can still decline them. OpenAI is adding
Forwardedsignals and working with Forter, Riskified, Sardine, Signifyd, Adyen, Checkout.com and Stripe. Ask your providers whether they ingest those signals. - Treat the credential as one-time. You get a network token, not the full card number. Use PAR, and do not reuse it. Recurring charges need separate consent.
- Decide how you want to be found. A current product feed and a claimed Business Profile help ChatGPT show accurate products. OpenAI says shopping is live in the US, Shopify and Etsy catalogs are already integrated, and there are no fees on purchases that start in ChatGPT or that are made on your site or app. Re-check that wording before treating it as a contract term.
- If you sell to EU consumers, watch the first-use consent rules. The Digital Fairness Act proposal (11 November) would, in Article 26, require a first-use choice: confirm every contract, only those that meet the consumer’s rules (including a maximum price and a time limit), or none. Article 35(6) would allow Commission fines of up to 6% of worldwide annual turnover. Annex I lists 62 practices considered unfair in all circumstances, including 10 dark patterns in Part III (points 53–62). It is a proposal, not law.
What’s still open
Checked 16 November 2026, Europe/Warsaw.
- Wallet statement descriptors and a merchant-facing liability guide for agent purchases were not in the Wallet pages we opened.
- Rain describes Visa Intelligent Commerce and Mastercard Agent Pay support as being enabled, not clearly as already live on every card.
- Typical-retailer onboarding, fees and country lists for Mastercard Agent Pay and Visa Intelligent Commerce were not in the pages we opened.
- A later pay-on-behalf path for Google Wallet in Gemini is not stated in the 13 November blog post.
- PayPal’s 13 October Agent Ready docs still mention instant checkout in ChatGPT Apps; OpenAI’s current merchant page does not present that as the path forward.
Re-check Wallet eligibility, fee language, network-program onboarding, and the Digital Fairness Act’s status within 48 hours of publication.
FAQ
Do I need a new checkout for ChatGPT Wallet?
No. OpenAI says Wallet works with your existing checkout and payment forms. Let verified ChatGPT browser visits through, and make sure fraud tools do not decline a real agent purchase. You get a network token, not the full card number; do not reuse it.
Can shoppers still check out inside ChatGPT?
As of 16 November 2026, OpenAI’s merchant page says it is moving away from a standalone Instant Checkout experience, and that purchases are completed on merchant-owned websites or apps. That matches the current playbook (browser or plugin, plus Wallet). We did not find a formal withdrawal notice with a shutdown date.
If I stay merchant of record, do I still own the customer?
You still take the payment, fulfill the order, and handle returns and support. You may not run the approval screen, store the card, or be the first place the shopper asked for help. Merchant of record and customer relationship are not the same thing.
Is Google Wallet in Gemini a way for Gemini to pay my store?
No. Google’s 13 November post is about spending insights for US Gemini app users. Gemini can read Wallet data; it cannot move money. Paying on Google’s shopping surfaces uses UCP checkout and a handler such as Google Pay.
What is Poppy, if it is not a wallet?
Poppy is how a personal agent identifies itself and learns what it may do. Shopify now publishes a Poppy file for every store automatically. It does not move money.
Does the EU Digital Fairness Act already change my checkout?
No. It is a proposal dated 11 November 2026, not law. If adopted, Article 26 would add a first-use consent choice, and Article 35(6) would allow Commission fines of up to 6% of worldwide annual turnover.