Part I — Foundations & Digital Public Infrastructure

Chapter 6 · The Licence Map: Who May Do What

Chapter 1 taught you the discipline: classify a firm by its licence and its function, never by its app's look. This chapter is that discipline made concrete — every licence on the Indian fintech map, what each permits and forbids, the caps and obligations attached, the registers where permissions are verified, and the sixty-second drill that classifies any firm you will ever meet in this book.

📖 Chapter 6 of 35 ⏱ ~65 min read 🎓 Session 6 · CILO 1 Core 55% Stable 45% Volatile 0% 📝 Quiz · 30 MCQs

🎯 Learning Objectives

1. Why Finance Runs on Permission

Most industries work the other way: you may do anything the law does not forbid. Finance reverses the default. You may do only what your licence permits. The reason is asymmetry: a firm that takes money from the public can fail in ways that hurt people who never chose it — which is why deposit-taking, payment settlement and credit intermediation all sit behind explicit permissions, each with its own regulator, capital requirements and conduct obligations.

Two ideas organise everything that follows. Activity-based classification: the question is what the firm does — holds funds? settles merchant money? underwrites credit? — not what it calls itself. Entity-based permission: each activity then maps to a licence held by a specific entity, and that entity carries the accountability. A payments app is not a licence; somewhere behind it is a PSP bank, and perhaps a PPI issuer, and each answered a regulator for the right to exist.

The cost of getting this wrong is not theoretical. Taking deposits without a licence is a criminal offence, and the Banning of Unregulated Deposit Schemes Act, 2019 exists precisely for the schemes that did. Running payment aggregation without authorisation invites RBI enforcement. And the sharpest recent lesson — a payments bank barred in 2024 from accepting fresh deposits after persistent non-compliance — shows that a licence is a living permission, revocable in substance even when it survives on paper.

Here is the whole map at a glance. The rest of the chapter walks it row by row, and the data file behind this table is the same one Chapter 1 previewed.

📋 Stable content — Reviewed: October 2026 · Next review: April 2027

2. Deposit-Takers: Banks, Payments Banks, Small Finance Banks

The Banking Regulation Act, 1949 defines banking around one activity: accepting deposits withdrawable by cheque — demand deposits. That definition creates the sector's deepest boundary. Only a licensed bank may do it, and the licence is the hardest to obtain in Indian finance.

Commercial banks hold the full permission set: demand and time deposits, lending of every kind, payment-system participation as settlement banks, foreign exchange. In stack terms from Chapter 5, they are the entities whose rails the apps ride on. Within the category sit the public-sector banks of Chapter 2's story, the private banks of the 1990s wave, foreign banks, and the newer differentiated licences below.

Payments banks (licensed from 2015, on the 2013 framework) are narrow banks by design: payments and remittances, not credit. They accept small deposits — capped at ₹2 lakh per customer since 2021 — and may distribute mutual funds and insurance, but may not lend or issue credit cards. The design logic: keep the deposit franchise small, keep risk-taking out, and let the entity specialise in moving money. The 2024 experience of a large payments bank losing its deposit-taking substance is the category's cautionary tale — narrow does not mean unsupervised.

Small finance banks hold full banking powers under a mandate: inclusion is the licence's purpose, not its marketing. Two requirements bite: a priority-sector lending target of 75 per cent of adjusted net bank credit (against 40 per cent for ordinary banks), and at least half the loan book in tickets of ₹25 lakh or below. Many began life as microfinance institutions; the licence converted lenders to the poor into deposit-taking banks.

📝
Why the caps matter: a cap is regulation of business-model risk, not bureaucracy. The payments-bank deposit cap bounds how much public money rides on a narrow institution; the SFB lending floors stop an inclusion licence from drifting upmarket to corporate borrowers. When you see a cap, ask what failure it bounds.
📋 Stable content — Reviewed: October 2026 · Next review: April 2027

3. The Non-Bank Lending Universe

NBFCs — non-banking finance companies — do most of India's non-farm lending outside banks. Registered with the RBI but not licensed under the Banking Regulation Act, they may lend and invest, but they may not accept demand deposits (only a small, specially permitted category takes any deposits at all, and those are term deposits). Their funding comes from banks, markets and equity — which is why NBFC health is a standing concern of Chapter 16's value chain: when funding freezes, digital lending freezes with it.

