Licensing and Access

Two routes to permission

Hold a licence yourself. Slow, capital-intensive, and you own the customer and the book.

Partner with someone who holds one. Fast, cheaper, and you operate inside their regulatory perimeter and their risk appetite.

Almost every Indian fintech starts with the second and moves toward the first once revenue supports the capital and compliance burden. That is a legitimate and well-trodden path ’ provided you understand that the rules still apply to you through the partner.

What each licence costs and takes — India

Net Owned Funds is the capital that must genuinely be there, from promoter equity rather than borrowed funds, at the time of application.

Timelines are typically three to six months for NBFC registration and four to six months for a payment aggregator authorisation, assuming complete documentation. Expect clarification queries; they are normal and they extend the clock.

The costs beyond capital

For a payment aggregator, direct licensing costs beyond the net worth requirement — infrastructure, certification, advisory and audits — have been put in the range of ₹1 crore to ₹3 crore, taking total investment to roughly ₹16–18 crore. Over sixty entities held in-principle or final PA authorisation as of 2026.

That capital requirement is doing deliberate work: it separates serious entrants from speculative ones, which is the regulator’s stated intent.

Eligibility details that cause rejections

Applications fail on the same points repeatedly.

• Main object clause. The Memorandum of Association must state financial services — lending, investment — as the main object. Applications listing financial activity as ancillary get rejected.
• Director experience. At least a third of directors should have ten or more years in banking or financial services.
• Source of capital. NOF must be genuine promoter equity, not borrowed. The source of funds is scrutinised specifically for money laundering risk.
• Director credit history. Clean records required. A director with an adverse bureau record is a problem discovered late.
• Business plan coherence. The model is reviewed on substance, not just form.

Applying

Applications are submitted through RBI’s online portal, and the accepted channel has changed — there is no walk-in or email route. Confirm the current portal and form before preparing anything, since sources differ and the wrong channel wastes weeks.

Scale Based Regulation

NBFCs sit in one of four layers — Base, Middle, Upper or Top — with obligations increasing as you move up. The layer follows asset size, activity and systemic importance.

The practical planning point: obligations that feel distant at launch arrive with growth. Governance, disclosure and capital expectations tighten as you cross thresholds, and a firm that built for the Base layer discovers Middle layer requirements at an inconvenient moment.

Design the audit trail and the governance programme for the layer above the one you are entering.

Data you cannot buy directly

This is the point that most reshapes a product plan, and it recurs across every module.

Almost everything a fintech needs is indirect. That is not an obstacle to route around — it is the structure of the market, and knowing the indirect route is frequently the difference between a product being buildable and not.

Choosing your route honestly

What changes once you hold a licence

Founders consistently underestimate the operating burden that arrives with permission.

• Named officers with personal statutory responsibility — Principal Officer and Designated Director under PMLA (Module 04), and they must be different people
• Regulatory reporting on defined cycles, with penalties counted per day of delay
• Board-approved policies that must exist, be followed, and be evidenced
• Inspection readiness — not a project, a standing state
• Grievance machinery with published officers and defined timelines (Module 06)
• Model governance under the MRM expectations (Module 09)
• Prior approval for changes in shareholding or control — under the Account Aggregator Directions 2025 read with the shareholding directions, a change in control needs RBI’s prior written approval before it takes effect

A prompt for mapping your permission path

You are an Indian financial services regulatory adviser who has
taken fintechs through licensing and partnership structures.

My situation:
- What the product does: [describe, including whether money or
  customer financial data passes through my systems]
- Who the customer is: [retail / MSME / enterprise]
- Capital available: [amount]
- Target launch: [date]
- Team's regulatory experience: [describe honestly]

Give me:

1. Whether I need a licence, can partner, or am out of scope -
   with the specific reasoning and the activity that triggers it.
2. If a licence: which one, the NOF requirement, the realistic
   timeline, and the costs beyond capital.
3. If partnering: what the partner will and will not let me do,
   and which digital lending constraints apply to my design.
4. Every data source I need, marked direct or indirect, and the
   specific route for each indirect one.
5. Which of those conversations must start in week one.
6. What the operating burden looks like the day after I am licensed.
7. The structural feature of my product most likely to be
   impermissible, so I can test it before building.

Be specific about current requirements and flag clearly where I must
take formal legal advice rather than rely on this.

Sources

Every figure, rule and date on this page, and where to check it. Entries are typed so you can see which are primary-sourced and which are industry reporting.