fintech product management
In fintech, your most important stakeholder is not your user, your CEO, or your investor. It is the regulator. Every other industry lets you ship and iterate. Fintech lets you ship, get a show-cause notice, and then iterate — if you are lucky.
Fintech is the single largest hiring vertical for product managers in India right now. Razorpay, PhonePe, CRED, Paytm, Zerodha, Slice, Jupiter, Fi, Groww, BharatPe, Pine Labs — the list is long and growing. If you are a PM in India in 2025, there is a very high chance your next job is at a fintech company.
But here is what most PMs discover in their first month: fintech PM is a fundamentally different discipline. Not because the product thinking changes. Not because the frameworks are different. Because the regulatory environment imposes constraints that do not exist in any other vertical. In e-commerce, if your feature has a bug, users complain. In fintech, if your feature violates an RBI circular, you get a letter from a regulator with the power to shut down your business.
After working with fintech PMs across dozens of Pragmatic Leaders cohorts — from early-stage payments startups to public companies — I can tell you the single biggest mistake PMs make entering fintech: they treat regulation as a blocker to work around. The PMs who succeed treat regulation as the product constraint that shapes every decision.
RBI is not your enemy. RBI is your product requirement.
Every product has constraints. Consumer apps are constrained by attention spans. B2B SaaS is constrained by enterprise procurement cycles. Fintech is constrained by the Reserve Bank of India.
The difference: if you ignore attention span constraints, your product fails slowly. If you ignore RBI constraints, your product fails overnight.
RBI circulars are not guidelines. They are binding instructions with compliance timelines. When the RBI issued its directive on card-on-file tokenisation in 2022, every fintech company in India had to restructure how they stored card data. PMs who had been tracking RBI circulars saw it coming months in advance and had migration plans ready. PMs who ignored the regulatory channel scrambled to ship in weeks what should have taken months — and some companies had payment failures affecting millions of users.
The practical implication for your day-to-day: every feature you design must answer three questions before engineering begins.
- Does this feature touch regulated activity? Payments, lending, insurance, investment — all regulated. If yes, you need compliance sign-off before the PRD is finalised, not after.
- Which RBI circular governs this? There is always one. KYC norms, data localisation requirements, digital lending guidelines, prepaid payment instrument (PPI) limits, UPI transaction caps. Find the circular. Read it. Not the summary your compliance team wrote — the actual circular.
- What changes if the regulation changes? Build for the current rule. But architect for the next one. If your lending product hardcodes a specific interest rate cap, you will be rewriting code every time the RBI adjusts rates. If you parameterise it, you ship a config change instead of a release.
Wednesday morning. A payments startup in Bangalore. The PM has just received a forwarded email from the compliance team — a new RBI circular on digital lending published the previous evening.
PM: “Has everyone seen the new RBI circular on first loss default guarantee? It changes how we can structure our lending partnerships.”
Engineering Lead: “We are shipping the BNPL feature on Friday. Is this going to affect it?”
PM: “Yes. The circular says FLDG arrangements between fintechs and NBFCs are now capped at 5% of the loan portfolio. Our current model assumes 10%. We cannot launch as designed.”
Head of Partnerships: “I just closed the NBFC partnership last week. The terms assume the old structure.”
PM: “I know. Here is what we do: we pause the Friday launch, rework the risk model with the NBFC to comply with the 5% cap, and renegotiate the revenue share. I need compliance to confirm our reading of the circular by end of day. Engineering — no code changes yet, but freeze the branch.”
Engineering Lead: “How long is the delay?”
PM: “If compliance confirms today and the NBFC agrees to revised terms by Friday, we can ship next Wednesday. If the NBFC pushes back, it could be two to three weeks.”
The PM who reads RBI circulars on the day they are published saves their team from shipping features that get pulled. The PM who delegates regulatory awareness entirely to compliance discovers problems when it is too late to fix them cheaply.
In fintech, a circular published at 7pm can invalidate a feature shipping at 9am. The PM's job is to be the first person in product who knows.
The fintech PMs I respect most have RBI’s circular page bookmarked. They subscribe to NPCI updates. They read the Master Direction on Digital Lending not because they enjoy regulatory documents, but because those documents are the specification their product must conform to. In no other PM vertical does reading government publications count as product research. In fintech, it is the most important research you do.
The UPI ecosystem: infrastructure you build on, not a feature you add
UPI is not a payment method. It is India’s financial infrastructure. Understanding this distinction is the entry ticket to fintech PM in India.
When NPCI launched UPI in 2016, it created a platform — a shared payment rail that any licensed entity could build on. By 2025, UPI processes over 14 billion transactions per month. More than credit cards, debit cards, and net banking combined. Every fintech product in India either builds on UPI, integrates with UPI, or competes with something that runs on UPI.
For a PM, this means several things:
You do not control the rails. If you are building a payments product, UPI is the underlying infrastructure. NPCI sets the rules — transaction limits (currently ₹1 lakh for most categories, ₹5 lakh for specific ones like tax and education), settlement timelines, dispute resolution processes, and API specifications. You cannot negotiate these. You build within them.
The 30% market share cap changes strategy. In 2024, NPCI introduced a rule that no single UPI app can process more than 30% of total UPI transactions. This directly affected PhonePe and Google Pay, which were both above that threshold. As a PM at any UPI app, this cap means your growth strategy has a ceiling. You cannot just acquire users indefinitely — you need to either diversify into non-UPI products or accept that your UPI volume has a regulatory limit. This is a product strategy constraint that does not exist in any other market.
UPI Lite and UPI 123PAY expand the design space. UPI Lite allows small-value offline transactions without a PIN. UPI 123PAY enables feature phone users to access UPI. If you are building for mass-market India — Tier 3, Tier 4, rural — these are not niche features. They are your primary payment channels. A PM building a payments product for kirana stores in rural Maharashtra who ignores UPI 123PAY is building for metro India and calling it “India.”
Interchange economics are zero. Unlike card networks where merchants pay interchange fees, UPI is a zero-MDR (merchant discount rate) instrument for most categories. This means if your business model depends on transaction fees from UPI payments, you do not have a business model. PhonePe makes money from merchant lending, insurance distribution, and investments — not from UPI payments. Paytm monetises through its wallet, payment gateway for businesses, and financial services. CRED monetises through brand partnerships and credit card bill payments. The UPI payment itself is a distribution channel, not a revenue stream. As a PM, this shapes every monetisation decision you make.
Lending PM: where product meets credit risk
Lending is where fintech PM gets genuinely complex. You are not just building features — you are building features where a mistake costs real money. Not “users complain” money. “The company loses crores in bad loans” money.
The lending PM operates at the intersection of product, risk, and regulation. Here is how it breaks down:
Building FOR an NBFC vs building AS an NBFC. This is the first distinction every lending PM must understand. If your company is a lending marketplace (like Paisa Bazaar or BankBazaar), you connect borrowers to lenders. Your product problems are distribution, matching, and conversion. If your company is an NBFC or has an NBFC licence (like Slice, or Bajaj Finserv’s digital arm), you are the lender. Your product problems now include credit underwriting, collections, and capital adequacy. The PM’s scope — and liability — is dramatically different.
Credit risk is a product problem. When a lending product has high default rates, it is tempting to blame the data science team’s models. But the PM chose which users to target. The PM designed the application flow that determines what data gets collected. The PM set the loan amount limits. The PM decided whether to offer ₹5,000 or ₹50,000 as the first loan. Each of these decisions affects default rates. A PM who designs a frictionless loan application that approves everyone in thirty seconds will have spectacular conversion metrics and catastrophic default rates. The product constraint is not “make it easy to borrow.” It is “make it easy for the right people to borrow.”
Collections UX is PM territory. Nobody talks about this in PM interviews, but collections — what happens when a borrower does not repay — is one of the most sensitive product surfaces in lending. The RBI’s guidelines on digital lending explicitly address collection practices: no harassment, no calls outside 8am-7pm, no threats, no misrepresentation. The PM designs the reminder flow, the escalation sequence, the restructuring options. A badly designed collections UX creates regulatory risk, brand damage, and — after the RBI’s digital lending guidelines of 2022 — potential licence threats. The PMs I have seen get this right treat collections as a product surface with the same care they give to onboarding.
BNPL is not “just” lending. Buy Now Pay Later products sit in a regulatory grey zone that the RBI has been progressively tightening. In 2022, the RBI effectively required BNPL products to follow digital lending guidelines — meaning full disclosure of the lending partner, interest rates, and terms to the borrower at the point of transaction. If you are building a BNPL feature, you must design the checkout experience to include regulatory disclosures without destroying conversion. This is a genuine product design challenge: compliance says show a full-page disclosure. Growth says every additional screen drops conversion by 15%. The PM finds the architecture that satisfies both.
Payments PM: the details that separate good from broken
Payments PM looks simple from the outside. Money goes from A to B. How hard can it be? The answer: extremely, because the margin for error is zero and the edge cases are infinite.
Transaction success rate (TSR) is your primary metric. Not conversion rate. Not user growth. Transaction success rate. If a user tries to pay and the payment fails, that is not a UX inconvenience — it is a trust-destroying event. In India, where digital payments are still building trust with a massive population that remembers the demonetisation chaos, every failed transaction pushes a user back toward cash. The benchmark for top payments companies in India is 96-98% TSR. If your TSR is below 95%, you have a product emergency.
Settlement flows matter to merchants. A consumer pays via UPI. The money arrives in the merchant’s account… when? T+0? T+1? T+2? The settlement timeline determines the merchant’s cash flow, which determines whether they keep using your payment product. Razorpay’s competitive advantage was partly built on fast settlements — giving merchants access to funds faster than traditional banks. As a PM, understanding settlement flows, banking partnerships, and nodal account structures is not finance trivia. It is what determines whether merchants stay.
Chargebacks are a product problem. When a consumer disputes a transaction, the chargeback process begins. The PM designs the dispute interface, the evidence collection flow, the merchant notification, and the resolution timeline. Bad chargeback UX causes merchants to lose legitimate revenue and consumers to lose trust. The PM sits between the consumer’s expectation (“I want my money back now”), the merchant’s need (“prove the dispute is valid”), and the regulatory timeline (RBI mandates turnaround times for different dispute types).
Merchant onboarding is your growth lever. In a payment gateway like Razorpay or PayU, every merchant who onboards is a recurring revenue source. The onboarding flow includes KYC, bank account verification, website/app review, integration setup, and test transactions. The PM who reduces merchant onboarding from seven days to one day does not just improve a metric — they unlock an entirely different growth rate.
Insurance PM: distribution is the product
Insurance in India is one of the most under-penetrated financial products — life insurance penetration is around 3%, general insurance even lower. The opportunity is enormous. The product challenge is distribution.
Traditional insurance distribution runs through agents. An LIC agent visits your home, explains the policy, handles the paperwork. Digital insurance companies — GoDigit, Acko, Policybazaar — are rebuilding this distribution model. But the PM challenges are specific:
Regulatory product approval cycles are long. Unlike payments or lending where you build the product and get compliance sign-off, in insurance the product itself (the policy) needs IRDAI approval before you can sell it. Designing a new insurance product — say, a bite-sized travel insurance for a single flight — means filing with the regulator, waiting for approval (which can take months), and only then building the digital experience around it. The PM must plan roadmaps around regulatory approval timelines, not just engineering sprints.
The purchase decision is fundamentally different. Nobody wakes up excited to buy insurance. Insurance is a negative-emotion product — it forces you to think about illness, accidents, and death. The PM’s job is not to make insurance “fun.” It is to reduce the cognitive burden of a decision that users actively avoid. Acko’s approach — embedded insurance at the point of purchase (buy a phone, get screen insurance in one tap) — works because it removes the standalone decision. The user never has to think “I should buy insurance.” The insurance appears at the moment they are already spending money and thinking about protecting their purchase.
Claims experience determines retention. Insurance is the only product where the core value is experienced at the worst moment of the user’s life. They are sick, their car is damaged, their flight is cancelled. The claims UX is not a back-office process. It is the product experience that determines whether the user renews or tells ten people that digital insurance is a scam. GoDigit’s emphasis on fast claims processing — with a target of cashless settlements in hours rather than weeks — is not operational efficiency. It is their core product differentiation.
How fintech PM differs by career stage
If you are entering fintech PM (0-2 years): Your first job is to understand the regulatory landscape. Read the RBI’s Master Direction on Digital Lending. Read the NPCI’s UPI procedural guidelines. Read IRDAI’s guidelines if you are in insurance. This is not optional reading — it is the equivalent of understanding your product’s technical architecture. You also need to understand the financial mechanics: how money flows between accounts, what a nodal account is, how settlement works, what NACH and e-mandate mean. Ask your finance team to walk you through a single transaction end-to-end. Most junior fintech PMs cannot trace the money flow of their own product. Fix that.
If you are mid-level (3-5 years): You should be leading the compliance-product integration. Do not wait for compliance to flag issues. Be the PM who reads the RBI circular first and brings it to the team. Develop relationships with your company’s compliance and legal teams — they are your most important cross-functional partners, more important than design or data science in this vertical. Start understanding the business model deeply: unit economics of lending, interchange economics of payments, loss ratios in insurance. Product decisions in fintech have direct P&L impact in ways that most other verticals do not.
If you are senior (5+ years): Regulatory strategy becomes product strategy. You are not just complying with regulation — you are anticipating it. When the RBI signals interest in account aggregation (the Account Aggregator framework), the senior PM sees a new product surface before the regulation is finalised. When IRDAI discusses sandbox programmes for innovative insurance products, the senior PM is already designing experiments. At this level, you attend industry consultations, your company’s responses to regulatory discussion papers include your product perspective, and you shape the product roadmap around a regulatory forecast, not just the current rules.
Pick any fintech app on your phone — a payments app, a lending app, a neobank, an investment platform. Go through its core user flow as a new user and answer:
-
KYC flow: What documents does it ask for? At what point in the journey? Does it gate value behind KYC or let you explore first? Is the KYC level appropriate for the product type (minimum KYC for wallets up to ₹10,000, full KYC for higher limits)?
-
Disclosure compliance: If it is a lending product, does it clearly show the lending partner’s name (the NBFC or bank), the interest rate, the total repayment amount, and the terms — before you accept the loan? The RBI’s digital lending guidelines require this at the point of sanction.
-
Consent architecture: Does the app ask for explicit consent before accessing your data — bank statements, contacts, SMS? Post the 2022 digital lending guidelines, accessing SMS and contacts for credit assessment without explicit consent is non-compliant.
-
Grievance redressal: Can you find the grievance redressal officer’s details within 2 taps? RBI mandates this for all regulated entities.
-
Data storage: Does the app’s privacy policy state where data is stored? RBI’s data localisation directive requires payment data to be stored in India. Check if the policy mentions this.
Write down what you found. If you spot gaps, you have found the kind of compliance debt that fintech PMs must actively manage — because regulators find these gaps too.
You are the PM for PhonePe's UPI payments product. Engineering has built a feature that pre-fills the UPI PIN entry screen with a numeric keypad styled to match PhonePe's brand colours, reducing one tap in the payment flow. Your UX team's A/B test shows a 4% improvement in payment completion rate — significant at PhonePe's transaction volume. Your compliance team flags it: the RBI's UPI security guidelines require the PIN entry experience to be provided by the issuer bank's app, not your overlay. The feature is technically within a grey zone — there is no explicit prohibition, but the intent of the guideline is to keep PIN entry out of third-party control. The CEO sees the 4% lift and wants to ship.
The call: Do you ship the PIN keypad feature or pull it?
You are the PM for PhonePe's UPI payments product. Engineering has built a feature that pre-fills the UPI PIN entry screen with a numeric keypad styled to match PhonePe's brand colours, reducing one tap in the payment flow. Your UX team's A/B test shows a 4% improvement in payment completion rate — significant at PhonePe's transaction volume. Your compliance team flags it: the RBI's UPI security guidelines require the PIN entry experience to be provided by the issuer bank's app, not your overlay. The feature is technically within a grey zone — there is no explicit prohibition, but the intent of the guideline is to keep PIN entry out of third-party control. The CEO sees the 4% lift and wants to ship.
The call: Do you ship the PIN keypad feature or pull it?
You are the PM for a BNPL product at a Series C fintech in Mumbai. Your product lets users split purchases into 3 interest-free installments at checkout — integrated with 200+ e-commerce merchants. Last quarter, the product processed ₹400 crore in transactions. This morning, the RBI published new guidelines: all BNPL products must now display the lending partner's name, the effective APR (even if interest-free, the processing fee must be annualised), and a full repayment schedule — at the checkout screen, before the user confirms the purchase. Your merchants are furious. They say the disclosure box will kill conversion. Your compliance team says you have 90 days to comply.
Your conversion rate at checkout is 34%. Internal estimates suggest a full-screen disclosure before confirmation could drop it to 20-25%. The merchants' contracts have minimum volume commitments. What do you do?
your path
The fintech PM toolkit
Beyond standard PM skills, fintech PMs need specific knowledge that other verticals do not require:
| Skill | Why it matters in fintech | Where to learn it |
|---|---|---|
| Reading regulatory documents | RBI circulars are your product specifications | Start with RBI’s Master Direction on Digital Lending (2022) |
| Financial product mechanics | You cannot PM a lending product without understanding interest rates, EMIs, NPA classification | Your company’s finance/risk team — ask for a 101 session |
| Transaction flow mapping | Every payment has a flow: initiate → authenticate → authorise → settle. You must know each step. | Trace one transaction through your product’s backend logs |
| Fraud pattern recognition | Fraud is not just a risk team problem. Product design choices create or close fraud vectors. | Sit with your fraud/risk team for a week |
| Compliance-first PRD writing | Every PRD needs a regulatory impact section before the feature specification | Look at how Zerodha documents their product decisions publicly |
Where to go next
- Understand multi-persona products and enterprise dynamics: B2B Product Management
- Activation is the metric fintech PMs fight for hardest: Activation Optimization
- When your product has real-world consequences, ethics is not optional: Ethical PM
- Build the metrics foundation for fintech KPIs: Metrics and KPIs
- Fintech pricing is a product and regulatory decision: Pricing Strategy