Checkout and branding
Checkout and branding
Payers complete checkout on Clearway-hosted pay pages at {docsEnv.paySiteUrl} — not on checkout.stripe.com. Stripe remains the payment processor; Clearway owns the domain and checkout shell.
What payers see today
| Flow | Merchant action | Payer lands on |
|---|---|---|
| Widget / one-off checkout | Create checkout via dashboard or API | {docsEnv.paySiteUrl}/pay/… embedded checkout |
| Payment links | Create link in dashboard or API | Clearway pay / link URL |
| After payment | Default success handling | Your configured success URL or Clearway complete page |
Branding
Customize appearance from the dashboard:
- Open Integrations → Branding → Appearance at https://app-dev.clearway.to/integrations/branding/appearance.
- Set colors, typography, pay button styling, and widget Pay button defaults (animation, label template, phrase-slide lines).
- Preview changes on widget demos and pay pages. Use Animation Lab for animation comparisons, then save defaults here.
Widget Pay button settings apply to your storefront embed (with pay-button.css), not to hosted pay page chrome.
Branding applies to Clearway pay surfaces — payers see your merchant identity inside the Clearway shell.
White-label direction
Clearway is evolving toward deeper layout ownership on pay pages (merchant logo, line items, policies) while keeping Stripe as the rail. New integrations should use Clearway pay URLs ({docsEnv.paySiteUrl}) rather than Stripe-hosted checkout links.
For embedded integrations, prefer the payment widget + checkout integration proxy pattern.
Custom checkout domains
Enterprise white-label may map a merchant CNAME to Clearway checkout infrastructure. Contact support for custom hostname setup — fallback origin is documented in platform runbooks.