twimco.Let’s talk ↗︎
Menu
Field notes / Commerce

ChatGPT Wallet can pay on your existing checkout. Place a test order before your firewall or fraud rules decline one

A shopper can now approve a purchase in ChatGPT and have it run through your existing checkout, with a network token instead of their card. Before you rewrite anything, place a test order through that path. If it fails, look first at the firewall and at any fraud rule that still treats a signed agent request as a bot.

Editorial illustration of a bike-shop owner holding a small test-order box and a blank packing slip while a colleague points a pencil at a laptop that shows two abstract color blocks.

Yes. ChatGPT Wallet, rolling out in dots for U.S. ChatGPT Pro users, can pay on your existing checkout with no Wallet-specific integration required. The shopper approves each purchase with a security check such as Face ID or a fingerprint. You keep pricing, fulfillment, returns and service. Place a test order first and check whether your CDN or firewall is blocking signed Web Bot Auth requests, or a risk system is declining a legitimate purchase. Then claim the business, upload a product feed, let verified agents through, work with payment and fraud providers, and treat a plugin or WebMCP as optional. Pre-approved spending limits come later.

Place a test order before you change anything

A customer can now ask ChatGPT to buy something from your site, approve the charge, and expect the order to land in your usual checkout. As of November 13, OpenAI is rolling out ChatGPT Wallet in dots, for ChatGPT Pro subscribers in the United States. The payment uses a network token, not the shopper's actual card details. You keep the customer relationship, and you still set the price, ship the goods, take the return and answer the support email.

The launch post is also a warning. OpenAI says some sites may unintentionally block Wallet purchases. The usual reaction is to start a project: a new checkout, a plugin, a feed rewrite. None of that is the first move.

Place a test order through the agent path before you change anything. If you have access to a U.S. ChatGPT Pro account that already has Wallet, try a small purchase through a dot and watch where it dies. If the request never reaches checkout, start with the CDN or firewall: it may be treating a signed ChatGPT browser visit as a bot. If the request reaches your payment form and then gets declined or cancelled, start with the risk system. Those are two of the checks in OpenAI's Commerce Partner Playbook. Fix what the test shows, and only then decide whether you need anything else.

One caution while you run it: OpenAI says availability is limited at first. If the tester cannot see Wallet yet, don't treat that miss as a failure of your stack.

What actually arrived today

ChatGPT Wallet is a way for an agent to pay without being given the shopper's actual card details. OpenAI built it with American Express, Mastercard and Visa. A shopper adds a card once. Before each purchase they review the items, the total and the selected card, then approve with a security check such as Face ID or a fingerprint scan. Each approval creates a record. After that, the payment network issues a token — a substitute with a card number, security code and expiration date — and the charge goes on the selected card. ChatGPT Wallet does not share the actual card details with your business or with the agent. OpenAI says existing card rewards and protections for eligible disputes still apply.

It is not a general ChatGPT feature yet. OpenAI says the wallet began rolling out on November 13 in dots, initially for ChatGPT Pro subscribers who are 18 or older in the United States, with eligible U.S.-issued cards, and that availability is limited so it can learn and improve compatibility.

You don't have to rebuild checkout to take the payment. The playbook's accept-payments guide says ChatGPT Wallet works with existing checkout pages and payment forms, and that no Wallet-specific integration is required. The customer reviews and approves the purchase in ChatGPT; your checkout processes the payment. Your business handles the order, fulfillment, customer support and fraud decisions. The launch post puts the same point in commercial language: users transact directly with businesses, who remain in control of pricing, fulfillment, returns and customer service.

What is not live is the next step OpenAI describes. Over time, it says, users may be able to delegate purchases by setting parameters such as spending limits, purchase categories or time periods, and pre-approve those with enhanced safeguards. That is a later plan. Don't build a process that assumes a shopper has already pre-approved a limit.

Place a test order through the agent path before you change anything.

Two places a test order can fail

Start with access. ChatGPT's cloud browser can already use your site. You don't have to add it to an allowlist. What you may have to do is stop a security rule from blocking a visit the playbook already considers verified.

OpenAI asks you to configure your CDN or firewall to recognize signed requests that use Web Bot Auth, and to confirm that general site security is not blocking ChatGPT agents. Browser access does not require a plugin or a product feed. The guide to cloud browser access says Akamai, Cloudflare, HUMAN and Vercel verify those ChatGPT signatures automatically. For other providers, a signed request carries Signature, Signature-Input and Signature-Agent headers — Signature-Agent is "https://chatgpt.com" — and you can check them against public keys OpenAI publishes. These are signed browser visits on a user's behalf, not OpenAI's search crawlers. An allowlist for one is not a decision about the other.

