Chapter 1 · Meaning and Scope of Fintech
What fintech actually is, the difference between fintech as a layer and fintech as a sector, three waves of fintech history and where India sits in them, the functional map of the industry — and the discipline this book will demand of you: classify a firm by its licence and its function, never by its app's look.
🎯 Learning Objectives
- Define fintech in one sentence and use the term precisely
- Distinguish fintech as a layer across the financial system from fintech as a sector of firms
- Tell the three waves of fintech history apart and place India's path within them
- Place any Indian fintech firm into its functional bucket — payments, lending, wealth, insurance or infrastructure
- Classify firms by licence and function, and explain why the licence decides what a firm may do
- State the organising idea of this book: India's fintech sector is public-infrastructure-led
1. What Is Fintech?
Fintech is short for financial technology. The one-line definition this book uses is simple:
Every word in that sentence carries weight. Technology means software, data and telecom — not just apps, but also the switches, databases and networks underneath them. Delivery means the service reaches the customer: the loan is disbursed, the premium is collected, the payment lands. Financial services names the industry being changed: payments, lending, savings, wealth management, insurance and the market infrastructure that connects them all.
Notice what the definition does not say. It does not say startups. It does not say mobile apps. It does not say crypto. A core-banking system built in the 1990s is fintech. A UPI app on a ₹8,000 phone is fintech. An algorithm that prices an insurance premium is fintech. The term covers the whole span, and that breadth is exactly why we will need a second distinction — layer versus sector — in the next section.
The word is also younger than the thing. Banks have used technology since the punched-card era, but "fintech" as a label spread only after the 2008 crisis, when startups began selling financial services directly to customers over the internet and smartphones. So when someone says "fintech", they may mean a seventy-year process or a fifteen-year industry. Both are correct. The trouble starts only when the two meanings are mixed in one sentence — which is what Section 2 fixes.
2. The Layer View and the Sector View
There are two honest ways to use the word fintech, and the whole course rests on keeping them apart.
2.1 Fintech as a layer
The layer view treats fintech as a capability that runs through the entire financial system. Every bank, every insurer, every fund and every market uses technology to deliver its service. From this angle, fintech is not an industry at all. It is a horizontal slice through every industry that deals in money.
The layer view answers questions like these. How fast is settlement? What does onboarding cost? Can a branch in a town of twenty thousand people offer the same products as a metro branch? When a ninety-year-old public-sector bank upgrades to a core-banking platform and launches a mobile app, the layer view is what you are watching. The bank is using fintech. It has not become a different kind of firm.
2.2 Fintech as a sector
The sector view counts firms. A fintech company is a firm whose business model is native-digital delivery of a financial service — the company exists because digital delivery makes its product possible, cheap or fast. Paytm, PhonePe, Razorpay, Zerodha, PolicyBazaar and CRED sit in this bucket. So do hundreds of smaller firms you will meet through this book.
The sector view is the one investors use, journalists use and — yes — this book mostly uses, because our task is to understand firms and business models. But the sector view has a trap attached, and we name it now so it never catches us: a firm is not a fintech because it calls itself one. A firm is a fintech-sector firm when digital delivery is the core of how it earns. We will classify firms the disciplined way instead — by function and licence, in Sections 4 and 5.
2.3 Why both views exist
Neither view is "right". They serve different users. A regulator thinks in layers: the technology runs through every firm it supervises, so the rules must work for all of them. An investor thinks in sectors: which firms are gaining share, at what unit economics, under which licence? A bank executive lives both at once — buying technology as a layer while competing against sector firms riding that same layer.
3. Three Waves — and Where India Fits
Fintech history is usually told in three waves. The boundaries are approximate, but the pattern is clear, and India's timing through the waves is unusual in a way that shapes everything else in this book.
3.1 First wave — automation and the back office (1950s–1990s)
The first wave put machines behind the counter. The ATM appeared in 1967. SWIFT gave banks a common messaging network for cross-border payments from 1973. Trading floors went electronic. In India, the Reserve Bank pushed bank computerisation through the 1980s and 1990s, and cheque clearing accelerated with magnetic media and MICR. Customers barely noticed most of it — the branch still looked the same — but each machine cut the cost and error rate of a manual process. This is the layer view in its purest form: technology inside institutions.
3.2 Second wave — the internet and the smartphone (post-2008)
The second wave put the branch into the customer's pocket. Two forces drove it. First, mass smartphones and app stores after 2007–2008. Second, the post-crisis regulatory climate: trust in banks fell, capital rules tightened, and supervisors in many countries chose to open the payments market to new entrants rather than wait for incumbents to innovate. Kenya's M-Pesa (2007) showed a phone could be a bank account. In India, Paytm (2010) built a wallet business on prepaid instruments, and the 2016 demonetisation — studied properly in Chapter 3 — shoved adoption forward overnight. The defining business model of this wave was the standalone app: one firm, one product line, digital first.
3.3 Third wave — shared infrastructure and embedded finance (2015– )
The third wave is the one India leads. Instead of every firm building its own rails, the state built shared digital public infrastructure: Aadhaar for identity, UPI for payments, the Account Aggregator for consent-based data sharing, OCEN and ULI for digital credit, ONDC for open commerce. Firms now assemble products on top of public rails, and finance travels inside non-financial apps — a merchant app offering loans, a ride-hailing app offering insurance. This is embedded finance, and it dissolves the boundary between "a finance app" and "an app that happens to include finance". Chapter 34 takes it up properly.
India's unusual position: it entered wave two late, compressed it, and then chose public rails for wave three while the United States stayed on private rails and China's private rails were pulled back under state control. That three-way contrast is Section 6.
4. The Functional Map
However you define fintech, the firms inside it sort cleanly into five functional buckets. This map is the first sorting tool for the whole course; we will use it in every chapter of Parts II, III and IV.
4.1 Payments
Moving value between people and firms. UPI apps, wallets, merchant QR codes, payment gateways, remittances. This is the bucket India did best: payments volume on UPI now dwarfs card systems, and the story of how — the architecture, the economics, the zero-fee debate — fills Part II of this book.
4.2 Lending and credit
Deciding who may borrow, at what price, and collecting repayments. Digital lending platforms, buy-now-pay-later, cash-flow underwriting against GST or UPI data. Lending is where the money is — literally — because credit carries a spread that payments no longer do. Part III covers the value chain and the RBI's (Digital Lending) Directions, 2025.
4.3 Wealth and markets
Helping people save and invest: discount brokers, mutual fund platforms, robo-advisory, gold apps. The puzzle here is the business model — when brokerage is zero, where does revenue come from? Chapter 21 answers it.
4.4 Insurance
Distributing and pricing insurance digitally: aggregators that compare policies, insurtechs that underwrite with new data, embedded insurance sold inside another app's checkout. Indian insurance penetration remains low, which is exactly why this bucket is watched closely.
4.5 Infrastructure and regtech
The firms that sell to other firms: payment switches, API platforms, KYC-on-demand, fraud scoring, compliance automation. This bucket is mostly invisible to customers and central to the industry — and it is where a large share of serious engineering happens.
5. Classifying Firms by Licence — A First Look
Function tells you what a firm does. Licence tells you what a firm may do. In Indian finance the second question decides the first: a firm's licence — banking registration, NBFC registration, PPI authorisation, PA authorisation, TPAP approval, AA licence, or LSP status under a regulated entity — sets the outer boundary of its business. Two rules follow, and they hold for the rest of this book.
Rule one: the licence names the accountability. If a lending app fronts customers for an NBFC, the app is a lending service provider, and the NBFC answers to the RBI for the app's conduct. Responsibility follows the licence, not the logo the customer sees.
Rule two: partnerships extend a licence, they do not create one. A distribution platform selling a partner bank's deposits is still not a bank. When you meet a firm in later chapters, your first question will always be: whose licence is this activity riding on?
The table below is the licence map in brief. Chapter 6 develops it in full, with the obligations attached to each licence; Chapter 7 adds the regulators. Treat this as your first pass.
6. The Indian Model: Public Rails, Private Apps
Every fintech story needs a setting. Here is this book's setting, stated in one idea:
Compare the three big models. In the United States, private rails came first: card networks and banks built the payment infrastructure, and fintech firms plugged into it. In China, private platforms — Alipay and WeChat Pay — built proprietary rails that scaled enormously, and the state then brought them under tighter control. In India, the state moved early and built the rails itself, through NPCI and the India Stack, then opened them to everyone on similar terms.
Why did India choose public rails? Three reasons recur through this book. Inclusion: private rails tend to serve customers who are already profitable; a public rail reaches a village shopkeeper at near-zero marginal cost. Cost: one shared UPI switch is cheaper for the system than a dozen proprietary ones. Competition: when the rail is public and neutral, a two-person startup can reach the same payment network as a trillion-dollar bank — competition happens at the app layer, not the access layer.
The model has a consequence that organises the rest of this course. Payments became a near-free public utility — UPI carries a zero merchant discount rate on most transactions, a decision we examine in Chapter 12. When the payment itself earns nothing, firms must earn somewhere else. So economic value migrated up the stack: into credit, wealth and insurance. That is why this book moves from infrastructure to payments, then to credit and wealth, and only then to digital money.
7. Boundaries: What Is Not Fintech
A definition is only useful if it excludes things. Here is what stays outside this book's use of the term, and why the boundary matters.
General business software is not fintech. Accounting packages, payroll systems and ERP software handle money information, but they do not deliver a financial service to a customer. A textile manufacturer's payroll system is business software. A bank's payroll for its own staff is not fintech either — the test is whether the technology delivers the financial service itself.
An incumbent's app is a channel, not a sector firm. When a traditional bank launches a mobile app, the bank is delivering its existing licensed business through a new channel. That matters for the layer/sector distinction, and it is why "every bank is a fintech now" is a sentence that sounds wise and explains nothing.
Big Tech in finance is fintech only where it delivers finance. A phone maker is not a fintech firm because its app store contains banking apps. When the same firm offers a wallet, a co-branded card or embedded credit at checkout, those specific activities are fintech — and are usually conducted under a licence or a licensed partner, which is exactly why we classify by licence and function rather than by company.
Crypto assets are inside the scope, under a distinct regime. Virtual digital asset platforms trade and hold crypto assets, which makes them part of the fintech universe — but India treats them under a specific tax regime (a flat 30 per cent on transfer income plus a 1 per cent deduction at source, with no loss set-off) and reporting obligations. Part IV gives them a full, unsentimental treatment.
Where this chapter ends
You now hold the course's first sorting tools: layer versus sector, three waves, five functions, and the licence-first discipline. The next chapter goes backwards before the story can go forwards — to India's financial system before fintech, and to the question that explains everything that follows: why did formal credit stay scarce for decades despite bank branches spreading everywhere?
🛠 Hands-On: The Taxonomy Mapping Exercise
This is the session's classroom activity, made self-paced. You will classify ten real Indian organisations across all three dimensions taught in this chapter: function (payments, lending, wealth, insurance, infrastructure), licence/regulatory position (whose licence does each activity ride on?), and layer (is the firm a native-digital sector firm, an infrastructure operator, or an incumbent using technology as a layer?). One of the ten is deliberately not like the others — finding it, and saying precisely why it differs, is the real test.
Steps
- Draw a table with four columns: Organisation, Function, Licence/Regulatory position, Sector or infrastructure?
- Classify each organisation below. Write your answer before checking the solution — a wrong guess you correct yourself is worth three right guesses you read.
- For any organisation you cannot place, write down exactly what you would need to look up, and where you would look (which regulator's register?).
- Find the odd one out, and state the reason in one sentence using a term defined in this chapter.
The ten organisations:
- PhonePe
- Zerodha
- PolicyBazaar
- Razorpay
- CRED
- BharatPe
- Groww
- CoinSwitch
- Paytm (the app, One97 Communications)
- NPCI
View Solution / Walkthrough
| Organisation | Function | Licence / position | Sector or infrastructure? |
|---|---|---|---|
| PhonePe | Payments (core), plus distribution | TPAP on UPI via sponsor PSP banks; insurance/broking arms hold separate licences | Sector firm |
| Zerodha | Wealth — broking | Stockbroker registered with SEBI | Sector firm |
| PolicyBazaar | Insurance — distribution | Insurance web aggregator under IRDAI oversight | Sector firm |
| Razorpay | Payments — merchant acquiring | RBI-authorised payment aggregator | Sector firm |
| CRED | Credit and payments | Distributes credit chiefly through partner banks/NBFCs (LSP-style); payments via bank rails | Sector firm |
| BharatPe | Merchant payments | Merchant QR/acquiring riding partner-bank rails; lending through an NBFC partner | Sector firm |
| Groww | Wealth — broking and funds | Stockbroker registered with SEBI; mutual fund distribution | Sector firm |
| CoinSwitch | Crypto/VDA platform | VDA reporting entity (FIU-IND); VDA tax regime applies | Sector firm |
| Paytm (One97) | Payments and distribution | TPAP plus distribution arms; its associate payments bank was barred by the RBI in early 2024 from accepting fresh deposits after 15 March 2024 | Sector firm |
| NPCI | Payments infrastructure | Umbrella organisation set up by banks under RBI encouragement; operates UPI, RuPay, IMPS | Shared infrastructure — not a fintech firm |
The odd one out is NPCI. It is the rail the other nine ride on, not a competitor on it — a not-for-profit umbrella organisation owned by member banks, not a firm whose business model is digital delivery of a financial service. Classifying it as a "fintech company" would blur the very distinction this chapter built: public rails, private apps.
Two footnotes earn you marks. First, Paytm's entry shows licence discipline in action: a payments bank licence was granted, then its usable scope was curtailed by supervisory action — proof that a licence is a living permission, not a historical fact. Second, CRED and BharatPe show that distribution-heavy credit models are classified through their partners' licences: the app is the front, the regulated entity is the accountability. Both ideas return in force in Chapters 6 and 16.
Key Takeaways
Fintech is technology applied to the delivery of financial services. Every financial firm uses it — that is the layer view.
The sector view counts firms whose business model is native-digital delivery. Classify them by licence and function, never by their app's look or their self-description.
India is public-infrastructure-led: the state built the shared rails, and private firms compete on top of them — the opposite of the US private-rail and Chinese platform-rail paths.
Zero-MDR UPI made payments a near-free utility, so value migrated up the stack — into credit, wealth and insurance. That migration is this book's route map.
The licence decides what a firm may do, and the regulated entity stays accountable for its partners. Ask always: whose licence is this activity riding on?
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 2.
1. Which sentence best describes fintech in one line?
2. The "layer" view of fintech means:
3. The "sector" view of fintech means:
4. A ninety-year-old public-sector bank upgrades to core banking and launches a mobile app. Under this chapter's distinction, it is:
5. The ATM, introduced from 1967, belongs to which stage of fintech history?
6. Which combination most sharply triggered the second wave of fintech after 2008?
7. India's third wave of fintech is best characterised by:
8. India's fintech sector is called "public-infrastructure-led" because:
9. In the United States, the retail payment rails were largely built by:
10. Which functional bucket does Zerodha belong to?
11. PolicyBazaar's core function and regulator are best described as:
12. Razorpay is best classified as:
13. Why did economic value migrate from payments to credit, wealth and insurance in India?
14. Which of these may a payments bank NOT do?
15. A third-party application provider (TPAP) in the UPI system:
16. An app fronts the customer journey for an NBFC's loans — sourcing, onboarding, repayment reminders. Under the 2025 Directions, the app is:
17. An Account Aggregator (NBFC-AA) may legitimately:
18. The difference between a payment aggregator (PA) and a plain payment gateway is:
19. Which item is OUTSIDE the scope of fintech as this chapter defines it?
20. The "everything is fintech" trap is a problem mainly because:
21. Crypto-asset trading platforms in India:
22. Which pairing is correct?
23. NPCI is best described as:
24. The India Stack's logical order, as this book uses it, is:
25. A super-app distributes loans, insurance and investments, all underwritten by licensed partners. The disciplined description is:
26. In China, the payment rails that scaled first were built by:
27. What best describes the difference between an incumbent's digital channel and a fintech-sector firm?
28. A firm's marketing calls itself "a fintech". This chapter's discipline for classifying it is to judge by:
29. This book treats digital currencies late in the sequence because:
30. Which sentence captures the Indian model in this book's one-line summary?