ChatGPT Wallet: how AI agent purchases stay under user control

OpenAI announced ChatGPT Wallet on Friday, November 13, 2026. It gives agents in ChatGPT Work, Codex, and dots a way to help complete purchases, but users still review and approve each transaction before checkout.

That approval step is the part to watch. The wallet moves an agent closer to taking action in the real world, while keeping a person in the payment loop.

#TL;DR

#What’s new

ChatGPT Wallet is a payment feature, not a new model. OpenAI says agents in ChatGPT Work, Codex, and dots can help users decide what to buy and complete a purchase with the user’s approval.

At launch, the feature is available to a limited number of U.S. ChatGPT Pro subscribers aged 18 or older, using a U.S.-issued Visa, Mastercard, or American Express card. That’s a narrow rollout, not general availability. The announcement doesn’t specify a price for the wallet or changes to ChatGPT subscription pricing.

Users add an eligible card once, then ask an agent to help with a purchase. Before checkout, they can review the items, total, and selected card. They approve with a security check such as Face ID or a fingerprint, which creates a transaction record.

OpenAI says the wallet uses a payment token, a substitute for the actual card details. The token is used to charge the selected card, so the card number isn’t shared with the agent or merchant. The merchant receives the information needed to fulfill the order, such as the shipping address and contact details.

The feature is designed to preserve card rewards and protections, including the ability to dispute a transaction. Those familiar card protections matter: an agent-assisted checkout still needs a way to handle mistakes or unauthorized charges.

The basic flow looks like this:

sequenceDiagram
    participant User as "User"
    participant Agent as "ChatGPT agent"
    participant Wallet as "ChatGPT Wallet"
    participant Merchant as "Merchant"
    User->>Agent: Ask for help with a purchase
    Agent->>User: Show items and total
    User->>Wallet: Approve with security check
    Wallet->>Merchant: Submit purchase using payment token
    Agent->>Merchant: Provide fulfillment details

#How it compares

OpenAI’s announcement and TechCrunch’s report provide limited detail about competing products or standard checkout flows. The comparison below sticks to what those reports establish, rather than assuming the products work the same way.

The meaningful distinction isn’t simply that an agent can shop. It’s whether the person can see what will be bought, understand the total, and approve the payment before it happens. OpenAI describes those checks for Wallet, but the available reports don’t provide enough detail for a security comparison with other agent tools.

#Try it yourself

There’s no public Wallet API or developer integration described in the announcement, so this example does not connect to ChatGPT Wallet or make a payment. It demonstrates a basic approval gate for an agent workflow: show the purchase details first, and continue only after an explicit yes.

Save this as quickstart.py and run it with Python 3:

item = "Wireless keyboard"
total = "$79.00"
card = "Visa ending in 4242"

print(f"Review purchase: {item}")
print(f"Total: {total}")
print(f"Payment card: {card}")

approved = input("Approve this purchase? Type yes: ").strip().lower() == "yes"

if approved:
    print("Approval recorded. No payment was made by this demo.")
else:
    print("Purchase cancelled.")

On approval, the output ends with Approval recorded. No payment was made by this demo. That last sentence is deliberate: user approval is a control point, but a real integration also needs a payment processor, secure credential handling, and a way to record the transaction. The announcement doesn’t document an API for those tasks.

#When to use it (and when not to)

• Consider it if you’re an eligible U.S. ChatGPT Pro subscriber and want an agent to help with a purchase while you review the final items and payment.
• Consider it as a product-design reference if you’re building agent workflows that need user approval before a consequential action.
• Don’t assume it’s available to you yet. OpenAI’s initial rollout is limited, and eligibility includes age, location, subscription, and card requirements.
• Don’t treat approval as a complete safety system. A review screen helps, but users still need to recognize incorrect items, totals, or fulfillment details.
• Don’t plan an integration around an undocumented API. The announcement describes a consumer-facing wallet, not a public developer interface.

#Limitations and open questions

The rollout is deliberately limited, according to the reporting, so OpenAI can test and improve the feature before making it more widely available. That leaves basic availability questions open: which users and retailers will be supported next, and how quickly access may expand.

OpenAI says it plans to add controls such as spending limits and rules for purchase categories or time periods. Those could let users pre-approve some purchases for more autonomous handling, but the reports describe them as future plans, not launch features.

Retailer support is another constraint. TechCrunch reports that some retailers are blocking AI agents from their sites, which could limit where agent-assisted shopping works. OpenAI has also published a Commerce Partner Playbook for retailers that want to support customers using agents. Neither the announcement nor the report provides a full list of supported merchants.

#Check your understanding

#FAQ

Can anyone use ChatGPT Wallet today?
No. The initial rollout is limited to some U.S. ChatGPT Pro subscribers aged 18 or older with an eligible U.S.-issued card.

Does the agent see my full card number?
OpenAI says the wallet uses a payment token so the user’s actual card details aren’t shared with the agent or merchant.

Can I set spending limits now?
Not according to the launch reporting. OpenAI plans to add spending limits and other purchase rules in the future.

#What I’d do

For users who get access, I’d treat Wallet as a supervised checkout assistant, not an autonomous shopping system. Review the item, total, shipping information, and card before approving. For developers, the useful design lesson is simpler: agents that can spend money need an explicit approval boundary, and the available announcement doesn’t yet provide enough detail to build against Wallet itself.

#Key takeaways