Skip to content

Platform

White Label Gateway Branding: Domain, Pages and Reports

A merchant who signs with your PSP should never find another company's name in its admin panel, on its checkout or in its monthly statement. If it does, it starts wondering who it's really working with, and whether it could go to them directly.

That's what white label gateway branding protects. This page lists every surface of the gateway, who sees it, what you can brand on it, and the few screens in any payment flow that belong to someone else by design.

White label gateway branding, surface by surface

A gateway has more screens than most buyers expect. Shoppers see one or two of them, your merchants see several, and your team works in the rest.

Surface Who sees it What carries your brand
Hosted payment page Shoppers Your domain in the URL, logo, buttons, colors and layout, 25+ languages
Embedded checkout (JS SDK) Shoppers The merchant's own page, styled to match, hosted on your domain
Admin panel Your team Your URL and logo
Merchant dashboard Your merchants Your URL, logo and the reports they download
Reports and statements Merchants and finance teams Your logo and name on transaction reports and settlement statements
Mobile SDKs Shoppers in merchant apps The merchant's app, with your checkout inside

In our gateway your brand goes on the payment page and admin panel URLs, on the logos and buttons, and on every report. Our name appears nowhere your merchants or their shoppers can see it.

The screens nobody can brand

Some screens in a payment belong to other parties, and no gateway can put your logo on them. Knowing them up front saves an awkward conversation with a merchant who asks why the checkout "changed".

  • The 3-D Secure challenge comes from the card issuer, so the shopper sees the issuing bank's screen or app.
  • Apple Pay and Google Pay open their own payment sheets.
  • Local methods such as bank redirects send the shopper to the bank's own page.
  • The line on a cardholder's statement is the merchant descriptor, which the acquirer and the merchant set.

None of these weaken your brand, because shoppers expect them. Your page frames them, and the shopper comes back to your branded result screen at the end.

Branding on your own domain

The domain matters most for trust. A payment page on pay.yourbrand.com tells shoppers and merchants the same thing your logo does, and it keeps working if a merchant checks the URL before entering card details.

Both the payment page and the admin panel run on your domain. On SaaS we host them for you. In your own cloud account or on your own servers, they run inside your infrastructure under the same addresses.

The logo is the easy part. A merchant judges a branded PSP service by everything around it, and that's where most launches show the vendor underneath.

Check that merchant onboarding forms, merchant IDs and support contacts all point to you, and that pricing plans and settlement schedules are yours to set per merchant rather than fixed by the vendor. Integration options should come under your name too, so a merchant's developer installs your plugin or SDK and then logs into a merchant portal that shows your logo.

Checklist before you launch your brand

Test before the first merchant signs. Run each step below on a test merchant, because each one is a place where a missed setting shows through.

  1. Open the hosted payment page on a phone and on a desktop, and check the URL, logo and button colors.
  2. Run a test payment with a 3-D Secure challenge and confirm the result screen is yours.
  3. Download a transaction report and a settlement statement as the merchant would.
  4. Log into the merchant dashboard with merchant credentials, not admin ones.
  5. Install the CMS plugin on a test store and read every label it shows.

Fix anything that shows a placeholder or the wrong name now, since every merchant you onboard afterwards will see the same thing.

Questions

Which white label payment gateway provider is best to launch my own branded payment service?

One where your brand reaches every screen a merchant sees, including URLs, reports and the admin panel, and where you keep your own acquirer contracts. Check both in a demo with a test merchant rather than on a feature list.

How quickly can I launch a branded PSP service?

On SaaS with connectors that already exist, the first live payment usually goes through in about 5 business days. Self-hosting adds time, roughly 30 days in a cloud account and 60 on dedicated servers.

Can each merchant's checkout look different?

Yes. The payment page layout and styling can be adjusted, and the JS SDK lets a merchant fit the checkout into its own site design.

Will my merchants know which software I use?

Not from the payment page, the admin panel, the dashboard or the reports, which all carry your brand and your domain. Check the CMS plugin labels on a test store too, since merchants install those themselves.

See your brand on a live gateway

Send us your logo and domain, and we'll show the payment page and merchant dashboard under your name.