Online stores judge a payment provider at two moments: when a shopper pays, and when something goes back. The first decides conversion. The second, refunds and disputes, decides how much work the store's finance team does and how much of its margin survives.
A white label payment gateway for e-commerce lets a PSP, an acquiring bank or a commerce platform serve online stores under its own brand, with the checkout, the payment methods and the back office already built. This page covers what e-commerce merchants need, the refund load that comes with them, and what to configure first.
What online stores need from their payment provider
E-commerce merchants differ from in-store ones in a few ways that shape the setup. The table shows the main needs and what each one asks of the platform.
| Need | Why it matters online | What the platform has to do |
|---|---|---|
| Local payment methods | Shoppers abandon checkouts that don't offer the way they pay | Show cards, wallets, BNPL and local methods by country |
| Fast, branded checkout | Every extra step costs sales | A hosted page on your domain, or embedded fields |
| Refunds without friction | Returns are a normal part of online retail | Full and partial refunds from the dashboard or API |
| Dispute handling | Card-not-present payments draw more chargebacks | Case tracking with evidence and deadlines |
| Plugins for store platforms | Many merchants run on a store builder | CMS plugins, alongside the API |
| Multi-currency | Cross-border sales are common | Pricing and settlement in several currencies |
The refunds row is the one PSPs underestimate. Their software has to handle it as well as it handles a sale, or support costs grow with every merchant.
The refund and returns load
Returns are large in online retail. The US National Retail Federation's 2025 Retail Returns Landscape projected that 19.3% of online sales would be returned in 2025, and it estimated that 9% of all returns are fraudulent.
For a PSP, that means a steady stream of refunds and some disputes on every e-commerce merchant. Take a hypothetical store with $200,000 of monthly online sales. At a 19.3% return rate, about $38,600 of that comes back in refunds each month, and each refund has to be matched to its original payment, deducted from settlement and shown on the merchant's statement.
White label payment solutions for e-commerce: what to configure first
This order gets a PSP's first online stores live without rework.
- Choose the checkout per merchant: a hosted payment page on your domain, embedded fields through the JavaScript SDK, or a CMS plugin.
- Turn on the payment methods each merchant's market expects, shown by the shopper's location and language.
- Set refund rules, including partial refunds and who in the merchant's team can issue them.
- Configure fraud filters per merchant before the first sales, since online stores are tested by fraudsters quickly.
- Set settlement schedules and reserves, especially for stores that sell goods delivered later.
- Give each merchant its dashboard with sales, refunds, disputes and payouts in one view.
The fifth step matters most for stores that take preorders or ship weeks after payment. A reserve covers refunds that arrive after the money has already been paid out.
White label payment solutions for retail
Retailers that sell both online and in stores want one view of their payments. A PSP serving them needs online checkout alongside in-store acceptance from its acquirers, with reporting that brings both into the same merchant dashboard. The gateway handles the online side and the merchant management, while in-store terminals usually come through the acquirer or a terminal partner.
Our white label payment gateway for e-commerce
Our white label gateway runs the checkout and back office under your brand. The payment page is customizable and hosted on your domain, and it picks which cards, wallets and local methods to show from the shopper's location and language. It's on your domain. Merchants can also connect through host-to-host API or CMS plugins, and mobile apps use the iOS and Android SDKs.
Behind the checkout, 700+ ready connectors reach acquirers and payment methods, and 150 configurable fraud filters can be set per merchant. The checkout supports tokenized cards that stay up to date for repeat buyers, and the merchant side handles refunds and chargeback workflows through to settlement.
Questions
What is a white label payment gateway for ecommerce?
Gateway software that a PSP, bank or platform runs under its own brand to give online stores a checkout, payment methods, refunds and a merchant dashboard, without building the gateway itself.
Which payment methods do online stores need?
Cards and mobile wallets almost everywhere, plus the local methods of each market they sell into, such as bank transfers, BNPL or national schemes.
How do PSPs handle refunds for e-commerce merchants?
Through the gateway's refund tools, with full and partial refunds matched to the original payment and deducted at settlement, and reserves for merchants whose goods ship long after payment.
Can a white label gateway work with Shopify-style store builders?
Yes, through CMS plugins where they exist for the store platform, or through the API and hosted checkout.