Explainer
ChatGPT Wallet lets OpenAI's agents buy with a network token and a check on every purchase. This post explains how it works and how to offer the same in your own AI app.

On November 13, OpenAI added a wallet to ChatGPT.
It isn't a crypto wallet or a prepaid balance. It holds a person's own credit card, so that a dot, one of ChatGPT's always-on agents, can buy things on a store's website for them. The person approves each purchase with Face ID, the store is paid like any other card payment, and the card number stays in a vault.
For teams building AI apps, it's a sign that agents paying for things is moving into mainstream products, and that users will start to expect it.
This post explains how a Wallet purchase works, what Wallet is built on, what it took OpenAI to build, where it falls short today, and how to offer the same thing in your own app.
How a Wallet purchase works
Take a request for running shoes under $120, in size 10. The purchase goes through these steps:
The user adds their card to the wallet once. The dot never sees the card details.
The dot shops. It browses, picks a store and fills the cart.
The user sees a review screen with the merchant, the items, the total and the card, before any money moves.
The user approves with Face ID or a fingerprint, and that approval is kept as a record of exactly what they agreed to.
The card network issues a stand-in card number, with its own security code and expiry date, for this one purchase.
The dot checks out. It enters the stand-in number at the store's own checkout, and the store runs a normal card payment.
The purchase completes as usual. The statement shows the store, the card's points apply, and returns go through the store.
The user is involved in two of these steps: adding the card and approving the purchase. The agent can make purchases, but it never has access to the card details.
What Wallet is built on
Wallet has four main parts.
A vault. Card details sit in a PCI DSS compliant vault. The agent can't read it, and neither can the merchant.
A network token. Visa, Mastercard and American Express each issue tokens for agent purchases, and OpenAI built Wallet with all three. At checkout, the token looks like a card. The token is tied to the user's approval for that one purchase.
An approval on the record. Every purchase gets a biometric check, and the check is logged. If a charge is ever disputed, there's proof of what the user said yes to.
A browser that can check out. The dot uses a cloud browser on the merchant's existing checkout page. The merchant doesn't install anything.
To a merchant's fraud system, a browser running in a data center, visiting for the first time and paying with a card it has never seen, looks a lot like fraud. So OpenAI signs every request, letting a merchant's CDN check that the visitor really is ChatGPT. It passes along signals about the real person behind the agent. And it works with fraud and payment providers so good agent orders don't get declined.
What it took to build
Building Wallet took a card vault, work with three card networks, bot verification, fraud providers, a merchant program with guides and product feeds, and a cloud browser that can get through checkouts designed to stop bots.
It also followed an earlier attempt. OpenAI's Instant Checkout completed orders inside ChatGPT, and in March 2026 it was scaled back. Wallet is the second design: the agent now shops where the merchant already sells, so the merchant keeps the customer.
OpenAI has a dedicated team for this. For most AI apps, building the same thing would mean a year of compliance, card network work and checkout automation, time they would rather spend on their own product.
Current limitations
As a first release, Wallet has some limits:
Every purchase needs approval. A Face ID check on each purchase is safe, but it means an agent can't reorder coffee beans while the user is asleep. Spending limits are on OpenAI's roadmap but not live yet.
Some stores block agents. An agent can't buy from a merchant that blocks agents, and some of the biggest retailers do.
Browser checkout is slow. A cloud browser loads pages and fills in forms the way a person would.
Access is limited. For now, Wallet is available to a limited group of ChatGPT Pro subscribers in the US, with US-issued cards.
Launch a card wallet in your own AI app
You don't need to build this yourself.
Wallet's design is close to how Prava works: the user's own card, a passkey approval, and a one-time network token locked to the merchant and amount. Prava has run this model in production since February.
Prava offers it, along with product search and checkout, through one API:
What Wallet has | What your app gets with Prava |
|---|---|
Product search | The Shop API, across UCP stores and merchants Prava has enabled directly, with quotes held for about 15 minutes |
Checkout | 5 to 20 seconds on UCP stores, where checkout runs through the protocol instead of a browser. Browser checkout in 10 to 20 seconds on most other store websites |
A card vault | A PCI DSS compliant vault, with an embedded or hosted card form, so your app stays out of PCI scope |
Network tokens | A one-time network token for every purchase, locked to the merchant and amount |
An approval | A passkey in your app: Face ID, Touch ID or a security key |
Spending limits, coming | Mandates, live today: limits on merchant, amount, frequency and duration |
US cards | Cards issued in 13 countries |
Mandates are worth a closer look. With a mandate, your user approves once and sets limits, and your agent can buy within those limits while they're out for a run or asleep. Each purchase still gets its own one-time token.
All of this runs inside your app, under your brand, and your users don't need a Prava account.
In August, we co-hosted the Agentic Commerce Hackathon with OpenAI and Visa, with 3,500 applicants, 400 builders and more than 160 projects built around agents that buy things, so we were glad to see this launch. To start building, follow the quickstart.
ChatGPT Wallet and Prava
ChatGPT Wallet works only inside ChatGPT, for OpenAI's own agents. Prava brings the same checkout to every other AI app, under that app's own brand. See them side by side.
Summary
ChatGPT Wallet keeps the user's cards, asks for a security check on every purchase and pays with a token, so neither the agent nor the merchant sees the card number.
The agent checks out on the merchant's own website, and the merchant handles the order, the payment and any returns.
To launch the same in your app, you need product search, checkout, a card vault, network tokens and an approval step. Prava gives you all five in one API, and you can integrate it in an afternoon.
FAQ
Can I use ChatGPT Wallet in my own app? ChatGPT Wallet is built into ChatGPT for OpenAI's dots. OpenAI's developer guidance covers merchants that accept Wallet payments, not other apps offering Wallet to their users. To give your own users the same experience, you need a wallet of your own, and that's what Prava provides.
Do merchants need to integrate with Prava? No. On UCP stores, Prava handles the UCP integration. On other store websites, Prava's browser checkout uses the merchant's existing checkout, and the merchant processes the token like any card payment.
Can I use my own browser agent? Yes. Use Prava's checkout, or run your own and use Prava for approvals and tokens. See the integration modes.
Which cards work with Prava? Visa and Mastercard, through Visa Intelligent Commerce and Mastercard Agent Pay. Cards issued in the US, Canada, Mexico, Australia, Hong Kong, Japan, Malaysia, New Zealand, Singapore, South Korea, Taiwan, Thailand and Vietnam, subject to the issuer. Indian cards aren't supported yet.
Is Prava the merchant of record? No. The merchant sells the goods and charges the user's card. Prava handles the search, checkout, approval and token.
Sources

Prava team