Since October 2022, NBFCs are regulated under scale-based regulation: four layers — base, middle, upper and top — with obligations that tighten as size and systemic weight rise. A base-layer NBFC faces light-touch rules; the upper layer — the large, systemically important names — faces bank-like governance and capital discipline. The principle is proportionality: regulation should track the blast radius.

Two specialised members matter for this book. NBFC-P2P platforms (under the 2017 directions) match willing lenders with willing borrowers online — but the platform itself neither lends nor guarantees returns; it is a matchmaker with a licence, not a bank in disguise. And the LSP — lending service provider — from the RBI (Digital Lending) Directions, 2025: the app or agent that fronts the customer journey (sourcing, onboarding, servicing, recovery assistance) for a regulated entity. The LSP construct's whole point is accountability: the regulated entity answers to the RBI for everything its LSP does. Chapter 17 turns that clause inside out.

🌎
Real World: When a lending app's name is on the screen but an NBFC's name is on the sanction letter, the customer sees the app and the regulator sees the NBFC. Both readings are correct — and the second one is why conduct enforcement reaches the app through its regulated partner. There is no "just an app" defence in Indian digital lending.
📋 Stable content — Reviewed: October 2026 · Next review: April 2027

4. Payments-Side Licences: PPIs, TPAPs, Aggregators

4.1 PPI issuers — the wallet licence

A prepaid payment instrument is stored value: money loaded into a wallet or prepaid card, spent without a bank account in the loop. PPI issuers are authorised by the RBI (banks, and NBFCs meeting the criteria). The caps do the risk management: a small, minimum-details PPI (opened on OTP verification) is capped at ₹10,000; a full-KYC PPI may hold up to ₹2 lakh and is interoperable — including through UPI, which is how full-KYC wallets ride the public rail. Wallets faded as a default after UPI's rise; the licence still underlies closed-loop instruments, gift cards and corporate disbursement products.

4.2 TPAPs — the app approval

A third-party application provider is a UPI app approved by NPCI, riding on one or more sponsor PSP banks. The TPAP builds the experience; the PSP bank connects to the switch and touches settlement. Two boundaries define the licence. The TPAP never holds customer funds — money moves from account to account over bank rails. And since January 2021, NPCI's market-share cap limits any single TPAP to 30 per cent of total UPI transaction volume — a competition rule, not a safety rule. The two dominant apps ran far above it, and enforcement dates were deferred repeatedly; Chapter 11 treats that fight in full, because it is the clearest collision between the public-rail model and platform-scale economics.

4.3 Payment aggregators versus payment gateways

The line is funds. A payment aggregator (PA) handles e-commerce merchants' money: customer payments land with the PA, which pools them in escrow with a scheduled bank and settles to merchants on prescribed timelines. Non-bank PAs need explicit RBI authorisation — a gate many large gateways have had to queue behind. A pure payment gateway (PG) sells routing software and never touches merchant funds; it needs no PA licence for that reason alone. The moment a gateway touches funds, it is a PA in law regardless of its label — the cleanest example on the whole map of activity-based classification.

⚠
Warning: "We are only a technology platform" is the most common defence in payments enforcement — and it fails exactly when funds flow through the firm's accounts. Courts and the RBI both look at the money trail, not the website copy. Classify by the flow of funds, always.

5. The Data-Side Licence: Account Aggregators

The newest permission on the map rounds it out. An Account Aggregator holds the NBFC-AA licence from the RBI — a licence to be a pipe, nothing else. Chapter 5 built the framework: FIPs provide data, FIUs use it, and the AA carries it on a machine-readable, revocable consent. The licence's obligations are the pipe's walls: no storing data after delivery, no using it, no lending against it, no selling it. If a firm holds your financial history beyond the transaction it was consented for, it is not behaving like an AA — whatever it calls itself.

Why license the pipe at all? Because data about money carries the same asymmetry as money itself. The consent artefact only protects the customer if the carrier is supervised, capital-backed and forbidden from monetising what passes through. A licence turns a privacy promise into an enforceable duty — the same move this whole map makes, layer by layer.

