A foreign founder’s first Indian question is not “Which RBI licence do I buy?” It is “What does the Indian customer receive, and who is legally responsible for the money or credit?” The answer can differ sharply for SaaS, lending and payments.
Build the Indian structure around that answer. An incorporated subsidiary can sell software without being a lender, while a polished app cannot make an unregistered lender or payment operator lawful.
Quick Answer
Not every fintech company in India needs an RBI licence. Pure software supplied to authorised institutions may be different from lending, P2P facilitation, payment aggregation, PPI issuance or account aggregation. Foreign ownership adds FDI, FEMA, beneficial-ownership and reporting questions. Classify the exact activity, contracts and money flow before incorporating or seeking authorisation.
1. Begin with the customer promise
A lender provides credit, a P2P intermediary connects lenders and borrowers, a payment aggregator handles merchant collections and a gateway may only supply technology. The same app can contain several features. A label such as financial marketplace cannot determine the correct route.
Write down who signs with the end user, who chooses providers, where funds move and who bears loss. If offshore IP sits with one company and an Indian subsidiary sells the product, record which entity controls onboarding and customer decisions.
- Separate software supply from financial activity.
- Identify every bank, NBFC and payment partner.
- Record who receives funds or repayments.
2. Compare the common routes
Pure analytics or workflow SaaS may be a technology service, though outsourcing and data contracts still matter. Lending from an Indian balance sheet differs from serving a licensed lender. P2P and account aggregation have distinct NBFC registration frameworks and distinct limits.
Payment aggregation, gateway technology and prepaid wallets are not synonyms. Whether the business holds merchant funds or stored value changes the regulatory question. Cross-border payments add purpose-specific RBI and FEMA rules; a domestic integration cannot simply be copied.
- Build a route matrix for each revenue line.
- Check who is authorised in law and in the user interface.
- Classify future features before investor promises.
3. FDI is a parallel workstream
Even if no RBI licence is needed for software, foreign investment into the Indian company requires sector and entry-route checks. Financial services not specifically regulated, ownership from sensitive jurisdictions and control arrangements can change the analysis. Instrument choice, valuation and receipt of funds also matter.
Do not rely on a generic “100% FDI” sentence for a financial product. Draw the cap table through ultimate owners, plan the funding instrument and identify reports such as FC-GPR when Indian equity is issued to a non-resident.
- Check the current FDI policy and NDI rules.
- Prepare ownership and source-of-funds records.
- Align group agreements with regulated duties.
4. Put approvals in order
A usable sequence starts with activity classification, then entity and ownership design, product controls and licence planning. An application timeline is a dependency, not a launch date. A bank contract or pending application is not authority to conduct a regulated activity.
Budget for customer disclosure, cyber and privacy controls, regulated outsourcing, grievance handling and reports after launch. Nominate local decision-makers who can explain the same business model to banks, regulators, investors and auditors.
- Freeze the launch scope before choosing a route.
- Track phase-two features separately.
- Do not advertise unapproved regulated services.
How to record the decision
A short decision note should explain why the chosen route fits the facts, which authority controls the point, what was checked and which assumptions remain open. For fintech company in India, the note should also identify the responsible person, the next filing or approval event and the evidence that supports each conclusion.
Keep the note with board materials, agreements, portal acknowledgements and professional advice. This simple record helps founders answer investor, lender and regulator questions without reconstructing the reasoning months later. Update it whenever the business model, ownership, money flow, instrument terms or scheme status changes.
Documents to keep in one working file
The exact set depends on the transaction, but the working file should make the facts easy to test. Start with these records and add authority-specific forms or declarations where required:
- Map product features and every fund flow.
- Classify each feature against current RBI directions.
- Check FDI sector, route, control and ownership.
- Choose entity and funding instrument.
- Prepare applications and partner agreements.
Use dated versions and keep a clear approval trail. A missing email, valuation input or portal receipt can become a material due-diligence issue even when the commercial decision itself was sound.
Decision table
Use the facts of the proposed transaction to test each row before choosing a route.
| Activity | Question to settle |
|---|---|
| SaaS to a licensed institution | Is the company truly a vendor? |
| Loans or P2P matching | Which lending or P2P framework applies? |
| Merchant collections | Is PA authorisation required? |
| Wallet or consent-data sharing | Do PPI or NBFC-AA directions apply? |
Practical checklist
Work through these steps using dated documents, not assumptions made in a pitch deck.
- Map product features and every fund flow.
- Classify each feature against current RBI directions.
- Check FDI sector, route, control and ownership.
- Choose entity and funding instrument.
- Prepare applications and partner agreements.
- Calendar FEMA and post-launch reporting.
Mistakes that create avoidable delay
The following shortcuts frequently create avoidable legal or filing work later.
- Assuming a software label removes regulated activity.
- Using a partner’s approval to market the startup as licensed.
- Taking foreign investment before checking its route.
When professional review is useful
A fact-specific review should test the chosen route, evidence and filing sequence before money or customer commitments make a correction expensive.
For a fact-specific review, share the proposed activity, ownership, funding instrument and present stage with Sunny G And Co. at contact@cssunnygupta.com. The scope and professional fee should be agreed only after the facts and required filings are clear.
Related service paths
If the issue involves actual filings or structuring, these service pages describe the relevant scope of work. They do not change the eligibility and approval tests explained above; the right route still depends on the company’s documents and intended activity.
Official sources and last review
This article was last reviewed on 15 September 2026. Rules, portal status and filing practices can change, so check the current authority before acting.
