How the payment reseller business model works
A payment reseller sits between online merchants and the underlying payment infrastructure. Your merchants want to accept deposits and send withdrawals to their users. The money moves through merchant accounts held with banks or licensed payment companies, and a technology layer connects everything: APIs, a payment page, a dashboard, routing and reconciliation. As a reseller you package these pieces into a service that each merchant can use under clear terms.
In practice there are four roles. The merchant serves end users. The account holder, often the reseller or the merchant itself, holds the merchant accounts. A regulated bank or payment institution actually settles funds. A technology provider runs the gateway software. Your business model depends on which of these roles you take on and which you contract out.
- Revenue usually comes from a margin on transaction fees for pay-ins and payouts, sometimes combined with setup or monthly platform fees; the right mix depends on your merchants' volumes and your own costs.
- Your main costs are account and processing fees charged by your banking partners, the technology layer, operations staff and support.
- Your main value to merchants is fast onboarding, reliable collections and payouts, and a single point of contact when something goes wrong.
Decide your position before you build anything
Before you think about software, write down who you serve and what you sell. A reseller focused on consumer apps in India that need UPI collections and instant payouts has very different needs from one serving merchants across several Asian countries. Your choice of markets determines which payment methods you need, which account partners you approach and which regulatory questions you must answer.
Also decide whether you offer pay-in only, payout only or both. Many digital businesses need both directions, because they take deposits from users and later return winnings, refunds, earnings or balances. Offering both in one channel makes reconciliation easier for your merchants, but it also means you must handle payout failures, bank holidays and beneficiary errors, not just incoming payments.
- Target merchants: industry, typical ticket size, expected volume pattern
- Markets: India first, or India plus Pakistan, Bangladesh, Vietnam, the Philippines or Myanmar
- Flows: pay-in, payout or both
- Brand: will merchants see your brand, their own brand, or both
- Support model: who answers merchants, and how fast
How to become a payment gateway reseller, step by step
The order matters. Resellers who sign merchants before their accounts and technology are ready often lose them during a delayed launch. The steps below follow the sequence most resellers can work through without blocking themselves.
- Define your merchant segment, markets and the flows you will offer.
- Take legal and compliance advice for each market on what activity you may perform and which licences or partner arrangements apply.
- Secure merchant accounts or partner arrangements with banks or licensed payment companies that support the methods you need, such as UPI for collections and IMPS or NEFT for payouts in India.
- Choose your technology approach: build in-house, or use a white-label gateway that runs under your brand and domain.
- Set up your tenant structure so each merchant has separated credentials, balances, reports and settings.
- Agree your pricing, settlement terms and merchant onboarding checks.
- Run test transactions end to end, including failed payments, reversals and payout rejections.
- Onboard a first merchant with limited volume, watch operations closely, then scale.
Payment gateway reseller India: methods, accounts and regulation
In India, most consumer collections today run over UPI, which lets users pay from their banking app using a VPA or QR code. For sending money back, IMPS offers near-instant bank transfers around the clock, while NEFT runs in batches and suits payouts where speed matters less. A reseller serving Indian merchants typically needs both: a UPI pay-in flow and an IMPS or NEFT payout flow.
Regulation is the part you cannot outsource to a technology vendor. Businesses that handle merchant funds in India generally fall under the Reserve Bank of India's framework for payment aggregators, and arrangements with partner banks carry their own compliance requirements. The same is true in Pakistan, Bangladesh, Vietnam, the Philippines and Myanmar, each under its own regulator and rules.
Centabal Pay builds, integrates and operates the payment technology; licensing, regulatory obligations, merchant due diligence and the commercial relationship with account providers remain with you as the client. Get qualified local advice before you take on merchants in any market.
Choosing the technology: build in-house or white-label
Building your own gateway means designing APIs, a hosted payment page, a merchant dashboard, routing to multiple accounts, callbacks, reconciliation, payout queues, monitoring and security. It gives full control but takes engineering capacity and ongoing maintenance, and every new payment method or account partner adds more integration work.
A white-label gateway gives you this layer already running, under your brand and on your own domain. You keep the merchant accounts and relationships; the provider runs the software and operations. For a reseller, the critical feature is multi-tenancy: each merchant gets its own credentials, balances, transaction history and reports, while you see and manage all of them from one panel.
Whichever route you choose, check that merchants never see a third-party brand at checkout, that pay-in and payout share one ledger, and that you can add accounts or merchants without code changes.
- Deposit and withdrawal APIs with clear documentation and callbacks
- Branded payment page on your domain
- Multi-tenant reseller panel with per-merchant separation
- Routing across several merchant accounts
- Reconciliation and settlement reports
- Round-the-clock monitoring and operations support
Running operations after your first merchant goes live
Launch is where the real work starts. Payments fail for many reasons: a user abandons the UPI request, a bank is slow to confirm, a beneficiary account number is wrong, or a partner account reaches a limit. Merchants will judge you on how quickly these cases are spotted, explained and resolved, not on how the system behaves on a good day.
Plan for monitoring at all hours, because users in India and the other markets pay and withdraw in the evening and at weekends. Decide who reconciles transactions against bank statements, how you handle pending and disputed transactions, and how merchants reach you. Many resellers in this region coordinate with merchants and their provider through Telegram groups, which makes fast escalation possible when everyone agrees on the process.
- Daily reconciliation of pay-ins and payouts per merchant
- Clear rules for pending, failed and reversed transactions
- Escalation path to account providers
- Alerts for unusual success rates or account limits
- Regular statements and settlement reports to each merchant
Launch checklist for a new payment reseller
Use this list before onboarding paying merchants. If any item is unclear, resolve it first; fixing it with live volume is far more expensive.
- Legal advice obtained for each market you serve
- Merchant accounts or partner arrangements active and tested
- Payment methods confirmed: UPI pay-in, IMPS or NEFT payout, and local methods for other markets
- Domain, branding and payment page configured
- Tenant set up for each merchant with separate credentials
- Pricing, settlement cycle and reserve terms written into merchant agreements
- Merchant onboarding and due diligence process documented
- End-to-end tests passed, including failures and reversals
- Operations rota and escalation contacts agreed
- Reporting and reconciliation templates ready
Mistakes to avoid when you start a payment gateway reseller business
Most problems for new resellers come from sequencing and assumptions rather than technology. The patterns below are common across India and the other markets in this region.
- Signing merchants before accounts and technology are tested end to end
- Relying on a single merchant account with no fallback when limits or reviews hit
- Treating regulation as the technology provider's responsibility
- Mixing merchants in one balance or report instead of separating tenants
- Ignoring payouts during planning and discovering failure handling only after launch
- Promising merchants fixed success rates or settlement times you do not control
- Running operations only during office hours when users transact late and at weekends