6. Reading the Map Like a Practitioner

6.1 The registers

Chapter 1 promised the walkthrough; here it is. Permissions are public, and verification is free. The RBI website publishes the list of authorised payment aggregators, the list of authorised PPI issuers, and a searchable register of NBFCs by registration number. NPCI publishes the TPAP list with each app's sponsor PSP banks, and the banks live on UPI. SEBI's register lists every stockbroker and intermediary; IRDAI's lists insurance companies, brokers and web aggregators. Five minutes on a register settles what an hour of marketing cannot: does the permission exist, and who holds it?

6.2 The sixty-second drill

For any fintech product, ask in order:

  1. Name the activity. Holding balances? Moving money? Settling merchant funds? Underwriting credit? Matching lenders to borrowers? Carrying data?
  2. Name the licence. Map the activity to a row of this chapter's table. If the activity spans rows, the product rides multiple licences — name each.
  3. Check the register. Who is the licensed entity behind the logo, and does the register confirm it?

Three traps fail the drill most often. The app trap: assuming the brand on the screen is the licence holder — it usually is not; the licence sits with a partner bank or NBFC. The partnership trap: treating a partnership as permission — distribution rights come from the partner's licence and end where its obligations begin. The label trap: accepting a firm's self-description ("aggregator", "platform", "marketplace") — the funds flow decides, as the PA/PG line shows.

6.3 A map that moves

Finally, remember that the map is not stone. Payments banks have seen their effective permissions curtailed; the PA authorisation gate reshaped the gateway industry; new licences keep arriving as activity shifts — and every Deep-dive chapter from here on adds obligations to these rows. That is why this chapter's discipline is a method, not a memorised list: activity, licence, register. The method survives every revision of the map.

One question the map raises and cannot answer: who decides? Every licence above traces to a regulator — RBI here, but SEBI, IRDAI, PFRDA, IFSCA, NPCI and MeitY elsewhere — and the boundaries between them are where fintech's hardest jurisdiction fights happen. That is Chapter 7.

🛠 Hands-On: The Licence Sorting Challenge

This is the session's classroom activity, made self-paced. Ten situations follow — some legal, some questionable, one criminal. For each, name the licence required (if any), the regulator or authority, and the register you would check. Write your answers before opening the solution.

Steps

  1. An app holds customers' prepaid balances of up to ₹2 lakh (after full KYC) for online purchases. Licence? Register?
  2. An e-commerce marketplace collects payments on behalf of its sellers, pools them, and settles them weekly. Licence? Where do the pooled funds sit?
  3. A platform matches retail lenders with borrowers, takes a fee per match, and never lends its own money. Licence category, and what is it forbidden from doing?
  4. A UPI third-party app processes 40 per cent of all UPI volume. What rule does this engage, and what does Chapter 11 add?
  5. A company accepts deposits repayable on demand and issues cheque books. Licence category, and what defines the boundary activity?
  6. A software firm routes payments for merchants; funds move directly from customer banks to merchant banks. Does it need a PA licence? Why?
  7. A service pulls a borrower's bank statements, with consent, and delivers them to a lender's underwriting system. Licence, and its three walls?
  8. An NBFC's loans are sourced entirely through a co-branded app owned by a media company. Whose licence covers the journey, and who answers the RBI for the app's conduct?
  9. A lender must keep 75 per cent priority-sector lending and half its book under ₹25 lakh tickets. Which licence imposes this?
  10. A firm advertises "14 per cent assured returns on flexible deposits" and holds no registration of any kind. Legal status, and which statute applies?
  11. Drill: Pick any real fintech app on your phone and run the sixty-second drill — activity, licence, register. Write the three-line answer.
