A white label payment gateway is ready-made payment gateway software that an operator licenses from a vendor and runs under its own brand, domain and pricing. It is for you if you sell online payment acceptance to merchants as a PSP, an acquiring bank, an electronic money institution (EMI), an independent sales organization (ISO) or a software platform.
What Is a White Label Payment Gateway?
It is a payment gateway that a vendor builds and maintains and that you sell as your own. Every operator gets a branded copy of the same platform, with its own payment pages, merchant back office, domain and price list. Merchants contract with you and see only your brand; the vendor bills you, not them.
The platform is more than a payment form. It bundles a hosted payment page, application programming interfaces (APIs), connectors to acquirers and alternative payment methods, routing, anti-fraud tools, reporting and merchant management. You configure what merchants and shoppers see; the vendor keeps one shared codebase for all its clients.
White label vs private label vs referral vs payment facilitator (PayFac)
These four models differ in who owns the brand, who owns the merchant and who carries the regulatory risk.
Model
Whose brand merchants see
Who owns the merchant relationship
Typical fit
White label gateway
The operator’s
Operator
PSPs, banks, ISOs and platforms that want their own gateway quickly on shared, vendor-maintained software
Private label
The operator’s
Operator
A product built or customized exclusively for one company and not offered to others; more control, higher cost
Referral / reseller of a branded gateway
The vendor’s
Vendor (the reseller earns commission)
Agents and consultants who want revenue without running a payment business
Payment facilitator (PayFac)
The platform’s
Platform, as sub-merchants under its master merchant account
Software platforms that take on underwriting (assessing a merchant’s risk before boarding), risk and often fund flows for their users
A white label gateway can power a PayFac or an ISO business, but it is only the technology. Your contracts and licences decide who signs with the acquirer, who holds funds and who is liable for chargebacks. Our guide to the payment gateway business model shows how each setup earns.
How Does a White Label Payment Gateway Work?
It processes a payment like any other gateway: it collects the payment details on your branded checkout, protects them, sends the transaction to an acquirer and returns the issuer’s answer to the merchant. The difference is ownership: you run the merchant-facing business and the vendor runs the software behind it.
Step-by-step transaction flow
Checkout on your brand
The shopper enters card details on your hosted payment page, your payment widget, a screen built with the gateway’s mobile SDKs (software development kits) or the merchant’s own form connected by API. In the first three, the card number goes straight to the gateway and does not pass through the merchant’s server.
Data protection and fraud screening
The gateway encrypts the card data and stores a token in place of the card number (payment tokenization). It then applies the anti-fraud rules you set, such as transaction limits, blacklists and country checks.
Cardholder authentication
Where strong customer authentication applies, as it does to electronic payments under Article 97 of PSD2, the EU’s second Payment Services Directive, the gateway’s 3-D Secure server hands the shopper to the issuer, which verifies them before authorization.
Routing to a connector
Payment routing rules that you set pick the acquirer or payment method by card type, currency, country, amount, cost or approval rate, and can retry a declined payment on a backup route.
Authorization
The acquirer sends the request through the card scheme to the issuer, which approves or declines it. The response returns along the same path.
Result to the merchant and the back office
The gateway shows the result to the shopper, notifies the merchant’s system, for example by webhook, and records the transaction in your back office and the merchant’s.
Capture, settlement and reconciliation
The merchant captures the authorized amount at once or later (a two-step payment). The scheme clears the transaction and the acquirer settles the funds, to the merchant or to you, depending on your contracts. The gateway moves no money itself; its reports let you reconcile fees, refunds and chargebacks per merchant.
Alternative payment methods (wallets, bank transfers, local schemes) replace the acquirer, scheme and issuer chain with their own provider. The gateway’s job stays the same: one integration for the merchant, many providers behind it.
PCI DSS certification of the platform, updates and patches
Support
First-line support for merchants
Technical support for you; some vendors offer merchant support as an add-on
What Does a White Label Payment Gateway Include?
A complete platform covers the whole merchant lifecycle, from the checkout to settlement reports, not only the payment form. Expect the nine components below, and check each against the acquirers, payment methods and merchant types you plan to serve.
Checkout options
Hosted payment page, embeddable widget, mobile SDKs and server-to-server API, all in your branding and in several languages.
Merchant integrations
Ready-made payment modules for shopping carts, plus payment links that merchants share by email or messenger without any website integration.
Connectors
Pre-built integrations with acquirers and alternative payment methods, and a process for adding new ones on request.
Routing and cascading
Rules that send each transaction to the best connector, and cascading logic that retries a declined payment on another route.
Security tools
Tokenization, 3-D Secure, anti-fraud rules and limits that protect card data and reduce chargebacks.
Transaction types
Card transaction types such as one- and two-step payments, refunds, voids, recurring payments and payouts, plus chargeback handling.
Merchant management
Onboarding, shop setup, fees, limits and user roles in your back office.
Reporting and finance
Transaction statistics, balances and financial statements for settlement and reconciliation, for you and for each merchant.
Multi-currency
Accepting and settling payments in many currencies, with currency conversion where the connector supports it.
If most of your volume is cards, look closely at acquirer connectors, 3-D Secure, recurring billing and chargebacks. Our guide to white-label credit card processing covers that side in detail.
Who Uses a White Label Payment Gateway?
Operators that sell payment acceptance to merchants use one: PSPs, acquiring banks, EMIs and fintechs, ISOs and software platforms. It fits when payments are part of what you sell. The table shows what each type of operator brings and what the gateway adds.
Operator
What you already have
What the gateway adds
PSPs
Merchants and acquirer agreements
Checkout, routing across your acquirers and a back office without a development team; on eComCharge a SaaS installation takes from 1 week. See our guide to a white-label solution for PSPs.
Card acceptance, so your clients receive and move money in one place.
ISOs and resellers
A portfolio of merchants boarded for acquirers
Your own brand on the gateway and the merchant relationship, instead of sending merchants to someone else’s brand.
Software platforms and marketplaces
Many sellers or subscribers on one product
Payments embedded in your product and many merchants managed from one back office. See how a SaaS payment platform works.
Note
Who does not need one: a merchant that accepts payments only for its own sales is better served by a standard gateway account from a PSP. The same goes for you if you want referral income without onboarding, support or compliance duties: a referral agreement with an existing gateway is the simpler choice.
White Label vs Building Your Own vs a Third-Party Gateway
You have three routes. License a white label gateway to sell under your own brand within weeks. Build in-house if you need full control and can fund a build that we estimate at 12 months to 2 years. Refer merchants to a third-party gateway if you want no platform to run.
Criteria
White label gateway
Build your own
Third-party gateway
Time to first transaction
On eComCharge: from 1 week (SaaS) or from 3 months (your own servers)
12 months to 2 years for a production-ready gateway (our estimate)
As fast as the provider boards each merchant
Upfront cost
Setup fee plus monthly licence
Highest: development team, infrastructure and PCI DSS certification
None for you
Brand merchants see
Yours
Yours
The provider’s
Merchant relationship and pricing
Yours
Yours
The provider’s; you may earn referral fees
Acquirers and payment methods
Vendor’s connector catalog plus new ones on request
Every connector built by your team
Whatever the provider supports
PCI DSS burden
Platform certified by the vendor; you cover your own scope
Full certification of your own platform
Mostly the provider’s
Control over roadmap
Shared with the vendor; source-code options exist
Full
None
Best for
PSPs, banks, ISOs and platforms that want speed and their own brand
Large operators with unique needs and a long horizon
Referral partners that do not want to run a platform
Time to first transaction: white label vs building in-house
White label on eComCharge, SaaS: from 1 week
White label on eComCharge, your own servers: from 3 months
In-house build: 12 months to 2 years (our estimate)
eComCharge installation times and our own estimate for an in-house build. Acquirer agreements and licensing are not included.
The build estimate is for a production-ready gateway with certification, connectors and a back office; by our estimate, basic card processing alone takes at least six months to build. Compare the routes on three-year total cost of ownership, not on launch time alone.
What Are the Benefits of a White Label Payment Gateway?
The main benefits are speed, a cost you can plan and ownership of the merchant relationship. You launch on working software, the vendor carries the platform’s certification and maintenance, and you keep the brand, the pricing and the margin.
Faster time to market
An eComCharge SaaS installation takes from 1 week and an installation on your servers from 3 months, so launch is a configuration project, not a development project. See what drives white label setup time.
Cost you can plan
Setup and licence fees replace the salaries of a gateway development team, security specialists and infrastructure engineers.
Your brand, your merchants
Merchants sign with you and see only your brand, so the customer relationship and the pricing power stay with you.
Smaller compliance load
Card data is stored and processed on a platform the vendor already certifies, which narrows the part of PCI DSS you handle yourself.
More acquirers and payment methods
Ready connectors and routing let you add local methods and backup acquirers, the basis of a multi-acquirer strategy, and enter new markets.
A new revenue line
You charge your merchants setup fees, monthly fees and a margin on each transaction.
What Are the Drawbacks, and How Do You Reduce Them?
The main drawback is dependence: your merchants run on another company’s software. Five trade-offs follow from that, and you can reduce each one in the contract or in the way you deploy.
Drawback
Why it matters
How to reduce it
Vendor dependence
Outages, price changes or a slow roadmap at the vendor hit your merchants directly.
Negotiate an uptime service level agreement (SLA), support response times and price-change terms; check the vendor’s track record.
Lock-in
Merchants, card tokens and transaction history live on the vendor’s platform.
Agree data-export formats, token migration and an exit clause in the contract.
Shared software means you can’t change everything, and new features follow the vendor’s priorities.
Check what is configurable before signing; consider on-premises or source-code options if you need deep changes.
Residual compliance
The vendor’s certificate does not cover your systems, people or merchant onboarding.
Map responsibilities in writing and keep your own scope small, for example with hosted payment pages.
Cost at low volume
Fixed fees weigh heavily until you have enough merchants.
Model break-even volume first; start on SaaS and move to another model as volume grows.
How Much Does a White Label Payment Gateway Cost?
There is no list price. You pay a setup fee, a monthly licence or maintenance fee and transaction fees, sized to your project. eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.
Setup fee: charged once, for installation, branding and initial configuration.
Monthly licence or maintenance fee: charged for software use, updates and support, and for hosting on SaaS.
Transaction fees: charged as a fixed fee per transaction, a percentage or a tiered mix.
Optional services: charged for new connectors, dedicated infrastructure or merchant support on your behalf.
Four inputs shape the quote: the deployment model, your expected transaction volume, the connectors you need and the amount of customisation. On-premises installations and lifetime licences take more capital upfront than SaaS.
Note
The software is only part of the budget. Add your own costs: licences or a licensed partner, PCI DSS for your own scope, risk and support staff, and sales. For the fee structure in detail, see our article on white label payment gateway cost.
Who Is Responsible for PCI DSS Compliance?
Responsibility is shared. The vendor certifies the platform that stores, processes and transmits card data. You remain responsible for everything outside that platform that can affect card data: your own servers and networks, staff access to the back office, merchant onboarding and the way your merchants integrate.
What the vendor’s Level 1 certification means
Card schemes classify service providers by volume. Under Visa’s service provider rules, Level 1 covers any service provider that stores, processes or transmits 300,000 or more Visa accounts or transactions a year. It validates every 12 months with an Attestation of Compliance (AOC) from a Qualified Security Assessor (QSA), and Visa can request the full Report on Compliance.
Ask your vendor for its current AOC and check which services it covers. If you are a bank weighing your own audit against a vendor’s, read our post on outsourcing PCI DSS.
How the integration method changes your scope
Smaller scope
Hosted payment page: the shopper types card data on the gateway’s page, not on the merchant’s site.
Embedded widget served by the gateway in an inline frame.
Tokens instead of card numbers for repeat and recurring payments.
Larger scope
Direct API integration where the merchant’s own form collects card data.
Storing card numbers in your own or merchants’ systems.
Unmanaged third-party scripts on payment pages.
Payment page scripts need attention. PCI DSS v4.0.1 requirements 6.4.3 and 11.6.1 took effect on 31 March 2025, according to the PCI Security Standards Council. They call for payment page scripts to be authorized and checked for integrity, and for the pages to be monitored for tampering. Confirm with your vendor how its hosted payment pages meet them.
What Do You Still Need Besides the Software?
You still need everything that turns software into a payment business: acquiring agreements, a licence or a licensed partner, merchant KYC/AML and underwriting, and people for risk, support and sales. The gateway connects these parts; it does not supply them.
A licence or a licensed partner
Depending on the country and the fund flow, you need your own licence or work under a licensed institution. In the EU, a payment institution that acquires payment transactions must hold initial capital of at least €125,000 under Article 7 of PSD2, and an e-money institution at least €350,000 under Article 4 of EMD2, the second Electronic Money Directive. Read more about payment service licences.
Acquiring agreements
Contracts with acquirers and alternative payment method providers that will accept your merchants. The gateway connects to them; it does not replace them.
KYC/AML and underwriting
Procedures to verify merchants, assess their risk, set limits and reserves, and monitor transactions for money laundering.
Risk, support and sales teams
People who handle chargebacks and fraud, answer merchants and bring in new ones.
Illustrative example
From contract to first transaction
Assumptions: you are a technical PSP that does not hold merchant funds, one acquirer agreement is signed, you deploy on SaaS, and your first 20 merchants use the hosted payment page. The week ranges are illustrative, not a quote.
Week 1: the vendor installs and brands the platform (an eComCharge SaaS installation takes from 1 week).
Weeks 2–8: the vendor configures the acquirer connector; you and the acquirer run test transactions.
Weeks 4–12: you verify and board the merchants; each merchant connects the hosted payment page.
Result: a first live transaction after roughly 1 to 3 months, most of it spent on the acquirer and the merchants, not on the software.
For the full sequence of business model, licensing, banking partners, technology and launch, see our guide on how to start a payment processing company.
Which Deployment Model Fits You: SaaS, On-Premises or Lifetime Licence?
Pick SaaS for the fastest launch and the smallest team, on-premises when data residency or IT policy requires your own servers, and a lifetime licence when you want full control of the system. The model decides who hosts, how fast you start and how much PCI DSS scope returns to you.
Model
Who hosts
Typical launch (eComCharge)
Best for
SaaS
Vendor, in its certified environment
From 1 week
Fast launch, lower upfront cost, no infrastructure team
On-premises
Operator, on its own servers
From 3 months
Data residency rules, banks with strict IT policies
Lifetime licence
Operator, on its own servers
From 3 months
High-volume operators that want full control of the system
On-premises and licence models move hosting, uptime and part of the compliance work back to you, in exchange for control. You can start on SaaS and reconsider once volume and team size grow. Our posts on the SaaS payment gateway and the on-premises payment gateway describe each model.
How Do You Choose a White Label Payment Gateway Provider?
Shortlist vendors that already connect your target acquirers, hold a current PCI DSS Attestation of Compliance and let you leave with your merchants and tokens. Then put the same six questions to each one and get the answers in writing.
Connectors
Are your target acquirers and local payment methods already integrated? How long does a new connector take, and who pays for it?
Security and compliance
Does the vendor hold a current PCI DSS Attestation of Compliance, and will it give you a written split of responsibilities?
Branding depth
Can you brand the payment page, widget, back office, emails and domain, not just upload a logo?
Merchant integrations
Which integrations do merchants get: API documentation, mobile SDKs, e-commerce plugins, payment links? Our white-label API checklist lists what your technical team should verify.
Reliability and support
What uptime does the SLA commit to, and is technical support available round the clock?
Pricing and exit terms
What are the fees, who owns the data, and how do you leave with your merchants and tokens?
eComCharge develops a white label payment gateway for PSPs, acquiring banks and platforms that serve online merchants. You brand the payment page, widget and back office as your own and choose SaaS (installation from 1 week), on-premises or lifetime-licence deployment (from 3 months).
PCI DSS Level 1 compliant, with annual security audits since 2012.
170+ active connectors with banks and payment methods, and new connectors developed on request.
Hosted payment page, payment widget, mobile SDKs, 40+ e-commerce plugins and payment links.
A white label payment gateway is ready-made payment gateway software that a PSP, bank, acquirer or platform licenses from a vendor and offers to merchants under its own brand. The vendor builds, maintains and certifies the platform; you own the brand, the merchants and the pricing.
It works like any payment gateway, only under your brand. The shopper pays on your branded checkout, the gateway tokenizes the card data, applies fraud rules and 3-D Secure, and routes the transaction to an acquirer. The issuer approves or declines it, and the gateway sends the result to the merchant and records it in the back office for reconciliation.
The gateway collects and routes the payment, the processor carries the transaction messages between the acquirer and the card networks, and the acquirer is the bank or licensed institution that accepts the payment for the merchant and settles the funds. A white label gateway replaces only the gateway layer; you still need acquiring partners behind it.
A white label gateway is shared software that many operators rebrand, while a private label product is built or customized exclusively for one company. White label is faster to launch because the platform already exists; private label gives you more control at a higher cost.
You pay a setup fee, a monthly licence or maintenance fee and transaction fees. eComCharge pricing depends strictly on your specific needs, such as the deployment model, transaction volume, connectors and customisation, so contact our sales team for a quote. Add your own costs for licensing, compliance and staff.
With eComCharge, a SaaS installation takes from 1 week and an installation on your own servers from 3 months. Acquirer agreements, licensing and merchant onboarding come on top and usually take longer than the software. For comparison, we estimate 12 months to 2 years to build a production-ready gateway in-house.
Responsibility is shared between the vendor and you. The vendor certifies the platform that handles card data; you stay responsible for your own systems, staff access, merchant onboarding and integration choices. Hosted payment pages and tokenization keep your own scope small.
It depends on your country and on whether you hold or move merchants’ funds. You may need a payment institution or e-money licence, or you can work under a licensed partner or acquirer. In the EU the minimum initial capital is €125,000 for a payment institution that acquires payments and €350,000 for an e-money institution.
Yes, that is the main reason PSPs and platforms use one. You charge merchants setup fees, monthly fees and a margin on each transaction, and you keep the difference between what you charge and what you pay the vendor and your acquirers.
Yes, if your contract allows it. Agree in advance on export of merchant data and transaction history, migration of stored card tokens and an exit clause; without them, switching providers can mean collecting card details from shoppers again.
Respectfully, the eComCharge Team
eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.
How PSPs and acquirers process high-risk card payments: which merchants count as high risk, who carries the liability, Visa VAMP thresholds, reserves and limits, the gateway features you need, multiple acquirers and the risks.
A practitioner's guide to launching a payment service provider: choosing a model, signing an acquirer, licensing, PCI DSS, platform choice, cost drivers and a 9-step launch plan.
How PSPs, acquiring banks and EMIs onboard high-risk merchants: which MCCs count as high risk, the KYB, UBO and sanctions checks EU law requires, underwriting and reserves, Visa registration and monitoring, what to automate and how to keep an evidence trail.
How a PSP protects itself from a sudden acquirer shut-off, outage or limit change: concentration risk, scheme and underwriting triggers, backup acquirers, portable tokens, volume split, an outage runbook, costs and who does not need it.
A guide to cascading payments for PSPs and acquiring banks: soft, hard and technical declines, which Visa response codes may cascade, cascade design, duplicate-charge prevention, 3DS, scheme rules, recovery KPIs and who should not cascade.
A guide for PSPs, banks and platforms on custom payment solutions: custom build vs off-the-shelf vs white-label, what can be customised, how a connector or payout flow is scoped and delivered, what drives cost and time, and the risks.