White label vs third party checkout: what each model means
A payment aggregator, as most Indian buyers use the term, onboards you as a sub-merchant, collects money from your users through its own checkout and settles funds to your bank account. You integrate its API, your users meet its name or interface somewhere in the flow, and its dashboard, risk rules and settlement schedule apply to you. It is a packaged service: the aggregator holds the relationships with banks and you use its access.
A white label gateway turns that arrangement around. The payment technology, meaning pay-in and payout APIs, the hosted payment page, the merchant panel and the operations behind them, runs under your brand on your domain, while funds move through merchant accounts that you hold or arrange. With Centabal Pay you bring the accounts and we set up and operate the channel: UPI pay-in, IMPS and NEFT payouts, a branded cashier page and a multi-tenant panel for your own merchants.
Side-by-side comparison on the criteria buyers weigh
The differences become clearer when both options are placed against the questions a payments team actually has to answer before signing. The list below compares a direct aggregator integration with a white label channel run on your own accounts. Neither column is better in every row; the point is to see which trade-offs matter for your platform.
- Branding: an aggregator shows its own checkout or name at some step; a white label channel shows your brand and domain on the payment page, while what appears on a user's bank statement depends on the underlying merchant account.
- Account ownership: with an aggregator you are a sub-merchant on its account; with white label you keep the merchant accounts and their commercial terms.
- Pay-in and payout: aggregators often treat collections and disbursements as separate products; a white label channel can bring UPI pay-in and IMPS or NEFT payout into one API and one panel.
- Setup effort: aggregator onboarding is mostly paperwork plus a standard integration; white label adds decisions about domain, accounts, routing and tenant structure.
- Control: aggregators expose the configuration options they choose to offer; white label lets you decide which accounts are used, how flows are routed and how reporting is structured.
- Dependency: a single aggregator is a single point of failure for your cash flow; a white label channel can spread traffic across several accounts you hold.
- Maintenance: the aggregator maintains its platform for everyone; with white label the provider operates the technology for you, but you own more of the decisions.
- Resale: aggregators are built for end merchants; a multi-tenant panel is built for serving many merchants with separated data and balances.
Cost drivers and time to launch
An aggregator usually charges per transaction, sometimes with additional fees for payouts, settlement speed or specific methods. Upfront technical cost is low, and if onboarding is approved you can go live with a standard integration. The trade-off is that cost scales directly with volume and the pricing structure is the aggregator's, not yours.
A white label channel has a different cost shape. What you pay depends on the scope of setup, the number of payment methods and countries, how many tenants the reseller panel must support and the level of operations coverage, plus whatever fees apply to the merchant accounts you negotiate yourself. We do not publish fixed prices or delivery times because they depend on these factors and on how ready your accounts and documentation are.
For context, building the same capability in-house means hiring for payment engineering, integrating each bank or provider, and staffing around-the-clock monitoring. That is the path many teams leave when payment work starts slowing product releases.
Own branded gateway vs aggregator: control and user experience
When a user on your app taps deposit and lands on a page with an unfamiliar name, some will hesitate, abandon or raise a support ticket asking whether the payment is genuine. An own branded gateway keeps the payment page on your domain with your look and wording, so the journey from your app to the UPI request and back feels like one product. For a consumer platform with a large user base in India, that consistency also reduces confusion when users later receive payouts.
Control goes beyond the visuals. With a white label channel you decide which merchant accounts carry which traffic, how to react when one account has issues, what payout rules apply, and how transaction data is reported to your finance team. With an aggregator, you work within the switches it provides and wait on its roadmap for anything else.
The honest trade-off: more control means more decisions and more responsibility. Someone on your side needs to own account relationships, reconciliation and the commercial terms with each provider.
Risk, compliance and who is responsible
In India, payment aggregators are regulated by the Reserve Bank of India and need authorization to handle funds on behalf of merchants. When you use a licensed aggregator, much of that regulatory weight sits with the aggregator, although you still carry your own obligations as a merchant. Pakistan, Bangladesh, Vietnam, the Philippines and Myanmar each have their own central bank rules, and those differ from India's.
Centabal Pay builds, integrates and operates payment technology. Licensing, approvals, the terms of your merchant accounts, user verification, tax and any other regulatory obligations remain with you. If your model involves reselling payment services to other merchants, confirm with qualified legal advisers in each country whether that activity requires authorization before you choose a structure. A white label channel is not a way around these requirements, and we do not set it up as one.
Operational risk also differs. A single aggregator account can be restricted, which pauses collections. Spreading volume across several accounts reduces that concentration, but every account still follows its provider's risk rules.
Payment aggregator alternative India: when each option fits
Most teams searching for a payment aggregator alternative in India are not unhappy with aggregators as such. They have outgrown one specific limitation, usually branding, control over payouts or the need to serve several merchants. The lists below set out typical situations for each choice.
- An aggregator fits when you do not hold and cannot obtain your own merchant accounts.
- An aggregator fits when volume is still modest and simplicity matters more than control.
- An aggregator fits when a third party name at checkout is acceptable to your users.
- An aggregator fits when you need only collections and have no regular payouts to users.
- A white label channel fits when you already have or can arrange merchant accounts and want to keep them.
- A white label channel fits when your brand must appear from deposit to withdrawal on your own domain.
- A white label channel fits when you need UPI pay-in and IMPS or NEFT payouts handled in one place.
- A white label channel fits when you resell payment services and need clean separation between merchants.
- A white label channel fits when in-house payment development is slowing your product team.
For payment resellers and regional expansion
Payment resellers face a problem that direct aggregator integrations do not solve: each new merchant needs its own credentials, balances, reporting and limits, and none of them should see the others' data. A multi-tenant reseller panel provides that structure, so adding a merchant becomes configuration rather than a new build. The commercial relationship with each merchant, and responsibility for vetting them, stays with you.
For teams expanding from one market into India, Pakistan, Bangladesh, Vietnam, the Philippines or Myanmar, the hard part is usually local: securing accounts, approvals and the payment methods users in that country expect. In a white label model you handle those local arrangements, and we run the technical channel on top of them, so you are not rebuilding the payment layer each time you enter a new country. Which methods are available in each market depends on the accounts you secure there.
A simple recommendation rule and how to start
The rule we suggest is straightforward. If you have no merchant accounts and no strong need for your own brand at checkout, start with an aggregator and revisit later. If you hold or can obtain accounts, need your brand throughout, want collections and payouts in one channel, or serve multiple merchants, a white label gateway is worth evaluating seriously. Many businesses begin with an aggregator and move to white label once volume, brand or resale needs justify it.
If you are considering the switch, a short conversation is the quickest way to test fit. Message us on Telegram at @zfxt5 with the points below and we will tell you what a setup would involve and what it depends on.
- Countries and payment methods you need for pay-in and payout
- Merchant accounts you already hold and those you are arranging
- Rough volume ranges and the split between deposits and withdrawals
- The domain and brand the payment page should run under
- Whether you serve one platform or several merchants as a reseller
- Who on your side will handle integration and reconciliation