How to prepare your online store for ChatGPT Wallet

To prepare your store for ChatGPT Wallet, check product information, agent access, basket behaviour, delivery and payment handling. OpenAI says existing checkouts need no Wallet-specific integration. Start with the twelve checks below; add a direct integration when it solves a problem the existing site cannot handle reliably.

As of 17 November 2026, ChatGPT Wallet payments are available only to eligible users in the US. See OpenAI’s rollout details. At IZZY, we work on ecommerce integrations, AI shopping assistants and AI-assisted checkout flows. To illustrate these checks, we use MOTORA, a fictional car-parts store. We follow the journey from product selection to checkout, looking at what can go wrong, what the store should fix and when a direct integration helps.

12 reasons a ChatGPT purchase may fail

Use this table to choose the first team to involve, then confirm the cause with the checks below. “Store platform” means your ecommerce software or hosting provider; OpenAI is identified separately.

Possible cause First team to involve
1. Product not found Merchant catalogue team; store platform for indexing/feed delivery
2. Site blocked or unusable Merchant web team; store platform/CDN for access blocks
3. Wrong pack or variant Merchant catalogue and web teams
4. Compatibility assumed Merchant product team and compatibility-data provider
5. Stale price or stock Merchant operations; store platform for synchronisation
6. Old choice survives a new request Merchant web/integration team; OpenAI if agent behaviour is the cause
7. Lost or duplicate basket Merchant web team and store platform
8. Delivery or total violates the request Merchant delivery/pricing team; shopper for missing details
9. Wallet unavailable Shopper checks eligibility/access; OpenAI for account or rollout issues
10. Payment declined or verification blocked Payment/risk provider or card issuer; shopper for required approval
11. Unclear order result Merchant checks order first; payment provider/OpenAI as indicated
12. Order cannot be retrieved or managed Merchant customer service and store platform

1. The product is not found

The public description may omit the product reference or pack contents, key specifications may appear only in an image, or a feed may be out of date.

Check: give the agent the product URL, then run a separate discovery task without it. Can it open the item but not find it?

Fix: put the reference, pack contents and relevant specifications in readable product text, then investigate indexing or feed freshness. A product feed helps discovery; it neither updates a basket nor confirms an order. Our practical ecommerce test covers discovery in more depth.

2. The agent cannot open or use the site

Verified browser traffic may be blocked, a control unclear, or a redirect may send the shopper to another market.

Check: identify the stopping point: an access-denied page, a repeated verification screen, an unusable control or a country redirect. Record the URL, action and selected market. Consent and login requests are not automatically technical failures.

Fix: an allowlist may be unnecessary. If traffic is blocked, follow OpenAI’s browser-access guidance. Before an exception, verify request signatures through your CDN or firewall. For manual verification, check Signature-Agent, retrieve OpenAI’s public key and validate Signature and Signature-Input under RFC 9421. Keep other protections. Clarify ambiguous buttons and enable continuation after consent or login.

3. The agent selects the wrong pack or variant

In our MOTORA example, a shopper needs a pair of front wipers. Classic Solo costs €14.90 per blade; Silence Duo costs €32.90 per pair. Choosing the lower price alone would miss the requested pair. In the MOTORA journey, the agent opens a comparison rather than adding the single blade as that pair.

Check: compare the selected SKU, image, pack contents and basket quantity. Does “1” mean one blade or one pair?

Fix: correct the catalogue first, then make selected variant and pack labels explicit on the page and in the basket.

4. Compatibility is assumed

A Peugeot 208 from 2020 may still need a version or connector identified. MOTORA waits for a vehicle check and cannot confirm compatibility when the version is unknown.

Check: identify the merchant or manufacturer reference that establishes compatibility. Try an unknown version and a genuine no-match. If the shopper requests quiet wipers, check which product information supports that claim; a product name is insufficient.

Fix: request the missing identifier. Keep unknown, compatible and incompatible results distinct. Leave quietness unresolved when the product information cannot substantiate it.

5. Price or stock has changed

An earlier page or feed may disagree with the current offer for the selected variant and destination.

Check: in an authorised test environment, change price or stock after selection. Does the basket refresh before commitment? Verify the seller as well as the product.

Fix: retrieve the current offer from its authoritative source. Explain changed prices or unavailable stock; ask before substituting a product, quantity or delivery option. Do not leave the replaced item beside its replacement.

6. An old choice survives a changed request

MOTORA shows two specific resets. After Silence Duo at €32.90 has been added, lowering the product budget below €30 clears that basket and selects Essentiel Duo at €24.90. Changing cars clears the previous compatibility confirmation and basket.

Check: repeat those changes on the merchant journey. Does the old item stay in the basket without another check?

Fix: define which changes invalidate a selection. Recheck the affected items and explain the result; this does not mean automatically emptying every basket after any change.

7. The basket disappears or contains duplicates

Login, session expiry, back navigation or a repeated add may lose a selection or add it twice.

Check: add one pair as a guest, then sign in to an account with an existing basket. Inspect the resulting references and quantities. Repeat an add after an unclear response.

