OpenAI's wallet code is already on user machines, which makes agentic checkout an integration problem

OpenAI's production Windows desktop client contains a complete but unreleased flow called ChatGPT Wallet, for saving payment methods that ChatGPT can use while carrying out tasks, according to a reverse-engineering report by RuntimeWire ^[1]. That matters because the code is not in a preview branch: it was compiled into the shipping bundle and distributed to end-user machines ^[2][4], which puts stored agent-spendable credentials in the integration queue rather than the roadmap deck.

What RuntimeWire describes is not a mockup. The bundle carries a native announcement titled "Introducing ChatGPT Wallet" alongside secure card enrollment, validation, save, retry and success states ^[2], with copy telling users that ChatGPT can use saved payment methods to carry out tasks ^[8]. The implementation references a feature gate numbered 3398492218, a connector named connector_openai_wallet, and a resource string internal://wallet-vgs-card-enrollment ^[3]. Failure and retry handling is the detail worth noting: that is the part teams write when they expect real cards, not when they are sketching a concept.

The limits are real and RuntimeWire states them. It hashed and extracted the original ASAR without modifying it, then made byte-length-preserving edits to a cloned application and replaced the enrollment component with an introduction-only renderer to surface the interface; the setup action was disabled and no payment information was entered ^[5]. It did not test card enrollment, confirm account eligibility, establish that the backend connector was enabled, or determine a release date ^[6]. It found no previous public report using the exact name ^[15], and notes that a finished interface inside a shipping application can still be delayed, revised or discarded ^[14]. OpenAI had not responded to a request for comment by publication ^[7].

The strategic context is a company that has already changed its mind once. On September 29th, 2025, OpenAI launched Instant Checkout with Stripe and the Agentic Commerce Protocol for U.S. users buying eligible products ^[9], with ChatGPT passing encrypted payment tokens to merchants that remained responsible for processing, fulfillment and support ^[10]. In December it added an Instacart integration for assembling and paying for a grocery cart without leaving ChatGPT ^[11]. Then on March 24th, 2026, just under six months after launch ^[16], OpenAI said the initial Instant Checkout design had not provided the flexibility it wanted, shifted attention to product search, and let merchants bring their own checkout experiences, including in-app environments that preserve retailer accounts, loyalty programs and existing payment systems ^[12].

Read together, the wallet code suggests OpenAI wants an account-level payment credential even while merchants keep their own checkout, and RuntimeWire's assessment is that the two can coexist: a reusable payment layer that an agent can draw on when a task reaches checkout, broader than the cards OpenAI already stores for subscription billing ^[13][17]. For anyone running a checkout, that is the design question to answer now, before enablement rather than after: if the agent arrives holding a credential from OpenAI and the merchant owns the payment page ^[12][13], someone has to decide which credential is presented, how the transaction is authenticated, and who carries the dispute.

Watch for server-side activation of connector_openai_wallet and account eligibility, neither of which RuntimeWire could confirm ^[3][6], and for whether the wallet is positioned inside the merchant-owned checkout direction OpenAI announced in March or alongside it ^[12]. A response from OpenAI would settle most of it ^[7].