ChatGPT Wallet: scoped source reconciliation

Reviewed 2026-11-14 against main 5e9504e2901313138d86fdc610eb4d754bff7a92. Scope: the newly launched personal Wallet payment boundary only; not a whole-OpenAI currency review. Existing Dots guide v0.3.0 had generic purchase authorization in 4.4 but no Wallet control. Ownership remains OpenAI; platform placement unchanged.

Source-first candidates and disposition

Candidate Fetched first-party evidence Disposition
Eligibility and rollout Launch Covered in 4.5; no Enterprise entitlement inferred
Owner workflow and payment lifecycle Help Covered in 4.5; neither authorization nor removal proves merchant outcome
Delegated authority and verification wording Terms Covered with explicit conflict boundary; no legal-language-derived control
Credential processing Privacy notice Covered; collect no payment secrets in evidence
Trust Center Public catalog Public landing/catalog inspected. PCI assurance announcement is not a customer configuration guide. Private reports and full interactive document catalog not traversed; no exhaustive Trust Center coverage claim. FedRAMP adjacent-edition materials do not establish personal Wallet support.
Merchant commerce enablement Launch’s merchant guidance Excluded from this owner-side control: accepting agent payments is a distinct merchant-management plane

Surface census and Code Pack decision

Surface Evidence status Write/read disposition
Terraform resources/data sources Unverified for Wallet; consumer documents establish no provider handle No enforcement or verification pack
REST/GraphQL Unverified for Wallet; no endpoint contract established No invented administration or audit routes
First-party CLI Existing CLI inventory marks workspace/Dots administration unverified; API Platform CLI is a separate product No CLI pack
SDK Unverified for Wallet No payment/admin SDK invented
Native config/MDM Unverified for Wallet; workspace requirements do not prove consumer Wallet enforcement No configuration emitter
SIEM Unverified Wallet event/export schema; transaction records described by privacy terms are not an export contract No invented detection fields

No handle is claimed available, deprecated or removed. These are research gaps, not proof that an interface cannot exist. No manual/checklist pack: create-code-pack Phase 3 forbids checklists and requires executable code against verified interfaces. Existing packs remain unchanged except their applicability README. No Wallet data, credentials, orders or accounts were accessed.

Validation boundary

Control 4.5 ClickOps: DRIFT-CHECKED-ONLY, documentation-backed, not live exercised. Wallet Code: no supported pack authored. Live checkout/removal tests SKIPPED because eligible test account and transaction-specific authorization are absent. No maturity promotion. Structural checks are reported in the PR independently of this semantic result.