Architecture Teardown: OpenAI Launches Native Commerce and ChatGPT Wallet

If your store runs on Shopify or custom headless infrastructure, you are likely tracking openai launches native commerce and chatgpt wallet.

OpenAI releases native commerce tools, Business Hub catalog feeds, and ChatGPT Wallet for autonomous agent shopping.

While most public coverage focuses on consumer novelty, the engineering mechanics under the hood require significant edge routing, WAF reclassification, and endpoint hardening. Here is what actually broke in production:

1. Cloud browsers execute checkouts directly

Ephemeral cloud browsers render storefronts and execute checkout flows. Headless tools handle pricing and inventory in seconds.

2. Feeds older than 14 days are deleted

OpenAI's Business Hub requires 9 core product attributes. Any merchant feed not refreshed within 14 days is automatically purged.

3. Default bot firewalls block agent orders

Standard Cloudflare and Akamai rules mistake ChatGPT cloud browsers for malicious scrapers. Stores must allowlist Bot ID 129220581.

4. iFrame plugins are banned from Operator

OpenAI explicitly mandates headless MCP servers. Store endpoints must expose get_product_details, update_cart, and create_checkout.

5. Tokenized checkout prevents fraud declines

ChatGPT Wallet passes tokenized payments and forwards customer IP in RFC 7239 headers so fraud engines approve agent orders.

Key Production Takeaways

1. Allowlist Verified Commercial Agent Signatures: Ensure edge reverse proxy and WAF configurations permit verified crawler traffic (such as WAF Bot ID 129220581) rather than flagging them as hostile scrapers.
2. Deploy Clean Machine Documentation: Publish deterministic Markdown documentation layers (/llms.txt) and discovery manifests (/.well-known/webmcp.json) to minimize token overhead.
3. Preserve Originating Client IP Headers: Ensure reverse proxies preserve incoming RFC 7239 Forwarded headers on checkout routes so fraud engines do not reject orders originating from datacenter IPs.

Maintained and documented at stacktxt.com.