Fix: define which basket survives sign-in and how quantities combine. Show the resulting lines after each update. Use guest checkout where supported; adding another login method will not itself repair a lost basket.

8. Delivery or the final total breaks the request

The address may be unsupported, delivery too late, or a promotion lost. Shipping and applicable taxes may push the total beyond budget.

Check: specify the destination and whether the budget covers products or the delivered total. MOTORA’s initial €35 allowance covers the product, not verified delivery costs.

Fix: show available delivery options and the current total before approval. Ask for agreement if the revised offer exceeds the request; do not quietly change the product or delivery choice to make it fit.

9. Wallet is unavailable to the shopper

As checked on 17 November 2026, Wallet is rolling out to eligible US Pro users aged 18+, with eligible US-issued credit cards and US billing addresses. Wallet works only in conversations with your dot, OpenAI’s agent, and not in Chat, Work or standalone Codex threads. Approval requires biometric verification, such as Face ID or Touch ID.

Check: establish eligibility and actual account access before scheduling a payment test; rollout is gradual.

Fix: classify ineligibility separately from a merchant defect. Preparing a French or UK store does not establish customer eligibility. Test the pre-payment journey separately where necessary.

10. Payment is declined or needs another verification

OpenAI notes that risk systems can reject cloud-browser purchases. A shopper approval or verification step can also require intervention.

Check: distinguish an expected approval from a refusal or an inability to resume. Record the actual status without collecting payment secrets.

Fix: ask your risk provider to ingest available Forwarded signals (ip-country, locale, tz); coverage varies during rollout. With your payment provider, check network-token handling and how to use PAR (Payment Account Reference) to link tokens to the underlying account. Wallet supplies a network token, not the original card number. Preserve the basket through verification. For subscriptions, checkout must support recurring billing and the customer must consent.

11. Approval produces no clear order result

An approval may expire, submission may be interrupted, or the screen may remain pending. Wallet approval is not merchant order confirmation.

Check: look for the accepted order and merchant reference. A pending authorisation or missing basket is insufficient.

Fix: check merchant order status before retrying submission. Show whether the customer should wait, complete another step or contact support. Repeating an uncertain purchase can create a duplicate rather than resolve the uncertainty.

12. The customer cannot retrieve or manage the order

An accepted order is difficult to use if its reference, guest lookup or account access is missing.

Check: retrieve it through the merchant’s supported account or guest route. Can support identify it? Is the cancellation or returns contact accessible?

Fix: provide a clear confirmation and continuation path. Keep the merchant’s delivery, support and cancellation instructions easy to find. Do not imply that Wallet manages fulfilment or refunds for the store.

What to prepare before the first run

Choose a category and give the agent its URL with a request whose result your team can check. For MOTORA:

On the store website I linked, find one pair of front wipers for a 2020 Peugeot 208, with a product budget of €35. Ask for any missing vehicle details before confirming compatibility. Prepare the basket and stop before payment.

Then assign these steps:

  • Choose one important category and write the correct outcome: reference, variant, pack, compatibility, destination and budget.
  • Run the intended agent from a known URL; assess discovery separately.
  • Include the costly variations for that category, such as changed vehicle, changed budget, no match, stock change and expired session.
  • Record the symptom, expected and actual result, likely cause and repair owner. Check the source before assigning blame to the agent.
  • Repair, replay the same task and count successful cases against attempted cases. Keep manual help and unrun steps separate.
  • Arrange a distinct, authorised Wallet payment test with an eligible setup. Mark payment and order stages as not run if access is unavailable.

When an integration helps

Choose the work from the finding:

  • Wrong or missing information: repair the catalogue, compatibility source or product page. Adding an API does not repair incorrect source records.
  • Correct data, unreliable browser steps: consider a tool in a ChatGPT plugin, connected to your systems through MCP, for vehicle/reference checks, current offers or basket updates. Compare it with the same website task.
  • The existing journey meets the tested need: no extra integration is justified by that test.

Our website, feed or ChatGPT app guide explains the route choices.

Keep the scope realistic: OpenAI says third-party plugin interactions with Wallet are still being worked on, and iframe-based MCP UI is unsupported in dots. Tools do not automatically create Wallet connectivity. If a step continues on the website, preserve the intended basket and session. See our implementation guide for the build decision.

Scope the first test with us

IZZY’s AI Agents & LLM Products work can help scope that decision. Bring us one shopping task, a catalogue record and the sources for compatibility, stock and basket state, so we can identify what to examine and which repair or integration the findings would justify. You can also send the team a short brief.

Sources and scope

Platform sources checked on 17 November 2026. MOTORA’s offers and behaviour are fictional; its final handoff places no order or payment. Live stock, delivery, payment and recovery scenarios above are proposed tests. Recheck platform guidance before implementation and affected journeys after merchant-system changes.

izzy.agency teamEngineering & product insights from the izzy.agency team.We use AI in our research and preparation. The analysis, the sourcing and the writing are ours. How we work