View Solution / Walkthrough
#Licence / statusAuthorityRegister to check
1PPI issuer — full-KYC wallet (₹2 lakh cap, ₹10,000 small PPI)RBIRBI list of authorised PPI issuers
2Payment aggregator — funds in escrow with a scheduled bank; weekly settlement needs checking against prescribed timelinesRBIRBI list of authorised PAs
3NBFC-P2P — matching only; forbidden from lending its own money, credit-enhancing or assuring returnsRBIRBI NBFC register (P2P category)
4TPAP over the 30 per cent volume cap (effective January 2021) — a competition rule; enforcement deferrals are Ch 11's storyNPCINPCI TPAP list with sponsor PSP banks
5Banking licence — accepting demand deposits withdrawable by cheque defines bankingRBIRBI list of scheduled banks
6No PA licence needed — pure gateway; funds never touch the firm. Touch funds and it becomes a PA in law—n/a (but confirm no funds flow in its accounts)
7NBFC-AA — the pipe; walls: no storing after delivery, no use, no lendingRBIRBI register of NBFC-AAs
8The NBFC's licence; the media company is an LSP — the regulated entity answers for the app's conduct under the 2025 DirectionsRBINBFC register; the app's disclosure of its RE partner
9Small finance bank licence — 75% PSL, 50% of book ≤ ₹25 lakhRBIRBI list of SFBs
10Unauthorised deposit-taking — criminal offence under the BUDS Act, 2019State / central enforcementNo register will show it — the absence is the finding

The drill. Strong answers follow the order exactly: activity first (what the firm does with funds and data), licence second (the row it maps to), register third (the primary source, not the app store page). If your phone's fintech app resolved to more than one licence — most do — you did it right: products assemble permissions, and the discipline is naming every one.

Key Takeaways

1

Finance reverses the default: you may do only what your licence permits — and the funds flow decides the licence, never the label.

2

Only banks take demand deposits. Payments banks (₹2 lakh cap, no lending) and SFBs (75% PSL, small tickets) are deliberate variations on the theme.

3

NBFCs lend without the deposit franchise, under scale-based layers since October 2022; LSPs act for them, and the regulated entity answers for everything the LSP does.

4

Payments-side permissions split by funds: PPIs hold value, TPAPs ride PSP-bank rails under the 30 per cent cap, PAs touch merchant money, gateways touch only software.

5

Verify from the registers — RBI, NPCI, SEBI, IRDAI — using the sixty-second drill: activity, licence, register. The method outlives every revision of the map.

Test Your Understanding

Choose one best answer per question. Select Check Answers to score yourself. An explanation appears after each question once checked. Aim for 24/30 before moving to Chapter 7.

1. The activity that only a licensed bank may perform is:

2. A payments bank may hold up to how much per customer?

3. Which activity is a payments bank NOT permitted?

4. The small finance bank mandate requires:

5. An NBFC, however large, may not:

6. Under scale-based regulation, NBFCs are sorted into:

7. A licensed P2P lending platform, by design:

8. Under the Digital Lending Directions, 2025, when an app fronts a lender's customer journey:

9. The balance cap on a full-KYC prepaid payment instrument is:

10. A wallet opened with only OTP-based minimum details is capped at:

11. Prepaid payment instruments are authorised by:

12. A UPI third-party application provider is approved by:

13. The TPAP market-share cap, effective January 2021, limits any single app to:

14. Which of these is a TPAP expressly not allowed to do?

15. What legally separates a payment aggregator from a payment gateway?

16. For a non-bank firm to aggregate e-commerce payments, it needs:

17. The Account Aggregator licence is:

18. Which behaviour would violate the AA licence?

19. To verify whether a firm is an authorised payment aggregator, you would check:

20. The register listing UPI third-party apps and their sponsor banks is published by:

21. An app holds customers' prepaid balances (up to ₹2 lakh, full KYC) for online purchases. It is a:

22. A marketplace collects sellers' payments, pools them, and settles weekly. The licence engaged is:

23. A platform matches retail lenders with borrowers for a fee, never lending its own money. Its correct classification is:

24. A firm with no registration advertises 14 per cent assured returns on flexible deposits. Its legal status:

25. A software firm routes payments so funds move directly between customer and merchant banks. It needs:

26. A distribution platform sells a partner bank's deposits under its own brand. The correct reading:

27. The 2024 experience of a large payments bank demonstrates that:

28. The sixty-second classification drill runs in which order?

29. This chapter's one-line summary of what a licence does:

30. The question this map raises but cannot answer — answered next in Chapter 7 — is: