The agentic commerce space has been moving fast. Since August, we've seen a wave of proactive, always-on AI agents from Meta, xAI, OpenAI, Anthropic, and outside contenders like Instinct. People use them to track reservations, manage travel, and keep up with their feeds.
Screen captures from a dot making a purchase and a user authorizing it
(from ChatGPT Wallet announcement)
Merchant responses have varied considerably. Meta's Muse made a splash as the only offering from a major lab with a free plan, and immediately reached No. 1 in the App Store. Following its launch, Amazon was quick to block it from transacting on its platform, claiming it violated the company's terms of service. Shopify did the opposite and added a special integration with Shop Pay to bring millions of its merchants onto the platform by default. Weeks later, JPMorgan Chase decided to block customers from using outside AI agents to do banking on their platform. Recently, we saw opposite approaches from two airlines, with United deciding to block AI agents while Southwest released a ChatGPT plugin to find and book flights.
As these agents got better at finding and curating purchase decisions, users started wanting them to make the purchases as well. This posed a challenge, as existing e-commerce infrastructure has been built around humans making payments, and automated traffic is treated as a risk signal that is frequently used to deny fraudulent transactions. With agent shopping becoming more prominent, payment processors and agent platforms needed to collaborate to enable a mechanism that would allow agents to shop anywhere.
Stripe Link was a recent solution that offered an agentic wallet through their platform, and OpenAI has now announced ChatGPT Wallet (see the screen captures of a dot making a purchase and a user authorizing it above) in collaboration with the major payment networks Visa, Mastercard, and American Express. With a touted weekly user base of 1.2 billion people, this opens up the ability to shop with agents to a large consumer base (although it initially rolls out to ChatGPT Pro subscribers, which OpenAI does not disclose the number of).
What’s needed for a person to start using ChatGPT Wallet - a dot (comes with ChatGPT Pro), a card added through settings, and a device that can biometrically approve transactions (e.g. using Face ID on iPhones).
ChatGPT Wallet works through OpenAI's Dots (their always-on agents with access to their own computing environments), and allows users to add their card details to the app and give dots the ability to complete transactions on your behalf. To use Dots, you need to be on at least the ChatGPT Pro plan, which starts at $100 per month. Wallet is also rolling out to users in the US only, as of the latest announcement.
Wallet is available for "US Pro users with eligible US-issued American Express, Chase, Mastercard and Visa cards" (source: https://help.openai.com/en/articles/20001654-making-purchases-with-chatgpt-wallet)
To add a card, you can ask your dot, or open the Settings page, both of which will lead you to a secure form for entering your card details. The wallet supports storing multiple cards. You may have to complete a bank verification to successfully add the card.
When your dot tries to make a purchase, you are required to manually approve the transaction, which involves biometric authentication. On Apple devices, this could be Face ID or Touch ID.
Dots can also be allowed to make recurring payments.
Payments made using ChatGPT wallet don't reveal your card details directly to the merchant. Instead, the agent gets a token from the network for every transaction, which it shares with the merchant.
This differs from how some existing digital wallets work. When you add a card to Apple Pay, for example, the card network assigns it a new, unique number specific to the card and device called the DPAN (Device Primary Account Number). This is opposed to the FPAN (Funding Primary Account Number), which is the actual card number. Google Pay can return either the FPAN or DPAN on transactions depending on how the card was set up. While the DPAN remains the same per device and card, every transaction has a one-time security code called a cryptogram that works like a dynamic CVV to verify the transaction. ChatGPT Wallet payments, on the other hand, will present a unique token to the merchant on every transaction (merchants can still associate these tokens with accounts through the PAR, which is described more below).
Responsibilities across different players for agentic transactions
In this model, issuers stay in control of tokens that are generated for agents and consumers. Thus, they retain the ability to turn off authorization for specific agent platforms if they see a rise in fraudulent activity, without affecting normal usage of the card.
Token issuance is based on these networks' own standards they are developing for agentic commerce, such as Visa Intelligent Commerce and Mastercard's Agent Pay. These are broader platforms that provide the rails for issuing tokens for making purchases to AI agents that represent humans.
What merchants need to do to start serving agentic shopping traffic: make sure agents are allowed to visit, make their products visible, and update their fraud checks using provided information.
ChatGPT Wallet is meant to be usable across major payment networks without requiring any special integration from individual storefronts. However, OpenAI has published a list of things to check to ensure people's dots will be able to shop on your platform.
To shop on your website, dots need to first be able to access it with their cloud browser. OpenAI has published an agent access guide with information on making sure they aren't inadvertently blocked, with instructions for providers including Cloudflare, Akamai, HUMAN, and Vercel.
Web requests can assert information about who is making them by including information in headers like the User-Agent. This value is easy to spoof, however, and could be used by malicious actors to get through under the guise of a legitimate agentic request. This is why OpenAI uses HTTP message signatures as part of the Web Bot Auth standard, which allows a server to cryptographically verify that the request is coming from OpenAI's servers. It's important to verify these signatures to make sure you're serving legitimate requests.
For more info on how these signals work, read our explainer article about bot and agentic traffic.
Normally, agents will browse by operating a web browser and navigating through web pages as a human would. This can be inefficient, though, and agents can browse much faster if there is a machine-readable interface of a store's catalog available to them. This is what Google's Universal Commerce Protocol does, by establishing a common language that agents and storefronts can speak to communicate information about product catalogs, variants, cart info, and more.
OpenAI also allows you to enable similar functionality within their platform by claiming your business in ChatGPT and uploading a product feed that the app can use to pull information about your store. Businesses in ChatGPT are their own feature that also give you insights into your mentions and website clicks through the app, and allow you to create a Business Agent that can answer customers' questions.
We mentioned above that transactions made through ChatGPT wallet are done with tokens issued from the payment network instead of the card number (FPAN). How can merchants associate multiple payments with the same customer's payment account then? This will be possible through the Payment Account Reference (PAR), a value introduced by EMVCo that links payment tokens to card numbers.
| Risk | Mitigation |
|---|---|
| Requests made by ChatGPT will have browser and IP signals of an automated browser in the cloud. | Verify the Web Bot Auth signatures to verify the request is coming from OpenAI. Then, use the Forwarded HTTP headers for IP and location signals from the original consumer. |
| Transactions use tokens that are distinct from the user’s card number, and potentially from each other, leaving related payment browsing unlinked | Use the Payment Account Reference token in transactions to associate payment activity with the same underlying payment account. |
| The storefront remains the merchant of record for the transaction, and is responsible for disputes. A shopper can dispute a duplicate order, a wrong item, or a canceled subscription even after approving the payment | Keep the final order summary, terms shown at checkout, receipt, processor transaction ID, and relevant delivery or cancellation records. OpenAI may provide Wallet records, so build the dispute process around evidence the merchant already controls |
Most online transactions are Card Not Present (CNP) transactions, where there is a higher risk of fraud because of the physical card not being used in the transaction. Usually, the risk of fraudulent charges lies with the merchant, which means if there is a chargeback related to a fraudulent transaction, it is deducted from the merchant's account.
If the merchant wants to avoid this, they can use a security standard called 3DS. This is a process where the payment network works with the card issuer to authenticate and authorize the transaction. The authentication flow can follow one of two paths: a frictionless flow, where low risk transactions go through without any extra steps, and a challenge flow, where a transaction marked as high risk can require verification from the customer, such as a one-time password. An advantage of using 3DS for merchants is that it shifts the liability to the issuer, since they take on the role of verifying the transaction.
3DS relies on important info like device and browser details, behavioral signals and cardholder details. While OpenAI hasn't shared technical details, they likely share the shopper's info with the payment network and issuer, as their terms say they may share necessary information with the payment providers. While OpenAI hasn’t disclosed technical details yet, they may provide information about the consumer’s device to issuers through this method.
Merchants may also want certain signals for their own risk assessment engines separate from the payment network. As Dots use browser environments running in the cloud, signals like the IP address can be unreliable. OpenAI is able to provide the original request information using the Forwarded HTTP header, which includes information such as the IP address, ASN, country code, and locale of the original device the request is being made on behalf of.
OpenAI has partnered with organizations like Forter, Riskified, Sardine and Signifyd for fraud prevention, and to help their systems adjust for legitimate purchases being made by agents.
ChatGPT's Wallet is a result of OpenAI and payment networks working together to find a fit for agentic commerce that allows merchants to leverage existing systems for risk and fraud management, and for issuers to remain confident in the ways their cards are used.
There are many pieces involved in making agentic commerce reliable. We've seen that the wallet integration (along with other open standards like AP2) provide payment authorization, while protocols like UCP make product navigation and cart management convenient for agents. While ChatGPT Wallet makes it possible for agents to shop on your behalf using your card details, what if you are an organization delegating payment authority to agents through employees, where the spending limits and constraints have to travel through multiple hops? Or what if you're an organization trying to accept payments from parties that can prove delegation from certain root parties, along with the ability to store verifiable logs of those transactions?
These use cases require verification of claims about agent identity and delegation, which are solved by a different type of puzzle piece. At Vouched, we are a contributor to a Know-Your-Agent protocol named KYA-OS, developed under the Decentralized Identity Foundation, which offers a Payments Profile spec to introduce identity and verifiable delegation to payments that can live across multiple parties. To read more about how KYA-OS fits in the picture alongside protocols like UCP and AP2, read our explainer on agentic payment protocols.