S3DAT NEWS
· 8 stories RSS s3dat.com

OpenAI separates card access from purchase approval in ChatGPT Wallet

OpenAI set out ChatGPT Wallet purchase and privacy rules in documents effective November 12. They explain where an assistant’s payment authority ends and the merchant’s order responsibility begins.

Spec sheet

Terms effective
12 Nov 2026
Age requirement
18 or older
Current product scope
US Pro users in conversations with a dot
Payment method
Eligible US-issued cards; no stored purchase balance

Who can use this payment flow?

OpenAI’s help page limits Wallet to Pro users talking with a dot. It excludes ordinary Chat, Work and standalone Codex conversations. Supported US-issued cards include eligible American Express, Chase, Mastercard and Visa cards. Chase enrollment requires the primary cardholder. Purchase approval uses biometric verification on a supported device. This puts payment access behind several checks: the account, the conversation surface, the card and the device. A subscription alone does not establish that every checkout will work.

What is different from a ChatGPT balance?

A saved card funds a merchant purchase through a payment credential. The separate ChatGPT balance holds dollar-denominated funds, including redeemed gift cards, for eligible purchases on OpenAI’s website. Those funds can cover eligible subscription purchases, but not API credits or subscriptions billed by Apple or Google. They remain attached to the account or workspace where they were redeemed. The distinction matters because an available subscription balance does not describe the card payment authority granted to an assistant. These are separate payment products with different destinations.

Does saving a card authorize an order?

Enrollment and purchase permission are separate. The terms describe approval tied to the merchant, amount, card, recipient and delivery details; material changes require renewed approval. They also allow advance authority, while the help page describes reviewing individual transactions. Consider a hypothetical parcel order approved for one address and price. A later change to either is a change to the purchase being authorized, not merely a revised sentence in the conversation. Issuer authorization and merchant acceptance remain distinct steps after the assistant submits the order.

What information remains after payment?

According to the privacy notice, the payment provider collects card details through a secure form. OpenAI receives a tokenized credential and limited card information, not the full card number or security code. That does not make the purchase anonymous. Records can include the request, approval or rejection, authentication result, merchant submission and order status. Delivery information can also reach the seller. Removing a saved card does not erase records retained for disputes, fraud prevention or legal obligations. The notice says Wallet data is not sold or shared for targeted advertising.

What does a failed conversation actually prove?

An assistant error is not a merchant cancellation. OpenAI’s help page tells users to check the order or receipt before repeating checkout. In the parcel example, a stalled conversation could leave the user without a clear result even after submission. A second attempt would be a second payment request, not proof that the first disappeared. The useful boundary is therefore evidence from the destination: whether an order exists. Wallet’s documentation separates that operational question from the fact that a card was saved or a purchase was approved.

Claim check

  • Confirmed The Wallet terms and privacy notice are effective November 12, 2026 [1]
  • Confirmed The published help page restricts Wallet to eligible US Pro users in dot conversations [3]
  • Unclear These documents do not establish worldwide availability or acceptance by every merchant

Sources