White-label payment infrastructure for acquiring banks
White-label payment gateway for low-risk PSPs
Built for high-risk PSPs — full control over your channels
A practitioner's guide to launching a payment service provider: choosing a model, signing an acquirer, licensing, PCI DSS, platform choice, costs, timelines and a 9-step launch plan.
White-label payment processing, also called white-label credit card processing, is a model in which a payment service provider, bank, ISO or platform sells online card acceptance to merchants under its own brand, while a technology partner runs the gateway, processing and security infrastructure behind it. Each payment travels from the reseller-branded checkout through the partner’s PCI DSS-certified platform to an acquiring bank, which sends it over card networks such as Visa and Mastercard to the cardholder’s issuing bank for approval and later settles the funds. The model suits companies that want to launch or scale a payment business without building and certifying their own processing technology.
“White label” means a product built once by one company and sold by many others under their own names. In payments, the product is the stack that lets a website accept cards: a hosted checkout, a payment API, a merchant back office, fraud and 3-D Secure tools, and connections to acquiring banks. The reseller puts its logo, domain and pricing on that stack and sells it to online merchants as its own service.
This guide is about accepting card payments online (card-not-present). Searches for “white-label credit cards” also return card issuing programs, where a company launches its own branded cards. That is a different business and is not covered here.
The three terms overlap, and vendors use them loosely. In practice:
| Term | What it usually covers |
|---|---|
| White-label payment gateway | The technical layer: checkout, API, tokenization, fraud screening and routing of transactions to acquirers. Read more on what a white-label payment gateway is. |
| White-label credit card processing | The gateway plus card-specific processing: authorization with Visa, Mastercard and other networks, clearing, settlement reporting and chargeback handling. |
| White-label payment processing | The broadest term: cards plus e-wallets, local payment methods and other alternatives, run under one brand. |
A white-label product is the same platform rebranded by many companies, with no exclusivity. A private-label product is customized and built for one company only (NMI). There is no single industry standard for “private-label payment processing”, so treat the terms as common usage rather than strict definitions.
Shared core platform, your branding on top. Faster and cheaper to launch, and you get the provider’s updates and new connectors automatically. Customization is limited to what the platform allows.
A version tailored exclusively to one company, often deployed on its own servers with custom features. More control and differentiation, but higher cost and longer delivery.
One more source of confusion: in the card business, “private label” also describes a store card that works only at one retailer. That meaning has nothing to do with processing.
Here is what happens when a shopper pays by card on a merchant’s website that uses a white-labeled gateway. Authorization takes a few seconds; the money moves later.
The shopper enters card details on a payment page or widget that shows the merchant’s and the reseller’s branding. The page is hosted by the technology partner, so card data never touches the merchant’s servers.
The gateway encrypts or tokenizes the card number, runs fraud rules and, where required, 3-D Secure authentication of the cardholder.
The gateway picks an acquiring connection (by rules such as currency, card type or cost) and sends the authorization request to that acquirer’s processor.
The acquirer passes the request to the card network (Visa, Mastercard and others), which routes it to the bank that issued the card.
The issuer checks funds, limits and its own risk signals, then returns a response. It travels back through the network, acquirer and gateway to the checkout, and the shopper sees the result.
Approved transactions are captured, usually when the order ships or right away for digital goods, and submitted in batches through the network for clearing.
The issuer pays the acquirer through the network minus interchange. The acquirer deducts scheme fees and its own margin, then pays the merchant, or the PayFac or PSP, which pays its sub-merchants net of its fees.
White labeling changes what the merchant and the shopper see, not how the card networks work. A typical split:
| Layer | Run by | Shows the brand of |
|---|---|---|
| Checkout page, widget, emails | Technology partner | Reseller (and merchant) |
| Merchant back office and reports | Technology partner | Reseller |
| API, documentation, domain | Technology partner | Reseller |
| Merchant contract and pricing | Reseller, ISO or PayFac | Reseller (acquirer may also sign, depending on model) |
| Acquiring and settlement | Acquirer or sponsor bank | Acquirer, behind the scenes |
| Card acceptance rules | Card networks | Visa, Mastercard and others |
The same white-label platform can sit inside very different business models. What changes is who signs the merchant, who receives the money and who carries the risk.
| Role | What it does |
|---|---|
| Merchant | Sells goods or services online and accepts cards. |
| Sub-merchant (sponsored merchant) | A merchant onboarded under a payment facilitator instead of holding its own merchant account with the acquirer. |
| ISO (independent sales organization) | Sells merchant accounts on behalf of an acquirer. The acquirer underwrites and contracts the merchant; the ISO earns residuals. |
| PayFac (payment facilitator) | Visa describes it as a third-party agent that can sign merchant agreements for an acquirer and receive settlement on behalf of sponsored merchants. Also called a master merchant or merchant aggregator (Visa). |
| PSP (payment service provider) | An umbrella term for a company that provides merchants with payment acceptance; it may act as a gateway, ISO, PayFac or a mix. |
| Acquirer | The licensed bank or institution that is a member of the card networks, settles funds to merchants and is responsible to the networks for them. |
| Sponsor bank | The acquirer in its role of sponsoring an ISO or PayFac into the card networks. Under Visa rules, the acquirer stays responsible for the PayFac and its sponsored merchants (Visa). |
| Processor | Runs the technical authorization and clearing messages for the acquirer. |
| Card network | Visa, Mastercard and others: set the rules and interchange, and route messages between acquirers and issuers. |
| Issuer | The cardholder’s bank: approves or declines payments and raises disputes. |
| Technology partner | The white-label provider that runs the gateway and processing platform under the reseller’s brand. |
These options are not exclusive: an ISO or a PayFac can run on a white-label platform. The table compares the typical starting positions.
| Criteria | White-label platform | ISO | PayFac | Build in-house |
|---|---|---|---|---|
| Who signs the merchant | You or your acquirer | Acquirer | You (as master merchant) | You or your acquirer |
| Who receives settlement | Depends on your license and acquirer agreement | Merchant, directly from acquirer | You, then you pay sub-merchants | Depends on your license |
| Typical pricing to merchants | Custom: your choice | Tiered or interchange-plus | Blended or flat rate | Custom |
| Risk you carry | Set by contract | Lower: acquirer underwrites | High: you underwrite and absorb losses | Set by contract |
| Technology you run | None: rented platform under your brand | Usually none | Onboarding, payouts, risk tooling | Everything, including PCI DSS certification |
| Time to market | Fastest | Fast | Slower: registration and sponsorship | Slowest |
Pricing patterns by model follow PayCompass. For the ISO route in detail, see how to become a credit card processor or ISO.
New PSPs enter the market without writing a gateway from scratch and spend their budget on sales and merchant acquisition. Established PSPs use a white-label platform to add acquirers, payment methods or regions faster.
Banks offer merchants a modern online checkout with Apple Pay, Google Pay, Samsung Pay and local methods, one-time and recurring payments, simpler merchant onboarding and transaction monitoring, without a multi-year IT project.
Sales organizations, marketplaces and SaaS platforms embed payments under their own brand to keep the merchant relationship and earn on every transaction instead of referring merchants elsewhere.
These verticals need several acquirers, smart routing to raise approval rates, strong fraud tools, automatic currency conversion and often crypto. See how this works for iGaming and Forex payment processing.
Every card payment carries three layers of cost: interchange paid to the issuer, scheme fees paid to the card network, and the markup of the acquirer and everyone between the acquirer and the merchant. Your revenue as a white-label reseller is the part of the markup you control.
Interchange depends on region, card type and channel. Some reference points from regulators and the networks:
| Model | How the merchant is charged | Good for | Watch out for |
|---|---|---|---|
| Interchange++ (IC++) | Actual interchange + actual scheme fees + your fixed markup (% and/or per transaction) | Larger merchants who want transparency | Statements are harder for small merchants to read |
| Blended (flat) | One rate for all cards, e.g. a single % + fixed fee | Small merchants and PayFac-style onboarding | You absorb the gap when expensive cards dominate |
| Tiered | Different rates for “qualified”, “mid-qualified” and “non-qualified” transactions | Traditional ISO portfolios | Opaque, which hurts merchant trust |
The buy rate is what you pay upstream (acquirer or processor) per transaction. The sell rate is what you charge the merchant. The difference is your spread. ISOs and agents receive it as a residual, a recurring share of the spread on every merchant they bring. Splits of 50/50 or 60/40 are commonly reported, but a split means little until you know the buy rate it is calculated on (American Banker, The Green Sheet).
Providers usually charge a setup or license fee plus a monthly or per-transaction platform fee. A SaaS deployment shifts hosting, updates and PCI DSS infrastructure to the provider. An on-premises installation means a larger upfront license, your own hosting and a wider compliance scope, in exchange for full control. For how these costs fit into a P&L, read about the payment gateway business model.
Under a white-label model, merchants sign up with you, so your onboarding process decides which risks enter your portfolio. A typical online-merchant lifecycle:
Company details, website, business model, expected volume and average ticket.
Verify the legal entity, directors and ultimate beneficial owners; screen them against sanctions and PEP lists.
Review the website (products, prices, terms, refund policy), the merchant category, processing history and past chargeback levels. Assign a risk tier, limits and, if needed, a rolling reserve or delayed settlement.
In an ISO setup the acquirer approves the merchant account; a PayFac registers the sub-merchant under its own account within the limits agreed with its sponsor.
The merchant connects via API, hosted page or a CMS plugin, tests in sandbox and starts processing, often with lower limits at first.
Transaction monitoring, periodic reviews and limit changes as the merchant’s volume and risk profile evolve.
When a cardholder disputes a payment, the issuer sends a chargeback through the network to the acquirer, which debits the merchant. If the merchant cannot pay (it closed, or ran out of money), the loss moves up the chain: to the PayFac or reseller that signed the merchant, and ultimately to the acquirer, which answers to the networks for everyone it sponsors (Visa). ISOs usually leave most losses with the acquirer, while a white-label PSP may take on part of the dispute risk depending on its contract (Chargeflow). Read that clause before you sign.
Visa and Mastercard run programs that flag merchants, and the acquirers behind them, when fraud or dispute ratios stay above set thresholds. Being flagged leads to fines, remediation plans and, in the worst case, termination. The thresholds have changed in recent years, so check the current network rules with your acquirer rather than relying on old figures.
A white-label provider certified at PCI DSS Level 1 stores, processes and transmits the card data, which removes most of the heavy compliance work from you and your merchants. It does not remove all of it. You remain responsible for your own systems and staff access to the back office, and each merchant still has to validate its own compliance. A hosted payment page or widget keeps card data off merchants’ servers and shrinks their scope.
For merchants, Visa sets four levels by annual Visa transaction count. Level 1 (over 6 million transactions a year) requires an annual Report on Compliance by a Qualified Security Assessor; smaller merchants usually complete a Self-Assessment Questionnaire (Otava).
It depends on your role and jurisdiction. If you only sell and support the service while the acquirer contracts and settles merchants directly, licensing requirements are lighter. If you receive and pay out merchant funds, you are likely to need a payment institution or e-money license, or equivalent, plus a sponsor agreement with an acquirer. Where the provider performs the regulated activity, a platform may not need a license of its own (Payrexx). Get local legal advice before choosing a model.
Renting the technology does not rent the regulatory status. Licensing, KYC and chargeback exposure follow the business model you choose, not the software you run.
| Benefits | Limitations |
|---|---|
| Fast market entry: weeks or months instead of years of development | Customization stops where the platform’s options end |
| Lower upfront cost: no gateway build, no own PCI DSS Level 1 infrastructure | Ongoing platform fees reduce your margin on every transaction |
| Your brand on checkout, back office and contracts | Dependence on the provider’s uptime, roadmap and support |
| Ready connectors to acquirers and payment methods | Switching providers later means migrating merchants and card tokens |
| Multi-currency and international payments from day one | Risk, KYC and licensing obligations remain yours |
Use these twelve checks when comparing providers. For a longer framework, see our guide to choosing a white-label payment platform.
Years in business, live clients and references you can call.
Ready connectors to the acquirers you need, and whether you can connect your own banks.
International cards, wallets such as Apple Pay and Google Pay, local methods and, if your verticals need it, crypto.
Checkout, back office, domain, emails and API docs: all of it under your brand, not just a logo swap.
Clear API documentation, mobile SDKs and pre-built modules for popular e-commerce platforms.
PCI DSS Level 1, encryption, tokenization, 3-D Secure and configurable anti-fraud rules.
Rules that send each payment to the best acquirer and retry soft declines elsewhere. Ask how routing rules are configured and who can change them.
KYC/KYB workflows, merchant limits, reserves and transaction monitoring in the back office.
SaaS or on-premises, who owns merchant data, and whether card tokens can be migrated if you leave.
Setup, license, monthly and per-transaction fees, plus the cost of new connectors.
Ask for an SLA in writing: 99.9% still allows about 8.8 hours of downtime a year, 99.99% about 53 minutes.
24/7 technical support, help with integration and testing, and training for your team.
The technical setup is the short part. Agreeing terms with acquirers, licensing and onboarding your first merchants usually take longer. For the full business plan, see how to start a payment processing company.
Choose ISO, PayFac or PSP, target verticals and regions, and confirm the licensing this requires.
Agree buy rates, risk appetite, reserves and settlement terms with one or more acquirers or a sponsor bank.
Sign the license agreement and share your business requirements so the platform can be configured for you.
A SaaS deployment can be ready in about a week; an on-premises installation takes around three months. You then receive back-office access to create users and manage operations.
Apply your brand to the checkout and back office, and run online training so sales, support and risk staff know the system.
Enable ready-made connectors, request new ones for unsupported acquirers, and validate the whole flow in a sandbox.
Run KYC and underwriting, add merchants and shops, switch to live mode and watch the first transactions closely.
Track approval, fraud and dispute rates; add tokenization, smart routing and recurring payments; connect acquirers in new regions as you grow.
eComCharge has built beGateway, a white-label payment gateway for PSPs, acquiring banks and payment businesses, since 2011. It is offered for white-labeled and private-labeled payment services.
White-label payment processing is a model in which a PSP, bank, ISO or platform sells online card acceptance under its own brand while a technology partner runs the gateway and processing infrastructure. Payments still pass through an acquiring bank and the card networks to the cardholder's issuing bank; merchants only see the reseller's brand on the checkout, back office and contract.
A white-label platform is one product rebranded by many companies, while a private-label platform is customized exclusively for one company. White label is faster and cheaper to launch; private label gives more control and differentiation at a higher cost. Usage of these terms varies across the industry.
A white-label processor is technology you rebrand, while ISO and PayFac are business models describing who signs merchants and who carries risk. An ISO sells merchant accounts that the acquirer underwrites and contracts. A PayFac signs sub-merchants itself and receives settlement on their behalf. Either can run on a white-label platform.
The merchant is liable first, then whoever signed the merchant, and ultimately the acquirer. If a merchant cannot cover a chargeback, the loss moves to the PayFac or reseller and then to the sponsoring acquirer. How much risk a white-label PSP carries is set by its contract with the acquirer, so check that clause before signing.
You earn the spread between your buy rate and the rate you charge merchants. For example, buying at IC++ + 0.15% + $0.05 and selling at IC++ + 0.45% + $0.10 leaves 0.30% + $0.05 per transaction before platform fees and losses. Agents and ISOs receive this as residuals, often split with the processor.
It depends on your role and jurisdiction. If the acquirer contracts and settles merchants directly, requirements are lighter. If you receive and pay out merchant funds, you will likely need a payment institution or e-money license, or equivalent, and a sponsor agreement with an acquirer. Get local legal advice.
Yes, you still have your own, smaller scope. The Level 1 provider covers storing, processing and transmitting card data, but you remain responsible for your own systems and back-office access, and each merchant must validate its own compliance. Hosted payment pages keep card data off merchant servers and reduce their scope.
The platform itself can be ready in about a week as SaaS or in around three months as an on-premises installation. Acquirer agreements, licensing and onboarding your first merchants usually take longer than the technical setup.
Start-ups, growing payment businesses, PSPs, acquiring banks, ISOs, platforms and high-risk verticals like iGaming and Forex benefit most. They save on development costs, launch faster and offer modern online payment methods to their merchants.
Check acquirer connectivity, payment methods, branding depth and security first. Then look at integration tools (API documentation, SDKs and CMS modules), routing, onboarding and risk tools, deployment options, transparent pricing, an uptime SLA and 24/7 support.
eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.
A practitioner's guide to launching a payment service provider: choosing a model, signing an acquirer, licensing, PCI DSS, platform choice, costs, timelines and a 9-step launch plan.
Learn the best practices to automate high-risk onboarding, reduce security risks, and ensure a smooth, compliant onboarding experience.
Discover how a multi-acquirer-protection-strategy enhances payment security, reduces fraud, and ensures seamless transactions for merchants.
Recover declined transactions cascading with expert tips to reduce payment failures and optimize your payment processing workflow
Unlock business growth with custom payment solutions tailored to your needs. Discover secure, flexible options for seamless transactions today.
Discover leading payment tokenization service providers. Compare features, benefits, and find the best solution for your business needs.
