A white-label payment platform is payment processing software that a vendor builds and maintains and that you run under your own brand, with your own merchants, acquirers and pricing. This buyer’s guide is for PSPs, acquiring banks and platforms comparing vendors: 12 criteria, a scoring method and an exit checklist, with no vendor ranking.
What Is a White-Label Payment Platform, and What Is It Not?
It is a complete payment stack that you license instead of building, all under your brand: checkout, connectors (ready integrations with acquirers and payment methods), routing (rules that choose the acquirer for each payment), a card vault (PCI DSS storage that swaps card numbers for tokens) and a merchant back office. The vendor stays invisible to your merchants.
Our guide to the white-label payment gateway explains how one works; this guide helps you choose one. Vendors use “white label” for four different products, so check which one each vendor sells before you compare features.
Option
What you get
Fits you if
White-label gateway platform
Gateway software, checkout and merchant management under your brand. You connect your own acquirers and payment methods.
You are a PSP, an acquiring bank or a payment institution
Payment facilitator (PayFac) programme
Your users are boarded as sub-merchants under the facilitator’s master merchant account and its acquirer agreement. Branding is usually limited.
You run a software platform or marketplace and want no licence of your own
Routing and a token vault on top of gateways and PSPs you already use. It usually has no merchant back office of its own.
You already run several gateways and want one routing layer above them
In-house build
Full control and full responsibility for development, certification and maintenance. We estimate 12 months to 2 years for a production-ready gateway.
You have a dedicated payments engineering team and a long horizon
The rest of this guide is about the first row: software that you run as your own gateway.
Which Type of Provider Do You Need, and Who Holds the Licence?
You need a software vendor if you hold a licence or contract acquirers directly, and an acquiring-led PSP if you want to resell under someone else’s licence. The provider type decides whose licence, whose acquirer agreements and whose PCI DSS scope your business runs on.
PCI DSS is the easiest of the three to verify. Under Visa’s service provider rules, a Level 1 service provider stores, processes or transmits 300,000 or more Visa accounts or transactions a year. It validates every 12 months with an AOC from a Qualified Security Assessor (QSA). Ask each vendor for that document before the demo.
Provider type
Licence and acquiring
PCI DSS scope
Chargeback liability
Your control
Gateway software vendor (SaaS or licence)
Yours: you hold the licence or contract acquirers directly
Shared: the vendor certifies the platform; you cover your own systems and staff, and the infrastructure too if you host it
Set by your merchant and acquirer agreements; the software vendor is not a party to them
High: merchants, pricing, routing and acquirers are yours
Acquiring-led PSP with a branded checkout
The provider’s; you act as a reseller, an independent sales organization (ISO) or a referral partner
Mostly the provider’s
The provider underwrites the merchants (assesses their risk before boarding) and answers to its acquirer for them
Low to medium: you depend on the provider’s underwriting and pricing
Orchestration layer
Held by the gateways and PSPs underneath
The orchestrator for its vault; the underlying PSPs for processing
Stays with the underlying PSPs and acquirers, as each contract sets out
Medium: you control routing, not the merchant back office
If you hold no licence and plan none, software alone will not change that: you still need an acquirer or a licensed partner. Read what payment service licences cover, and how each setup earns in our guide to the payment gateway business model.
SaaS vs On-Premises vs Hybrid: Which Deployment Fits You?
Choose SaaS when speed matters more than control. Choose on-premises when your regulator, your IT policy or data-residency rules (rules on where card data may be stored) require your own servers. Pick a vendor that offers both if that answer may change. Deployment also decides how PCI DSS scope is split between you and the vendor.
SaaS
The vendor hosts and operates the platform, on shared infrastructure or on a dedicated instance that serves only you. On eComCharge, installation takes from 1 week.
Fits you if you want the fastest launch, have a small technical team and want most PCI DSS scope to stay with the vendor.
On-premises
The vendor installs the platform on your servers. You run the hosting and decide where data is stored. On eComCharge, installation takes from 3 months.
Fits you if you are a bank or regulated institution with data-residency rules and your own IT and security team.
Hybrid
Some components run with the vendor and others with you, for example vendor-hosted processing with data stored in your own region.
Fits you if you need some control now and may move on-premises later.
Ask each vendor whether it also sells a lifetime licence (a one-off purchase of the software, installed on your servers) or a source-code licence (you also receive the code). That model takes more capital upfront than SaaS, moves hosting, audits and staffing to you, and changes your exit options. Our posts on the SaaS payment gateway and the on-premises payment gateway describe each model in detail.
Which 12 Criteria Should You Use to Compare White-Label Payment Platforms?
Compare every vendor on the same 12 criteria: compliance, deployment, connectors, routing, tokenization, 3-D Secure, anti-fraud, back office, reconciliation, payouts, reliability and commercial terms. For each one, put the question in writing, ask for the evidence and watch for the red flag.
Criterion
Why it matters
What to ask
Red flag
1. Compliance
Certification is costly to obtain and to keep; see our post on outsourcing PCI DSS
Can I see your PCI DSS Level 1 AOC, issued within the last 12 months? Which requirements are yours and which are mine?
No AOC, an expired one, or one that does not cover the service you are buying
2. Deployment model
Sets launch speed, data residency and PCI DSS scope
SaaS, dedicated instance or on-premises? Where is the data hosted? Can I change model later?
One model only, with no path to change
3. Connectors
Your markets depend on connectors that already work, and a multi-acquirer strategy needs several
Which connectors carry live traffic in my markets today? How long does a new one take, who pays for it and who maintains it?
“Supported” lists with no live traffic; open-ended timelines
4. Routing and cascading
Payment routing drives approval rates, cost and resilience when an acquirer fails
Which conditions can rules use: bank identification number (BIN), country, currency, amount, card type, 3-D Secure result? Does cascading logic retry a declined payment on another acquirer? Can rules differ per merchant?
Static assignment only; every rule change needs a vendor ticket
5. Tokenization
Payment tokenization enables recurring and one-click payments, and the freedom to change acquirer
Is there a PCI DSS card vault? Are network tokens (tokens issued by the card scheme) supported? Can tokens be migrated or exported?
Tokens usable only inside the vendor’s system
6. 3-D Secure (3DS)
In the EU, Article 97 of PSD2, the second Payment Services Directive, requires strong customer authentication when a payer initiates an electronic payment
Is the 3DS server your own and certified, or a third party’s? Does it run EMV 3DS, the version 2 protocol published by the standards body EMVCo? Can my rules decide when a challenge is requested?
No control over when 3DS is applied; per-request fees missing from the quote
7. Anti-fraud
Fraud drives chargebacks and can put you into a card scheme monitoring programme
Which anti-fraud tools are built in: rules, limits, block and allow lists? Which third-party tools connect? How are chargebacks handled?
Fraud control sold only as an opaque paid add-on
8. Merchant onboarding and back office
Your team works here every day
Is there a hierarchy of PSP, reseller, merchant and shop? A KYC workflow? Roles and permissions? Is the merchant portal branded as mine?
Vendor branding visible to merchants; a flat merchant structure
9. Reporting and reconciliation
Fees, settlements and disputes must reconcile to the cent
Are fees calculated per merchant? Do financial statements match acquirer reports? Is there a reporting interface for my finance system?
Reconciliation done by hand in spreadsheets
10. Payouts
Marketplaces and gaming operators send money as well as collect it, which takes a white label payouts system
Do you support card payouts, bank payouts and mass payouts? Is there balance management?
Payouts “on the roadmap” when your merchants need them now
11. Reliability and support
Downtime stops every merchant at once
What uptime is in the SLA, and with what credits? Is support available 24/7? How do you report incidents?
Uptime quoted in marketing and missing from the contract
12. Commercial model and exit
Total cost and the freedom to leave
What are the setup, monthly and transaction fees? What is the contract term? How do I export data and tokens when I leave?
A long auto-renewing term with no exit assistance
Weight the criteria to your model. If you are a bank, deployment and compliance weigh most. If you serve high-risk merchants, routing, connectors and anti-fraud do. If you pay out to sellers, payouts and reconciliation do.
How Is a White-Label Payment Platform Priced?
There is no list price. A quote combines a setup fee, a monthly licence or maintenance fee and transaction fees. 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. It gives you a fixed cost you can plan.
Transaction fees
Charged as a fixed fee per transaction, a percentage or a tiered mix. They grow with your volume, so check the tiers.
Four inputs shape the quote: the deployment model, your expected transaction volume, the connectors you need and the amount of customisation. Lifetime licences and on-premises installations take more capital upfront and add hosting, PCI DSS audits and staff on your side. Our post on white label payment gateway price explains each fee.
Compare quotes on three-year total cost of ownership at your expected volume, not on the setup fee. A percentage fee that looks small at launch can become your largest cost line once volume grows.
How Long Does It Take to Launch?
The software is the short part. An eComCharge SaaS installation takes from 1 week and an installation on your own servers from 3 months. Acquirer agreements, connector testing and merchant onboarding usually take longer, so ask each vendor what its launch time includes.
Platform installation: the vendor
The vendor installs and brands the platform: on eComCharge, from 1 week on SaaS and from 3 months on your servers. You supply the domain, the logo and colors, and the list of back-office users.
Acquirer contracts and connectors: you, the acquirer and the vendor
You sign the acquirer agreements. The vendor configures the connector or builds a missing one. You and the acquirer then run test transactions before the connector carries live traffic. This stage is often the critical path.
Compliance and merchant onboarding: you and your merchants
You prepare the licence or partner agreement, the KYC policy and the risk rules, and you verify the first merchants. Each merchant then connects its checkout; our post shows three ways to integrate merchants with your gateway.
When a vendor quotes a launch time, ask whether it covers stage 1 only or all three, up to your first live merchant. Our post on white label setup time explains what drives each stage.
What Should You Check Beyond the Feature List?
Check four things that a feature grid reduces to a tick: network tokens, who runs the 3DS server, payouts and the SLA. Two platforms can tick all four and still differ in what you control.
Network tokens
A gateway token works only inside the vault of the platform that created it. A network token comes from a scheme service such as Visa Token Service or Mastercard Secure Card on File. Ask which of those services the platform is connected to, for each card scheme you process.
Who runs the 3DS server
A third-party 3DS service adds another contract and another dependency between you and the issuer. With the server inside the platform, 3DS rules sit next to your routing rules, and one rule set decides which payments go through 3DS and when a challenge is requested; the issuer makes the final decision. Our post on low-risk transactions without 3-D Secure shows an example.
Payouts
Supporting payouts and reconciling them are different things. Check that payouts appear in the same reconciliation reports as incoming payments, per merchant, so your finance team does not match two systems by hand.
SLA
Ask how uptime is measured: over which period, with or without planned maintenance, and for the whole platform or per component. Ask too whether the failure of one connector can affect the rest of the platform.
What Are the Risks of a White-Label Payment Platform, and How Do You Plan the Exit?
The main risk is lock-in: your stored card tokens, merchant integrations and transaction history sit on another company’s platform. Each risk below has a contract term that reduces it. Negotiate those terms before you sign, while the vendor is still competing for your contract.
Risk
What it looks like
What to get in writing
Token lock-in
Tokens cannot leave the vendor’s vault, so shoppers would have to enter their cards again
Export of card data and tokens to your next provider, from one PCI DSS-certified environment to another. In one eComCharge token migration, 95% of the tokens the previous acquirer made available moved to a new acquirer in about one week.
Data lock-in
Exports are charged per request or limited to summaries
Full transaction, merchant and settlement history in a documented format, at a stated price
Merchant re-integration
A proprietary merchant interface with no compatibility layer, so every merchant has to integrate again
Versioning of the merchant interface and a notice period before any version is retired
Contract lock-in
A long auto-renewing term with high early-termination fees
A notice period, a transition window and migration support from the vendor
Vendor failure
The vendor stops trading or stops developing the product you depend on
A source-code licence, or escrow: a copy of the code held by a third party and released to you if the vendor fails
Big-bang migration
The only way in or out is to switch all traffic on one day
The right to run the old and the new platform in parallel for an agreed period
If you are replacing a platform, ask the new vendor to run in parallel with the current one. Send one new channel to the new platform first, then move merchants in batches. Our legacy migration guide describes that sequence for a bank’s acquiring stack.
Which Setup Fits Your Type of Business?
It depends on what you already hold. As a new PSP you will usually start on SaaS, as a bank on your own servers, and as a high-risk PSP wherever routing is deepest. If you only refer merchants, or only sell your own goods, you do not need a platform at all.
New PSP
Put speed, live connectors in your markets and a back office that a small team can run first. SaaS is usually the right start. See white-label processing for low-risk PSPs.
Bank or acquirer
Put on-premises or a dedicated instance, data residency, your own 3DS server and reconciliation against your processing reports first. See white-label processing for European banks.
ISO or reseller
You may not need your own gateway. A branded checkout from an acquiring-led PSP can be enough. Choose a platform only if you want to own pricing, routing and the merchant relationship.
Look for many acquirers, rule-based routing and cascading, new connectors on request, rule-driven 3DS and strong anti-fraud. Routing depth matters more than the feature count. See processing for iGaming and forex PSPs.
PSP replacing a legacy gateway
Token migration, a compatible interface for existing merchants, a parallel launch and data import decide your project. Apply the risk table above to your current vendor as well.
Note
Who does not need a white-label payment platform: a merchant that accepts payments only for its own sales is better served by a standard gateway account from a PSP. If you want referral income without onboarding, support or compliance duties, a referral agreement with an existing gateway is the simpler choice.
How Do You Run the Evaluation Before You Sign?
Run it in six steps: fix your must-haves, send every vendor the same written questions, test in a sandbox, check the evidence, score the answers and put the exit terms into the contract. Each step has an owner on your side.
Must-haves (you): write down your licence model, markets, acquirers and deployment model. A vendor that misses a must-have leaves the list, whatever it scores later.
Written questions (you, then each vendor): send the “What to ask” column of the 12 criteria and ask for answers in writing.
Sandbox test (your technical team): test the application programming interface (API) documentation, webhooks (server-to-server notifications) and software development kits (SDKs) against our white-label API checklist.
Evidence (your compliance lead): read the AOC and the responsibility matrix, the document that splits PCI DSS requirements between the vendor and you. Speak to one of the vendor’s clients with a business model like yours.
Scoring (you): score each criterion from 1 to 5, multiply by its weight and add up, as in the example below.
Contract (your legal and commercial leads): put the fee schedule, the SLA and the exit terms into the contract before you sign.
Illustrative example: scoring two vendors
Assumptions: you are a cross-border PSP that serves high-risk merchants, so connectors and routing carry half the weight. Vendors A and B are invented. The weights and scores are illustrative; a score runs from 1 (fails) to 5 (fully meets), and the weighted value is in brackets.
Criteria group
Weight
Vendor A
Vendor B
Connectors live in your markets
25%
5 (1.25)
3 (0.75)
Routing and cascading
25%
3 (0.75)
5 (1.25)
3DS, tokenization and anti-fraud
20%
4 (0.80)
4 (0.80)
Back office and reconciliation
15%
4 (0.60)
3 (0.45)
Commercial terms and exit
15%
2 (0.30)
4 (0.60)
Weighted total
100%
3.70
3.85
Vendor B wins narrowly, although Vendor A has more live connectors. Read the low scores before the total. Suppose A’s 2 on exit terms comes from tokens that cannot be exported: if token export is one of your must-haves, A leaves the list at step 1 and the arithmetic is not needed.
Where eComCharge Fits
eComCharge publishes this guide and sells one of the options in it, so score it on the same 12 criteria as any other vendor. Its platform is white-label payment gateway software: you bring the licence and the acquirer agreements, and the platform runs under your brand.
These facts from our product pages map to the criteria above:
Compliance: PCI DSS Level 1, with annual security audits since 2012.
Deployment: SaaS installation from 1 week; on-premises installation or a lifetime licence on your servers from 3 months.
Connectors: 170+ active connectors with banks and payment methods, and new connectors developed on request.
Routing: Smart Routing with 50+ conditions, sequential fallback and rules set at PSP, merchant or shop level. Anti-fraud and 3DS rules run in the same engine.
3-D Secure: an in-house 3DS Server and MPI (merchant plug-in) on EMV 3DS 2.0, certified by Visa, Mastercard and UnionPay, with rules that skip, request or force the challenge.
Tokenization: a local card vault at PCI DSS Level 1, with Visa Token Service supported since 2022 and Mastercard Secure Card on File since 2024.
Merchant tooling: a branded payment page and widget, mobile SDKs, payment links, 40+ e-commerce plugins, 25+ languages and 24/7 technical support.
A good fit if you
are a PSP, acquiring bank or payment institution launching or replacing an online gateway under your own brand
want the choice between SaaS and on-premises deployment from one supplier
need rule-based routing across several acquirers, with 3DS and anti-fraud in the same rules
want PCI DSS Level 1 and a certified 3DS server without building them yourself
Not a fit if you
are a merchant looking for a merchant account, not a platform to serve merchants
need the vendor to hold the regulatory licence and the acquiring for you; eComCharge provides technology, not a licence
want to build and own every component in-house with your own engineering team
Frequently asked questions
There is no single best white-label payment platform; the best one fits your licence model, your target markets, your acquirers and how much of the stack you want to run. Shortlist vendors on the same criteria (compliance, deployment model, live connectors, routing, tokenization and 3-D Secure, back office, pricing and exit terms), then test them in a sandbox and speak to a client with a business model like yours.
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. Lifetime licences and on-premises installations take more capital upfront, so compare quotes on three-year total cost at your expected volume.
With eComCharge, a SaaS installation takes from 1 week and an installation on your own servers from 3 months. The critical path is often outside the software: signing acquirers, testing connectors and onboarding merchants. When a vendor quotes a launch time, ask whether it includes your acquirers and your first live merchant.
Choose SaaS if speed and a small technical team matter most, and on-premises if data-residency rules or your IT policy require the platform on your own servers. SaaS keeps most PCI DSS scope with the vendor. On-premises gives you more control but adds hosting, audits and staff to your side. A vendor that offers both lets you change your mind later.
Usually you need less than if you built the gateway yourself, but you are not out of scope. Responsibility is shared: the vendor certifies its platform and should show you a current PCI DSS Level 1 Attestation of Compliance. You remain responsible for your own systems and processes, and for the infrastructure as well if you host on-premises. Ask for a responsibility matrix that shows who covers which requirement.
A white-label payment platform is the full gateway you run under your brand, while an orchestration layer sits on top of gateways and PSPs you already use. The platform includes a merchant back office, a checkout and acquirer connectors. Orchestration focuses on routing and a token vault across existing providers and usually has no merchant back office of its own.
Yes, if you secured the right terms before signing. You need an export of card data and tokens from one PCI DSS-certified environment to another, a full export of transaction and merchant history, a versioned merchant interface and exit assistance in the contract. A parallel run, with one new channel on the new platform first, lowers the migration risk.
Many do, but the depth varies a lot between platforms. Ask which conditions rules can use (BIN, country, currency, amount, card type, 3-D Secure result), whether a declined payment can be retried on another acquirer, and whether you can change rules yourself per merchant and per shop without opening a vendor ticket.
You can, but it takes longer than licensing white-label software. We estimate 12 months to 2 years for a production-ready gateway, before the ongoing work of PCI DSS audits, 3-D Secure certification and connector maintenance. Building in-house makes sense mainly if you have a dedicated payments engineering team and a long horizon.
That depends on the connectors the platform has live in your markets. Typical coverage includes card schemes, digital wallets, bank transfers and local alternative payment methods. Ask for the list of connectors that carry live traffic today, and for the time and cost of building any that are missing.
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.