ChatGPT Wallet starts rolling out in Dots
OpenAI’s initial US rollout lets eligible Pro users delegate purchases. A four-step test helps merchants check where an order can fail.
OpenAI began rolling out ChatGPT Wallet in Dots on November 13. The initial rollout covers US ChatGPT Pro subscribers aged 18 and older who have eligible US-issued cards. Wallet lets a dot make purchases on a user’s behalf. For merchants, the rollout creates a reason to check what happens between a product recommendation and a completed order. OpenAI’s Wallet announcement
Test the purchase as four separate steps
Start with one product variant and write down its SKU, published price, stock status, and expected shipping terms. At discovery, compare what the agent presents with the product page. At cart creation, check that it selects the intended variant and quantity. At checkout, record the amount including shipping and tax and check how your payment provider identifies the transaction. At confirmation, verify that the merchant system created one order and returned the expected confirmation.
Use a sandbox or a controlled purchase with explicit approval. If a run stops at checkout, the timestamps and merchant logs can help distinguish a cart error from a payment decline. OpenAI says payment tokens work with existing checkout flows and advises merchants to review whether their risk systems recognize agent purchases.
OpenAI also recommends current product feeds and recognizing signed agent requests. It says browser access can work without a plugin or a feed. Audit those individually so a stale price or blocked request can be traced to the right system. This early rollout has no published merchant conversion benchmark. OpenAI’s merchant guidance
Run a second case with two closely related variants
Use a product with two variants that share a title and image but differ in price or stock. For example, choose an in-stock black item and an out-of-stock blue one. Save the expected SKU and currency before the test. If the display looks right but the cart contains the wrong SKU, investigate variant mapping before touching payment settings.
Capture the storefront price, the cart subtotal, the total including tax and shipping, and the amount the user approves. Record which step introduces a discrepancy. If the charged amount matches what the user approved but the order is missing, check the merchant order record and payment status before retrying. Use synthetic data or a sandbox when testing repeated checkout actions.
Check what the merchant can fix
If the agent sees stale availability, compare the product feed and product page. If it cannot reach the page, check the firewall or CDN for the request and review OpenAI’s signed-request guidance. If it reaches checkout and the payment is declined, ask the payment or risk provider how they classified the transaction. Keep card data and personal details out of the test notes. OpenAI commerce documentation
Write down which steps you actually observed. A merchant can verify feed and cart behavior before a Wallet run, then add payment and order evidence when an eligible test account is available.
Keep learning
Continue this topic
Next in this topic
Bing adds an -ai search option to hide AI answers
Earlier in this topic
Google brings Gemini 4 Hydrogen to Search worldwide
AEO & AI Search
Ask a question or join the discussion