Skip to main content
v2026.11,986 entries · CC-BY 4.0

Editorial · CASRAI · AI and ML research outputs

OpenAI introduces ChatGPT Wallet for agent payments

OpenAI launched ChatGPT Wallet on November 13, with user-approved purchases and organizational permission required to store business cards.

Published 14 Nov 2026· 3 minute read

Ask CASRAI · free to try

Ask about this story

Ask your first 2 questions free below. Subscribers get 150 a day for $29 a month.

An AI assistant specialized in research administration. It cites the sources behind every answer, labels web answers and says when it can't answer.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

CASRAI is the reference for research administration — bookmark it for the next question.

OpenAI introduced ChatGPT Wallet on November 13, 2026, beginning a limited rollout of card payments through its dots agents. Users approve individual purchases; the company describes full delegation as a future development. For universities and research offices, the terms make organizational permission to store a business card a separate condition of use.

What launched and who can use it

The launch announcement says Wallet initially serves ChatGPT Pro subscribers aged 18 or older in the United States with eligible US-issued cards. OpenAI developed the service with American Express, Mastercard and Visa.

OpenAI’s purchase support page describes a gradual rollout, so eligibility does not mean immediate access. It requires a US billing address and supported biometric verification. Wallet works in conversations with a dot and is currently unavailable in Chat, Work or standalone Codex threads.

Saved Wallet cards are separate from the payment method for a ChatGPT subscription, gift cards and prepaid ChatGPT balance. The Wallet terms also state that the service creates neither a bank account nor a stored balance.

Purchase approval today, delegation later

In the announced flow, the user reviews the items, total and selected card, then authorizes the purchase with a security check. A payment token substitutes for the actual card details at checkout, according to OpenAI. The company says it expects future delegation to let users pre-authorize purchases within parameters such as spending limits, categories or time periods; that is a plan rather than the launch workflow.

The Wallet terms, effective November 12, allow for advance authorization in their wording. That contractual provision alone does not establish that full delegation is currently available. The terms limit approval to the purchase details shown and require renewed approval if a material detail changes. Merchant acceptance remains a separate decision.

Business-card permission matters for research purchasing

The terms require a card the user owns or is legally authorized to use. For a business card, the organization must also permit its storage with OpenAI for purchases. The merchant remains the seller and the purchase remains subject to the merchant’s terms.

For a university evaluating a procurement card workflow, the practical implication is to distinguish permission to enroll the card from approval of a specific order. That distinction gives a procurement card program a concrete question to resolve: whether its authorization covers storage with this service. A Wallet approval should not itself be read as evidence of institutional permission.

Transaction records extend beyond card details

The Wallet Privacy Notice says OpenAI receives a tokenized credential and limited card information, rather than the full card number or security code. It also collects purchase details, approval or rejection records, authentication results and information about the request sent to the merchant. Information needed to place and fulfill an order goes to merchants and their providers; payment-related information also goes to issuers and networks.

Removing a card does not erase records retained for the purposes described in the notice. For research offices considering a pilot, those provisions make record handling and data sharing relevant alongside procurement card reconciliation. Tokenization addresses which payment credential reaches checkout; the privacy notice describes the wider transaction information involved.

Sources

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →