A shopping agent that cannot pay is a browser with opinions. OpenAI closed that gap on November 13 when it began rolling out ChatGPT Wallet, the payment layer for its dots agents. A dot can now find a product, fill a checkout and complete the purchase, but only after you review the order and approve it with a security check such as Face ID or a fingerprint scan.
That approval step is the whole design, and it is why this setup deserves care. OpenAI calls Wallet, in its own words, “the first wallet that lets agents pay without access to users’ actual card details and that requires a security check for every purchase.” The claim is OpenAI’s, and the mechanics under it are plain enough to check. You add a card once. The card network then issues a payment token for an approved purchase, with its own card number, security code and expiration date, and the charge lands on your card without the agent or the business seeing the real details.
This tutorial follows the OpenAI announcement and the OpenAI Help Center article on making purchases with Wallet, checked on November 14, 2026. It claims no test purchase. Where Wallet is not yet on your account, the steps stop at eligibility, and that is a correct result for a rollout this narrow.
What You Will Build or Learn
You will end with a Wallet that is ready for a first purchase on terms you control. One eligible card will sit in Wallet as your default. You will know how to see the saved cards, change the default and remove a card. You will also know the exact review you give each purchase request before you approve it, and what to check when an approval succeeds but an order does not.
You will not end with an agent that buys on its own. OpenAI says it expects, over time, that users will be able to set parameters such as spending limits, purchase categories or time periods and preapprove purchases under added safeguards. That is a stated expectation in the announcement, not a feature you can turn on today. Anyone who sells you a delegate now setting for Wallet is selling you a screen that does not exist.
The token travels. The real card stays in the box. Illustration: Dirty Static
Before You Begin
Set up a dot before you look for Wallet. The Help Center is blunt on scope. Wallet works in conversations with your dot. It is not available in Chat, in Work or in standalone Codex threads. A Pro user in the United States can still lack access today, because the rollout is gradual. No setting fixes that, and no support message speeds it up.
For a Chase card, one more rule applies before you start. You must be the primary cardholder, not an authorized user, and the Help Center tells you to install the Chase app on your phone and sign in with biometrics first. For an American Express card, have the card in hand. Its security code is the four digit code on the front of the card, and the setup form will ask for it there.
Step 1: Check Eligibility Before You Hunt for Menus
Action: confirm each item on this list in order. You hold a ChatGPT Pro subscription. You are 18 or older and live in the United States. Your card has a US billing address. Your card is a credit card issued in the United States by American Express, Chase, Mastercard or Visa. You have set up a dot.
Expected result: every item checks out, or you stop with a clear reason. A debit card stops the setup. A virtual card stops the setup. A card issued outside the United States stops the setup. Waiting is the honest move in each case, because OpenAI has given no date for wider access.
Step 2: Start the Card Setup From Your Dot or From Settings
Action: pick one of the two paths OpenAI documents, and follow it to the same secure form.
Path one, with your dot: in a conversation with your dot, ask, “Help me add a card to Wallet.” Then open the secure card setup request or link that appears in the conversation.
Path two, through Settings: open the Settings page from the navigation. Select Wallet. Select Add Card and enter your card information in the form that opens.
A third door exists for a first purchase. If you begin a transaction for the first time with no card saved, the card enrollment flow should be presented at checkout. Use it only if the order in front of you is one you already want to buy.
Expected result: a secure form for card details opens. If no Wallet section appears in Settings and your dot offers no card setup, Wallet has not reached your account yet. Record that fact and stop. Our guide to sandboxed agent sessions covers the wider pattern here. Access expands on evidence from the provider, not on hope from the user.
Step 3: Complete the Secure Form and Add the Card
Action: in the secure form, and nowhere else, enter the card number, the expiration date and the security code. For American Express, enter the four digit security code from the front of the card. Review the ChatGPT Wallet terms and the ChatGPT Wallet Privacy Notice that the form links to. Then select Add card.
Expected result: the flow moves to bank verification if your bank asks for it, or it shows Card added. If you are not sure whether the card was added, ask your dot to show your saved cards before you try to add the card again. Adding the same card twice helps nobody and muddies the record you will rely on in Step 6.
Step 4: Pass Bank Verification in the Place Your Bank Chooses
Action: follow the instructions inside the secure setup flow. Your bank may ask you to enter a verification code, or it may ask you to approve the connection in the bank app. Your bank decides which methods you can use. For an eligible Chase card, follow the setup link to approve the connection in the Chase mobile app. If you are on a computer, scan the QR code with your phone. After you approve in the Chase app, return to Wallet to finish setup.
Expected result: verification completes and the card shows as added. Note what this step is not. Bank verification approves the card for Wallet. It does not approve any purchase. You will review and approve purchases apart from this, one purchase at a time, in Step 6.
Step 5: Name Your Default Card and Read the Saved List Back
Action: ask your dot to show your saved cards. The list gives each card by its nickname, its last four digits and its expiration date. If you add more than one card later, set the default in plain words. Ask, “Make the card ending in 1234 my default,” and put your own last four digits in place of the example digits.
Expected result: the saved list shows the card you added, with the right last four digits and expiration date, and the default is the card you intend to charge. Cards saved in Wallet are apart from payment methods saved on a merchant site. The card that matters for a Wallet purchase is the card selected in the purchase request, so read that line every time in Step 6.
Step 6: Approve a First Purchase, Line by Line
Action: choose what to buy, then ask your dot to complete the purchase. You can ask in the plain style the Help Center uses, such as asking the dot to help find a sweater or to book a hotel for a trip. When the purchase request appears, work through these checks in order, and do not rush the screen because the agent sounds sure of itself.
- Check the merchant. Is this the business you meant to buy from.
- Check the items. Names, sizes, counts and dates must match what you asked for.
- Check the total. Read the full total, not the first price the dot quoted in chat.
- Check the selected card. It must be the card you set as default in Step 5, or a card you choose on purpose for this order.
- Check any shipping terms and any recurring payment terms shown. If you agree to a recurring or continuous payment plan, the merchant may store the payment credential and charge it again under the terms you agreed to. That charge pattern sits with the merchant, not with a Wallet switch.
Then select Approve and complete biometric verification, such as Face ID or Touch ID. If you cannot approve on your current device, follow the link or QR code to continue on a supported device signed in to the same ChatGPT account. If your computer lid is closed, open it to use biometric verification, or continue approval on a supported phone.
Expected result: the screen reports Ready to check out, and your dot continues checkout and reports the result. After you approve, the dot uses a virtual card number linked to your selected card to complete checkout, and OpenAI describes that number as a payment token with its own card number, security code and expiration date. The number at checkout may differ from the number on your physical card. That difference is the system working as described, not an error to report.
Your card keeps its existing rewards, and its protections for eligible disputes stay in place, for example when an item is defective. You transact direct with the business, and the business keeps control of pricing, fulfillment, returns and customer service. Wallet changes who fills the checkout form. It does not change who owes you a refund.
Step 7: Decline, Remove and Clean Up With the Same Care
Action: to refuse a purchase, decline the request before approval. Declining ends that request. To cancel a completed order, contact the merchant. To remove a card, ask your dot to remove a saved card and identify the card by its last four digits. Check that the confirmation names the right card before you confirm removal. Then ask to see your saved cards again and confirm the card is gone.
Expected result: a removed card can no longer pay for new Wallet purchases unless you add it back. Removal does not cancel purchases, close the card with your bank or delete your Wallet data or your OpenAI account. Those are apart actions, with apart owners, and the Help Center keeps them apart for good reason.
Verification
Run these checks and record the results. The Settings page shows Wallet, and the saved card list shows your card by nickname, last four digits and expiration date. The default card is the one you named in Step 5. A test purchase request, one you are willing to decline, shows the merchant, the items, the total and the selected card before any approval control appears. Declining that request leaves no charge and no order.
Finish with the record check. OpenAI says each approval creates a clear record of the purchase you authorized the agent to make. After a real first purchase, match that record against the merchant confirmation and the charge on your card account. The three records should name the same merchant and the same total. If they do not, contact the merchant for the order, your card issuer for the charge and OpenAI Support for a Wallet error or a purchase that differs from what you approved.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| No Wallet section appears in Settings | Wallet has not rolled out to your account yet, or you have no dot set up | Set up a dot first, then check Settings again in a conversation with your dot. If Wallet still does not appear, wait for the rollout. OpenAI gives no access date for a given account |
| Wallet offers no purchase in Chat or Work | Wallet works only in conversations with your dot at launch | Move the task into a conversation with your dot. Wallet is not available in Chat, Work or standalone Codex threads |
| Add card stays disabled in the form | An error sits in the card number, expiration date or security code fields | Correct the field the form flags, in the secure form only. For American Express, use the four digit code on the front of the card. If the button stays disabled, contact OpenAI Support with the exact message and your device details |
| A debit card or virtual card will not save | Wallet does not support debit cards, and virtual cards are not supported at launch | Use an eligible US issued credit card from American Express, Chase, Mastercard or Visa instead |
| A Chase card will not connect | You are an authorized user rather than the primary cardholder, or the Chase app step was skipped | Install the Chase app, sign in with biometrics, and approve the connection in the app. Only the primary cardholder can add an eligible Chase card |
| Bank verification locks the card | Your bank restricted the card or account during verification | Stop the attempt and contact your bank through its official app or the number on your card. Give the bank the time and the exact error |
| Approval will not complete on a computer | The device cannot do biometric verification in its current state, for example with the lid closed | Open the lid, or follow the link or QR code to a supported device signed in to the same ChatGPT account and approve there |
| Checkout failed but a pending charge appears | The merchant result is unclear and a hold may sit on the card | Check for a merchant order confirmation before any new attempt. Ask the merchant whether the order went through, and ask your card issuer about the pending charge and when the hold may clear |
| The receipt shows a card number you do not know | Wallet paid with a payment token or virtual card number linked to your selected card | Compare the merchant and total with your approval record. A number that differs from your physical card is expected. A merchant or total that differs is not, and goes to the merchant, your issuer and OpenAI Support |
| A store will not complete a Wallet checkout | The site blocks agent purchases, or its risk systems flag the purchase | Check for an order confirmation first. If no order exists, buy direct with the store through its own checkout. OpenAI notes that some sites may block agent purchases without meaning to |
Next Steps
Keep the first weeks small. Use Wallet for orders you can verify in one glance, from merchants you already trust, and read every approval screen in full even when the dot summary sounds right. The approval record is your best tool in a dispute, so build the habit of matching it to the merchant confirmation while the habit is cheap.
Watch two things from OpenAI, and treat both as news rather than settings. The first is wider eligibility, beyond Pro users in the United States. The second is the delegated purchase model OpenAI describes for the future, with parameters such as spending limits, purchase categories or time periods. When that model ships, this tutorial will need a new step for setting limits before any purchase, and the review in Step 6 will change with it. Until OpenAI ships it and documents it, approval for each purchase is the product you have. Use it as if it matters, because on a payment screen, it does.
Facts checked against the OpenAI announcement and the OpenAI Help Center on November 14, 2026. Availability and card eligibility can change during the rollout, so confirm both in the Help Center before you rely on them for a purchase you cannot afford to miss. This procedure was verified against those documents and was not presented as a personal test run.
Sources
- OpenAI, Introducing ChatGPT Wallet, November 13, 2026: https://openai.com/index/introducing-chatgpt-wallet/
- OpenAI Help Center, Making purchases with ChatGPT Wallet: https://help.openai.com/en/articles/20001654-making-purchases-with-chatgpt-wallet
- OpenAI, Commerce Partner Playbook, for businesses that want to accept agent purchases: https://developers.openai.com/commerce
- Hero and token images: Dirty Static illustrations
END OF TRANSMISSION
Stay curious. Question everything.
