Thousands of Indian businesses resell bill payments, money transfer, verification and cash-out services, either through their own apps or through networks of shops. The ones that last do two things well: they choose a business model that fits their skills, and they know exactly what each regulated service lets them do. This guide covers both, then gives you a compliance checklist and a technical checklist to finish before your first customer.
Four ways to build a fintech reselling business
| Model | What you own | Your customers | What you need |
|---|---|---|---|
| API partner | Your app or portal, calling another platform's APIs | Businesses or users of your product | Developers, a server and business KYC |
| Distributor network | Relationships with the retailers you onboard | Shops using the platform's app | Field presence, training and support |
| White-label platform | A branded copy of a platform, with its source code | Your own retailers and distributors | Provider contracts and an operations team |
| Custom build | Software built to your specification | Whoever your product serves | A budget, clear requirements and provider contracts |
The models aren't exclusive. Many businesses start as distributors or API partners, learn the market, and move to a white-label platform once their volume justifies their own provider contracts.
What each regulated service allows
The software can look the same for every service. The rules are not the same.
Bharat Connect bill payments. Under RBI's BBPS Master Direction of 29 February 2024, customer operating units (COUs) are authorised by RBI and answer for the agent institutions they work with, which NBBL certifies. A reseller is normally an agent in that chain. Two consequences follow:
- Whether you may onboard sub-agents depends on your agreement, and some agreements don't allow it.
- The Direction treats a bill payment system run outside Bharat Connect by anyone other than a biller as a payment system that needs RBI authorisation, so don't build a side channel.
AePS. RBI's directions on due diligence of AePS touchpoint operators (RBI/2025-26/63), in force from 1 January 2026, put KYC of every touchpoint operator, including sub-agents, on the acquiring bank, with fresh KYC after three months of inactivity, according to a summary by Mondaq. If you build a network of AePS retailers, expect your bank or aggregator to ask for records on every one of them.
Money transfer. RBI's revised framework for domestic money transfer (RBI/2024-25/52, effective 1 November 2024) expects remitter registration and an additional factor of authentication on each transaction, and the bank remains the principal. A reseller can't take over the bank's KYC decisions.
Payouts and collections. RBI's Payment Aggregator Directions of 15 September 2025 regulate non-banks that handle funds for merchants. In our reading, collecting or pooling other businesses' money and paying it out is aggregation, while software that only instructs a bank on a business's own account is not.
Wallets. RBI's Master Direction on prepaid payment instruments of 27 August 2021 separates closed-system instruments, used only for the issuer's own goods and services, from instruments that can pay third parties. In our reading, a reseller wallet used to pay billers or support cash withdrawal needs careful design, so have it reviewed.
Verification. Bank account and document checks return personal data, which the Digital Personal Data Protection Act, 2023 governs. Run a check only with consent and for a clear purpose.
The readings above are general information, not legal advice. Have your model reviewed by a legal adviser before launch.
Commercial realities
- Prepaid balance. API transactions usually debit a prepaid wallet, so your working capital sets your daily volume.
- KYC and review first. Expect business KYC and a use-case review before you receive live keys.
- Margins vary. Charges and commission depend on the service and your volume, and they change. Never promise fixed income to the retailers or sub-partners you sign.
- Support is the real cost. Pending transactions, complaints and refunds reach you first, whatever your contract says about who resolves them.
Compliance checklist for resellers
Describe your role honestly
Don't call your business a bank, an operating unit or an agent institution, or claim approval by RBI or NPCI, unless it's true.
Know your customers
Verify the businesses and people you serve, and keep the records.
Record consent
Keep the consent and the purpose for every verification check.
Offer a grievance channel
Publish how customers can complain, and resolve complaints with your provider's status and complaint tools.
Respect sub-agent rights
Onboard sub-agents only where your agreements and the network's rules allow it.
Publish your terms
Terms of service, a privacy policy and a refund policy that match how your service actually works.
Technical checklist
- Keep API keys on your server only, never inside a mobile app, and rotate a key the moment it is exposed.
- Whitelist fixed server IPs, and keep server clocks synchronised, because signed requests carry a timestamp.
- Sign every request exactly as documented, over the exact body bytes you send.
- Use one idempotent reference per business transaction, and reuse it on every retry.
- Poll the status endpoints for pending transactions, with a sensible first wait and a backoff.
- Reconcile every day against the provider's records, and investigate every mismatch.
- Log requests and responses with secrets masked, and keep the logs for disputes.
Our guide to idempotency and reconciliation covers the engineering in depth.
What Payonclick India offers resellers today
| Offer | What it covers | Status |
|---|---|---|
| API partner account | BBPS bill payment in 30 categories, verification with 6 checks, and DMT to supported banks inside their service windows | Live |
| Distributor account | Retailers on the Payonclick app, through payonclick.in | Live |
| White-label platform | Your own branded platform with recharge, AEPS, Micro ATM, UPI cash withdrawal, money transfer and payout modules | Available |
| Custom software | Modules, integrations and products built to your specification | Scoped per project |
These aren't offered as partner APIs: operator recharge, AEPS, Micro ATM, UPI cash withdrawal, payouts, dynamic QR collection and CMS. There is no sandbox host, so API partners build against the read-only endpoints first and then run small real transactions.