OpenAI Is Shipping a Bearer Instrument, Not a Gift Card

OpenAI has begun a gradual rollout of giftable ChatGPT credits, and according to RuntimeWire the client-side machinery is already sitting in the shipped Windows app behind remote switches ^[1][3]. The consequence is not the greeting-card use case; it is that OpenAI now operates a prepaid instrument that one party buys and a different party spends ^[10].

The documented flow is straightforward. OpenAI's Help Center article describes purchase, delivery, redemption, expiration and refund rules for gifted credits ^[2]. Per that article, an eligible customer makes a separate prepaid purchase, receives a one-time claim link, and can send it by email or paste it into any other private channel; on redemption the credits land in the recipient's personal ChatGPT balance ^[10]. Buyers pick an amount and can attach an email address and a message at checkout ^[12].

Read the fine print and this is not account-to-account transferability. Gift credits are a new purchase, not a debit from the buyer's existing balance, and existing balances remain non-transferable ^[12]. So the primitive OpenAI has shipped is a second SKU that happens to be portable, not a wallet that moves money. It is available to eligible personal accounts on Free, Go, Plus and Pro in supported locations and billing currencies, purchased on the web, and explicitly closed to Business and Enterprise workspaces ^[11].

The security model is the part operators should sit with. The recipient email does not secure the gift; OpenAI says anyone holding the complete claim link may be able to redeem it ^[13]. That makes the link a bearer instrument, and bearer instruments attract resale, phishing and support-ticket volume. Expiration and refund rules exist in the documentation, though RuntimeWire's record does not spell out their terms ^[2].

On the client side, RuntimeWire says it extracted the Electron archive from the Windows package and found a dedicated gift-credit module, a direct purchase route at `https://chatgpt.com/gifts/credits`, remote controls named `purchase_flow_enabled` and `desktop_beacon_enabled`, and three UI entry points: home screen, profile and Usage settings ^[3][18]. The named assets include `gift-credits-entry-point-availability-BkG0LT6m.js`, `codex-home-announcements-DNS1iexT.js`, `profile-eeZS6pzc.js` and `usage-settings-DttykFrk.js` ^[17]. A shared availability module opens that URL, restricts the UI to eligible personal-account structures, and reads separate remote values for the purchase flow and the desktop banner ^[4]. Two flags means marketing and checkout can be turned on independently. In a copied installation with two local display conditions overridden, the shipped banner rendered with the text "Gift credits" and "Send a friend credits they can use for work or Codex tasks" ^[5][6].

The limits are stated plainly in the reporting record. No purchase or redemption was completed, because checkout eligibility stays server-controlled, and the live flow cannot be reproduced without an account inside OpenAI's rollout ^[7]. Tested build: `OpenAI.Codex_26.803.10989.0_x64`, bundled application version `26.803.81509`, Codex build `6415`, flavor `prod` ^[8]. The bundle was hashed before inspection ^[9]. OpenAI was not contacted before publication ^[16]. Product researcher Tibor Blaho flagged the live page on X early Wednesday, and RuntimeWire found reposts but no news-publisher coverage at the time it published ^[14]; it captured the documentation on August 12, 2026 ^[15][19].