# OpenAI Is Building a ChatGPT Wallet for Agentic Purchases > Source: > Published: 2026-08-14 03:01:56+00:00 ## Reporting record ### Finding The ChatGPT desktop client contains an unreleased ChatGPT Wallet flow for saving payment methods that ChatGPT can use while carrying out tasks. ### How we verified Methods: reverse engineering. OpenAI’s production Windows desktop bundle contains a native announcement titled “Introducing ChatGPT Wallet,” alongside secure card enrollment, validation, save, retry and success states. The implementation references feature gate 3398492218, connector connector_openai_wallet and resource internal://wallet-vgs-card-enrollment. RuntimeWire surfaced the bundled interface in a controlled local test. Exact-name searches found no previous public report of ChatGPT Wallet. RuntimeWire hashed and extracted the original ASAR without modifying it, searched the compiled assets for unreleased user-facing features, traced the Wallet components and their display conditions, and confirmed each patch target occurred exactly once. We then made byte-length-preserving changes to a cloned application, replaced the enrollment component with an introduction-only renderer and launched the clone. The setup action was deliberately disabled, and no payment information was entered. Public OpenAI materials and existing commerce coverage were reviewed to distinguish ChatGPT Wallet from previously announced Instant Checkout and PayPal support. Tested versions: Windows package 26.803.10989.0, bundled app 26.803.81509, Codex build 6415. ### Reproduction RuntimeWire independently reproduced the core finding. The bundled client interface was reproduced locally. RuntimeWire did not test card enrollment, confirm account eligibility, establish that the backend connector was enabled or determine a release date. ### File hashes `sha256:39c855f6a0db1cad89dc629edf2f9473b78a25b64fcb1445ece1022af6527755 original-app.asar` ### Company response RuntimeWire requested comment; the company had not responded by publication time. OpenAI is preparing a payment product called ChatGPT Wallet that would let users save cards for ChatGPT to use while carrying out tasks, according to interface code RuntimeWire found in the [Windows ChatGPT/Codex desktop application bundle](https://openai.com/index/introducing-the-codex-app/). The application bundle contains an announcement modal for the wallet, a secure card-entry session and separate states for saving a card, retrying after a failure and confirming success. The accompanying copy tells users that ChatGPT can use saved payment methods to carry out tasks. RuntimeWire surfaced the announcement by bypassing client-side display conditions in a cloned copy of the application. The setup action was disabled, no payment information was entered and RuntimeWire did not confirm that the wallet connector or card-enrollment backend was enabled for its account. The flow points to a broader role than the payment cards OpenAI already keeps for subscriptions. ChatGPT Wallet appears designed as a reusable payment layer for agent actions, allowing ChatGPT to access an authorized payment method when a task reaches checkout. A finished interface inside a shipping application can still be delayed, revised or discarded, so the code establishes active product work rather than a release date. The wallet would give OpenAI another route into transactions after an uneven first attempt at native commerce. On September 29th, 2025, OpenAI [launched Instant Checkout](https://openai.com/index/buy-it-in-chatgpt/) with Stripe and the Agentic Commerce Protocol, initially allowing U.S. users to buy eligible products inside ChatGPT. OpenAI said ChatGPT would pass encrypted payment tokens to merchants, which remained responsible for processing payments, fulfillment and customer support. OpenAI expanded that model in December with an [Instacart integration](https://openai.com/index/instacart-partnership/) that let users assemble a grocery cart and pay without leaving ChatGPT. The model promised a direct path from a conversation to a completed order, with ChatGPT occupying the interface between the customer and merchant. OpenAI changed course on March 24th, 2026. In an update focused on [product discovery in ChatGPT](https://openai.com/index/powering-product-discovery-in-chatgpt/), OpenAI said its initial Instant Checkout design had failed to provide the flexibility it wanted. OpenAI shifted attention toward product search and allowed merchants to bring their own checkout experiences, including in-app environments that preserve retailer accounts, loyalty programs and existing payment systems. ChatGPT Wallet suggests OpenAI still wants an account-level payment credential even as merchants retain their own checkout systems. The two approaches can coexist: a retailer can control the transaction while ChatGPT supplies a user-approved payment token or fills a secure checkout form. That would reduce the repeated card entry that adds friction when an agent moves across merchants or services. The language around carrying out "tasks" also leaves room beyond retail purchases. OpenAI has been broadening ChatGPT from a conversational product into software that acts across websites, files and connected services. The company introduced [ChatGPT Work](https://openai.com/index/chatgpt-for-your-most-ambitious-work/) in July as an agent built for longer jobs that can take action across applications. A reusable payment method would add transactions to that operating model, covering tasks that end with a booking, order or paid service. Payments create a harder authorization problem than browsing or drafting a document. OpenAI's original Instant Checkout policy said users would explicitly confirm each step and authorize encrypted tokens for a specific merchant and amount. ChatGPT Wallet's secure entry session indicates that raw card details would be collected outside the conversation itself. OpenAI separately [instructs users](https://help.openai.com/en/articles/12429613-customer-responsibilities-in-safeguarding-financial-data) to submit card data only through designated secure payment pages, rather than typing it into chats or files. A wallet could keep OpenAI involved when a recommendation becomes a transaction, even when a merchant controls the checkout environment. The client code does not establish whether OpenAI would receive transaction fees, collect conversion data or make the wallet available across unrelated merchants. That position will depend on how narrowly OpenAI defines permission. A card saved for future tasks could support one-time purchases, recurring jobs or transactions initiated after an agent has worked for hours. Each model requires different confirmation, spending limits and fraud controls. The code shows that OpenAI has developed a user-facing payment credential layer for ChatGPT tasks. Whether it ships, and what authorization rules would govern its use, remain unknown.