Optional module
Custom branding
Beyond a logo swap — the surfaces your merchants live in
What it solves
White-label that stops at a logo in the corner is obvious to anyone who has seen the same platform under another name. The surfaces merchants and payers actually look at are the panel, the checkout page and the e-mail.
How it works
Tenant branding config
App title, logo and theme values live in the tenant's branding configuration and are read by panels, hosted checkout, the docs host and the mail layer from one place.
Branded outbound mail
Invoice mail, merchant notifications, alerts and password resets all render through one branded layout in the recipient's own locale, rather than drifting per template.
Checkout presentation
The hosted payment form on your pay host carries your identity, while the payment logic behind it stays on the platform's tested path.
The advantage
It reads as your product
Merchants sign up with you, log into you, and get e-mail from you — with no seam where the platform shows through.
One place to change it
Rebranding is a configuration change, not a release across five surfaces.
Locale-correct out of the box
Branded mail respects the recipient's own language preference rather than the sender's panel locale.
Availability
Enabled per billing plan.