Browser-side reference implementation

Run the public checkout flow end to end.

This page is an operator tool for testing the direct-AI checkout path: short-lived checkout token, public session creation, Stripe PaymentIntent confirmation, and final UCP completion.

No merchant API key exposure

Buyer-side calls use only the short-lived checkout token.

Stripe Payment Element ready

Confirm the returned client_secret directly in-browser.

Good for smoke tests

See raw responses, PaymentIntent IDs, and final completion payloads.

Checkout Inputs

Checkout access token

Issued by your control plane via /v1/account/checkout-access-tokens.

Stripe publishable key

Auto-loaded from public browser config when available; otherwise enter it manually.

API base URL

Currency

SKU ID

Quantity

Buyer email

Full name

Address line 1

City

State

Postal code

Country

This is a reference client, not a public anonymous buyer page. It is meant for operators, QA, and integration testing before you wire your own branded checkout UI.

Stripe Payment Element

Session State

Session ID

PaymentIntent ID

Client Secret

Order Status

Waiting for checkout actions...

Flow Summary

1. Prepare checkoutCreates public session, updates buyer + fulfillment, and creates Stripe PaymentIntent.
2. Confirm paymentUses Stripe Payment Element with the returned client_secret.
3. Complete UCP sessionSends payment_data.payment_intent_id to OrderCore after Stripe confirmation.

What You Still Need

Merchant token issuanceA control-plane service must issue short-lived checkout tokens.
Publishable key distributionThe public browser config endpoint is live. Keep STRIPE_PUBLISHABLE_KEY configured in production so browser clients can auto-fill.
Branded buyer UXThis page is for reference testing, not end-customer production presentation.