Every ChatGPT Wallet purchase needs its own approval, with a security check, before any money moves. That rule, stated plainly in OpenAI’s launch post of November 13, 2026, is the entire accountability design of the product, and it is the part a Canadian firm should read first. The wallet lets an agent in ChatGPT complete a purchase on a person’s behalf, built with American Express, Mastercard and Visa. It is rolling out through dots, the separate agent conversations inside ChatGPT, to ChatGPT Pro subscribers in the United States. Canada is not in the launch. The rule still lands here this week, because the question it answers is already on Canadian desks: when an agent spends, who said yes, and where is the record?
The direct answer: ChatGPT Wallet stores a card, lets a dot agent prepare a purchase, and charges the card only after the user reviews the items, the total and the selected card and approves with a biometric check. The agent and the merchant never receive the real card details; the network issues a payment token in their place. At launch the buyer must be 18 or older, live in the US and hold an eligible US-issued card. Full delegation inside preset limits is a stated future direction, with no date. A Canadian firm’s work is 2-sided: write the spending rule for its own staff now, and check whether its own store can even take an agent’s order.
- How the approval record works
- Why the Canadian reader is a merchant first, a buyer later
- The spending rule to write before access widens
How the approval record works
The sequence matters, so take it in order. A user adds a card once, through a secure form, never in the chat. The bank may ask for its own verification at setup. Later, the dot prepares a purchase and presents it. The user reviews the merchant, the items, the total and the selected card, then approves with Face ID, Touch ID or a fingerprint scan. Only then does the payment network generate a token, a substitute card number with its own security code and expiry date, and the charge lands on the selected card. Each approval creates a record of the purchase the user authorized the agent to make. The card’s existing rewards and its protections for eligible disputes stay in place.
That record is the product’s answer to the oldest question in delegation. Give your AI agent an 8-line job description before access set the office version of the same rule this week: a named owner, a written access list and a spending default of $0 CAD until a person raises it. Wallet builds the spending line into the payment rail itself. The agent holds no card number to leak, no stored credential to reuse and no standing authority to spend. Authority is granted 1 purchase at a time, and the grant is logged at the moment it is given.
1 gap in the record deserves a line of its own. OpenAI’s Help Center states that an approval marked ready to check out does not confirm that the merchant has placed the order. Approval and fulfilment are 2 separate facts, with 2 separate owners. A buyer who treats the approval screen as a receipt will chase the wrong party when an order fails. The merchant owns the order. The issuer owns the charge. The platform owns the approval record. A firm writing its rule should copy that split word for word into its own procedure, because the first failed agent purchase in any office will test exactly those 3 lines. A judge says ’20x’ has to mean 20x. Read your AI plan like a contract made the companion point on plan language: the sentence in the vendor’s document is the sentence that decides the dispute.
Why the Canadian reader is a merchant first, a buyer later
No Canadian can use this wallet at launch. The eligibility list is closed: US residence, a US billing address, an eligible US-issued American Express, Chase, Mastercard or Visa credit card, and no debit cards at all. A Canadian executive reading the launch as a shopper can stop there. The same executive reading it as a merchant cannot. US Pro subscribers are the first agent buyers, and a Canadian store that sells across the border may meet an agent at its checkout before it meets 1 at its own office door.
OpenAI published a Commerce Partner Playbook beside the wallet, and its asks are plain. Claim your business and keep its product feed current, so an agent reads the right price and the right stock. Configure the site so signed agent requests are recognized and not blocked by a firewall set to stop bots. Talk to your payment and risk providers, because a risk system that cannot tell a legitimate agent purchase from a stolen card will decline the sale and keep the customer. Businesses in ChatGPT will count how often ChatGPT names you covered the discovery half of this shift on November 11. Wallet adds the payment half: being named is worth little if the agent cannot finish the order.
The spending rule to write before access widens
The launch post looks ahead, in its own words, to delegation inside clear parameters such as spending limits, purchase categories or time periods, pre-approved with added safeguards. No date is given. That paragraph is the deadline warning in this piece, and it cannot be moved by any reader. When pre-approval arrives, the firms that wrote their limits early will set a number and a category list in an afternoon. The firms that skipped the writing will discover their limit from their first disputed charge. Consent works the same way on every file this site tracks. Data centres lose at the polls. Consent is the new permit showed consent becoming a build step in Alberta and Ontario this month. On the payment file, approval is that same step, taken before the spend rather than after the complaint.
Write the rule in 4 lines while the product is still outside the country. Name who may let an agent buy at all. Set the per-purchase ceiling in CAD for your own books, even though the wallet itself runs on US cards today. List the categories that always need a second person, whatever the amount. State where the approval record is filed, and who reads it each month. None of that work needs the product to reach Canada, and all of it is harder to write after the first agent purchase clears.
The recap: the wallet is US-only, the token protects the card, and the approval is the contract. The Canadian work is the merchant check and the written rule, and both can be finished before the rollout crosses the border.
Check your own store this week for the 1 failure the playbook names first: run your firewall and checkout settings past your payment provider and ask, in writing, whether a signed agent request from a wallet like this 1 would be blocked, declined or accepted.