If you already watch agent traffic on Cloudflare, we wrote about following a personal agent to checkout before you block any. A Wallet test is the same instinct, with a payment at the end of the path.

Then look at risk. Wallet tokens are meant to work with existing checkout, but risk systems are often tuned to detect bots and lean on signals such as IP addresses or details about the connected browser. The playbook says ChatGPT's cloud browser can set those systems off by accident and cause purchases to fail. OpenAI is rolling out support for relaying user signals in the Forwarded HTTP header, and it tells you to contact your risk provider — or, if you run your own system, to start observing that header. The signals may vary as support rolls out to every site.

The launch post names fraud partners already in that work (Forter, Riskified, Sardine and Signifyd) and payment processors (Adyen, Checkout.com and Stripe). Even if yours is on that list, don't assume the rule is already right. You receive a network token, not the full card number; the playbook says to use the Payment Account Reference (PAR) to associate the token with the underlying account. And the customer has consented only to that transaction: don't reuse or save that payment credential for a separate purchase.

Decision guide

Two places a test order can fail

ConsiderationThe agent never reaches checkoutCheckout runs, then the payment is declined or cancelled
What you'll noticeThe agent stalls or is blocked on the site.A payment is attempted, then declined or later cancelled.
What's often going onA CDN or firewall is treating a signed ChatGPT browser visit as a bot.A risk system is using bot-like IP or browser signals.
What to checkWeb Bot Auth signed requests. Akamai, Cloudflare, HUMAN and Vercel can verify them automatically.Your payments and risk providers, and the Forwarded header OpenAI is rolling out.
What this is notNot the same decision as allowing OpenAI's search crawlers.Not a missing Wallet integration; the playbook says none is required.
Illustrative split based on OpenAI's Commerce Partner Playbook; not a client example or measured result.

The rest of the playbook, once the path is clear

The test tells you whether a purchase can complete. The other playbook steps decide whether ChatGPT can find you cleanly, and whether you want to expose structured actions later.

First, claim the business in ChatGPT and, once you're verified, update its details and upload a product feed with current pricing and availability. That claim flow is the same Business Hub work we walked through when it opened: fix what ChatGPT already says about you, get the feed to match the live storefront, and read the terms before you connect it. A feed helps discovery. It is not what makes the cloud browser able to check out.

Last, and optional: you can build a plugin so agents can check availability, manage carts or take other actions, and websites can also add WebMCP tools. The playbook is explicit that browser use follows your existing website flow and does not require a significant engineering lift, while a plugin takes more integration work and lets you expose structured actions. Skip it until signed traffic can reach the site and a legitimate agent purchase is not being declined. A plugin will not help a request that never arrives.

How the work moves

A first week on the agent path

  1. Place a test order through a dot

    A small purchase, from a U.S. ChatGPT Pro account that already has Wallet.

  2. Read the failure

    Did the request die at the edge, or after checkout?

  3. Let signed agent requests through

    The CDN or firewall recognizes Web Bot Auth; other security controls stay in place.

  4. Work with payments and risk

    So a legitimate agent purchase is not declined or cancelled.

  5. Claim the business and upload a feed

    Current prices and availability, after you're verified.

  6. Plugin or WebMCP only if you need it

    Optional structured actions, not a prerequisite for browser checkout.

Illustrative sequence based on OpenAI's published playbook; not a client workflow or measured result.

Put this into practice

Here's a sensible first pass this week:

  1. Find one U.S. ChatGPT Pro tester who can see Wallet in a dot, or wait until that account has it. Place a small test order on your own site through that path. If Wallet isn't on the account yet, don't treat the miss as a failure of your stack.
  2. If the agent never reaches checkout, look at your CDN or firewall and at whether signed Web Bot Auth requests from ChatGPT are being allowed.
  3. If checkout runs and the payment is declined or later cancelled, talk to your payment and risk providers about legitimate agent purchases, and about the Forwarded header OpenAI is rolling out.
  4. If you haven't already, claim the business and put a current product feed behind it. Don't wait on a plugin or on WebMCP.
  5. Leave pricing, fulfillment, returns and service where they are. You still own those.

Our ecommerce work covers the path from a product feed through checkout, payments and the rules that decide whether an order is real. When the question is how an agent should be allowed to act on your site, that also sits with our AI applications and agents work. If you want a second pair of eyes on a failed test order, send us what you've got.

Related work: Paddle8.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