OpenAI launched ChatGPT Wallet on Friday, a payment layer that lets its “dots” AI agents buy things on a user’s behalf — initially for US Pro subscribers aged 18 and over, as reported by CNBC. The company says the agents never see a card number: the payment network issues a “payment token” scoped to a single transaction, containing a one-off card number, security code and expiry that die with the purchase. American Express’s innovation head Luke Gebb is quoted in the CNBC report calling the deliberate small rollout “the right approach to make sure things are working,” noting OpenAI can “turn up the volume” given its base of more than 1.2 billion weekly ChatGPT users and nearly 100 million paying subscribers.
🔍 THE BOTTOM LINE: The most revealing detail sits in the timing and the merchant guidance. ChatGPT Wallet arrived within roughly 24 hours of United Airlines writing a ban on third-party agent bookings into its contract of carriage — and OpenAI published instructions for merchants on how to avoid accidentally blocking its agents. The agent-payment ramp and the merchant defences are being built simultaneously, by the same industry, at each other.
What actually launched
The mechanics are the story. Rather than handing an agent stored credentials — the exact risk United cited this week, that sharing account details with a third-party assistant “can expose sensitive information” and lead to “unintended purchases” — OpenAI routes transactions through network-issued tokens scoped per transaction. Card details stay with the wallet; the agent carries a disposable instrument. OpenAI is not taking a cut of transactions at launch, with CNBC reporting the near-term aim is merchant relationships and positioning ChatGPT as a serious shopping platform as vendors begin experimenting with personal agents.
OpenAI framed agentic commerce as still in its “early days” and published tools and guidance alongside the launch, including how merchants can make sure their websites are not inadvertently blocking OpenAI’s agents — a striking contrast with United’s stance. Product lead Pranesh Nayak told CNBC the wallet builds on OpenAI’s earlier work in product discovery. The PayPal-OpenAI wallet integration announced in late October pointed at exactly this: a branded agent checkout lane inside a chat window, now switched on for US Pro subscribers.
Two camps, one week
The collision course is now explicit. On one side, agent platforms embedding checkout: OpenAI’s wallet, Stripe’s agent payment rails, and Meta’s Muse shopping agent push. On the other, merchants asserting control of inventory: United’s contractual ban, which put it alongside Amazon’s September block of Meta’s Muse agent and against Delta and Southwest — a split our earlier coverage traced through the permission questions now landing on both sides.
Into that seam, OpenAI published merchant-facing guidance on not-blocking agents the same day United’s ban went live. Neither side is hiding the disagreement: the platforms claim the token layer solves the credential risk that merchants cite; the merchants answer that the problem is not payment security but agency itself — who is authorised to commit a purchase, and whose rules apply when an automated buyer makes mandatory disclosures. United’s position, as we covered yesterday, extends to regulatory territory: an agent booking a flight cannot itself attest that luggage contains nothing prohibited, where FAA and DOT rules may require the passenger to do so.
The next twelve months will decide which merchants copy United and which adopt token flows like OpenAI’s. The signal in this week’s back-to-back announcements is that both outcomes are being actively engineered right now — the checkout rail and the “agents not welcome” sign shipped together.
