AI Branding Pages — Test Site

Two generic checkout pages for testing brand deployment (Cloudflare Worker and JavaScript SDK), demoing before/after to stakeholders, and validating the request-interception rules in GU-5690.

/checkout.html

Cart checkout

Order summary + card form

/pay.html

Hosted pay page

Single-charge PSP-style page

/checkout-iframe.html

iframe-embedded checkout

Merchant page embedding a separate payment document in an <iframe> — tests whether Cloudflare Worker vs. SDK deployment can reach branded content inside the frame.

How to test each deployment method

Method	What to do
Cloudflare Worker	Deploy this site (or point an existing Worker route at it), then in the Brand Details → Deployment tab, connect Cloudflare and set the Target URL to this site's `/checkout` and/or `/pay` path. Push to Cloudflare. No code changes needed on this site — the Worker injects a `<style>` block that sets the `--ab-*` CSS variables directly.
JavaScript SDK	Uncomment the SDK `<script>` tag at the top of `checkout.html` / `pay.html` with the real `brandId`, then reload. The SDK is expected to call `window.applyBrandPayload(payload)` once it resolves.
Sales demo (no backend)	Click Simulate branding in the harness bar on either page to preview a sample brand instantly, client-side only — useful for stakeholder demos when a live integration isn't available yet.

Hosting

Plain static HTML/CSS/JS — no build step. Deploy to Cloudflare Pages, any static host, or a bucket + CDN. Whatever hostname you use must be added to the Worker's / SDK's host allowlist and match the checkout path patterns being tested (/checkout/*, /pay/*).