Does your shop need a ChatGPT Wallet integration?
A customer wants their AI assistant to buy from your shop. Before paying for changes to your website, check the payment form you already use. OpenAI says ChatGPT Wallet needs no special integration. Shops serving US customers should first find out whether agent purchases work through that form.
The customer brings the agent
OpenAI began rolling out ChatGPT Wallet on November 13. It lets a customer’s dot, OpenAI’s personal AI agent, pay through a merchant’s website. The customer reviews and approves the purchase with a security check. The payment uses a token that replaces the actual card details.
The initial rollout is limited to ChatGPT Pro subscribers aged 18 or over in the US, with an eligible US-issued card. The terms also require US residence, use in the US and a US billing address. Availability can vary by account, device and payment process.
We learned about the launch from TheTip.ai’s November 16 issue, then checked OpenAI’s guidance for merchants. We have not tested Wallet on a shop’s website.
OpenAI’s November 13 Wallet announcementCurrent Wallet eligibility and termsNewsletter discovery: TheTip.ai, November 16
Check payment separately from your business profile
A business profile helps you maintain the information ChatGPT shows about your company. Claiming one does not prove that your website can accept a purchase from a customer’s agent.
If ChatGPT shows incorrect delivery information or product details, start with our business-profile guide. If the customer reaches your shop but cannot buy, use the table below.
Find where the purchase stops
A report that an AI purchase failed is not enough to choose a fix. Ask your website and payment teams to identify the last step that completed. Use this table to guide that investigation.
| Observed problem | Question to resolve | Who should investigate |
|---|---|---|
| The agent cannot open the shop or reach the payment form. | Did site protection block a verified visit, or did the page itself fail? | Your website maintainer or hosting provider. |
| The payment is submitted but declined or cancelled. | What caused the decline, and can the provider recognise legitimate agent purchases? | Your payment provider and whoever manages fraud rules. |
| The customer approved the purchase, but no order is confirmed. | Was the order accepted, and is it recorded in the shop’s order system? | Whoever handles orders, with the payment provider if needed. |
OpenAI: check browser accessOpenAI: payment acceptance and risk systems
Ask for a diagnosis before changing settings
OpenAI’s access guidance says to check for unintended blocks and make changes only if security settings block verified visits. Ask your maintainer for that diagnosis. Turning off bot protection across the shop is not a sensible starting point.
Payment acceptance is a separate check. OpenAI says its cloud browser can trigger risk systems, and support for forwarding customer signals is still rolling out. Your provider needs to explain what it supports for your account; naming a provider in an announcement does not confirm your configuration works.
Illustrative example: an agent reaches the payment form, but the payment provider declines the transaction. Adding a product feed would not reverse that decision. Discuss the reason for the decline with the payment provider.
Browser-access guidancePayment guidance and rollout of customer signals
Approval is not an order confirmation
The Wallet terms distinguish the customer’s approval from the merchant accepting the order. The shop remains the seller and handles delivery, returns and customer service. When a customer asks whether an order went through, check the order and payment records before asking them to try again.
OpenAI says it plans to let customers delegate purchases within limits they set in advance. Plan around the approval steps available today.
Wallet terms: approval, acceptance and the merchant’s roleCurrent purchase approval and future plans
When to act
Investigate now if you serve US customers and have a specific failed agent purchase to examine. Otherwise, ask your providers about support during your next routine review. A limited rollout alone is a weak reason to replace a working payment process.
Only commission a custom integration when you can explain what it will add to your existing payment form. Set the budget around the customer problem you want to solve.
Sources
Choose one part of the purchase to improve.
Tell forvertz what a customer needs to do on your website and which tools the site uses. We can help scope the next step using public information or an illustrative example.
Discuss your websiteUpdated