The checkout is the only part of your payment platform that your merchants' customers ever see. A white label checkout puts your merchant's brand, or yours, on that page, shows the payment methods each shopper expects, and keeps card data away from the merchant's servers.
This page explains what our checkout does, the ways a merchant can put it on a site or in an app, and how it handles cards that pay every month.
What shoppers see on the page
A white label checkout page should feel like part of the merchant's site, not a detour to somebody else's. Ours is fully customizable, with layout and styling that follow the brand down to the logos and buttons, and the page can be hosted on your domain so the address bar never shows a third party.
It also works on any screen, so a shopper on a phone gets the same page as one on a laptop.
Payment methods shown by location
Shoppers drop off when they can't find the method they use. Our checkout shows the relevant ones automatically, choosing between cards, mobile wallets, buy now pay later and alternative payment methods based on the shopper's location, language and behavior.
A shopper in one country might see a local bank method first, while another sees Apple Pay or Google Pay at the top. The methods come from the 700+ connectors on the platform, so adding a market usually means switching a method on rather than building a new page.
Ways to put a white label checkout on a site or in an app
Merchants differ in how much they want to build and how much card data they want to touch. The platform gives them four options, and they can mix them.
| Option | How it works | Who handles the card data |
|---|---|---|
| Hosted payment page | The shopper pays on a branded page that we host, on your domain | The platform's page |
| Embedded fields (JS SDK) | Secure payment inputs sit inside the merchant's own checkout | The platform's secure inputs |
| Mobile SDKs | Payment screens inside iOS and Android apps | The SDK inside the app |
| Host-to-host API | The merchant collects card data and sends it to the gateway | The merchant's servers, so it needs its own PCI DSS validation |
Merchants who'd rather not handle card data pick one of the first three, which usually keeps their PCI DSS work smaller. CMS plugins cover merchants on common store platforms. Our page on API and integration lists what each option needs from a developer.
The white label paypage, step by step
The hosted page is the option most merchants start with, so here's what happens during one payment:
- The merchant's site sends the order to the gateway and gets back a link to the payment page.
- The shopper lands on the branded page and picks a method from the ones shown for their location.
- Card details are tokenized, and fraud filters and 3-D Secure run where your rules ask for them.
- Your routing rules send the payment to an acquirer, and a soft decline can cascade to another one.
- The shopper returns to the merchant's site, and the result appears in both dashboards.
The merchant writes code for steps 1 and 5 only. Everything between them is ours to run and yours to brand.
Recurring payments and stored cards
Subscriptions break when cards expire or get reissued. The checkout stores cards as tokens and keeps them updated automatically, and network tokenization protects card data at the network level so recurring payments keep working after a bank sends a customer a new card.
Wallet payments can recur too. Apple Pay and Google Pay are supported as tokenized methods for subscriptions, so a shopper who pays with a phone once doesn't have to type a card number for the next charge.
Fraud checks inside the checkout
Every payment through the page can pass through 150 built-in configurable fraud filters before it reaches an acquirer, plus 3-D Secure, including an external MPI if you already use one. Third-party risk tools can sit in the same flow.
You decide which checks apply to which merchants and amounts. A low-risk subscription and a first-time high-value order don't need the same friction, and the rules let you treat them differently. More on the rules themselves is in our guide to fraud prevention for PSPs.
Questions
Can the checkout run on the merchant's own domain?
Yes. The payment page can be hosted on your domain and styled to the brand, so shoppers don't see a third-party address or logo.
Which payment methods can shoppers use?
Cards, mobile wallets such as Apple Pay and Google Pay, buy now pay later and alternative payment methods. The page picks the relevant ones for each shopper.
Does the hosted payment page work in mobile apps?
For apps, merchants use the iOS and Android SDKs, which put the payment screens inside the app instead of opening a web page.
Who needs PCI DSS validation with a white label checkout?
The platform's SaaS is PCI DSS Level 1 certified. Merchants who use the hosted page or one of the SDKs leave card handling to the platform. Merchants on host-to-host handle card data themselves and need their own validation.