PRD Template | productgrowth.in

TL;DR / Quick Verdict

This Product Requirements Document (PRD) template is engineered for Indian product teams. It features a complete real-world example—integrating UPI Lite to reduce small-transaction failure rates. It includes sections for problem statements, metrics, user stories, scope boundary, technical specifications, and phased rollout plans.

How to use this template

Every section below is filled in with a real example: a fintech app adding UPI Lite support to reduce checkout friction on small transactions. Replace the example content with your feature. The structure, the questions asked in each section, and the success metrics format are what you keep. Delete any section that genuinely doesn't apply to your feature — don't fill it with filler.

Document Overview

Metadata

Feature name

UPI Lite Checkout Integration

Author

PM Name · Payments Team

Date created

10 Feb 2026

Last updated

18 Feb 2026

Target ship date

28 Mar 2026 (Q1 close)

Status

In Review

Reviewers

Engineering Lead · Design Lead · VP Product · Compliance

Related docs

RBI UPI Lite Circular (Sep 2024) · Payment Flow Figma · Q1 OKR Doc

Problem Statement

Why we're building this

The problem in one sentence

52% of our UPI transactions are under ₹200, but every one of them requires UPI PIN entry — adding 8–15 seconds of friction that is causing measurable drop-off on small purchases.

Evidence (data that proves the problem exists)

Checkout abandonment for transactions <₹200 is 18.3% vs 9.1% for transactions >₹500 (Mixpanel, Jan 2026)
Exit survey: "too many steps for small amount" cited by 34% of users who abandoned sub-₹200 checkouts
Session recording shows median time from payment screen to success is 22s for <₹200 vs 14s for larger amounts (longer PIN retries on mobile)
NPCI data: UPI Lite adoption at competitor apps (PhonePe, CRED) is now 30%+ of sub-₹200 transactions

Who is most affected

Daily active users making habitual small purchases (food delivery, transit top-ups, utility micro-payments). These are our highest-frequency users — 22% of our DAU but 61% of transaction volume by count.

Why now

RBI expanded UPI Lite transaction limit from ₹200 to ₹500 per transaction in Sep 2024, significantly increasing the addressable transaction pool. Three major competitors have already shipped this. Delay is costing us switching.

Goals & Success Metrics

How we'll know it worked

Primary success metric

Checkout completion rate for transactions ≤₹500 — from 81.7% to 88%+ within 60 days of full rollout

Sub-₹500 completion rate

81.7%

→ target

88%+

Median checkout time (small txn)

22 sec

→ target

<12 sec

UPI Lite adoption rate

→ target (D90)

35%+

Secondary metrics

UPI Lite wallet top-up rate (target: 60% of UPI Lite users top up in first week)
Wallet balance utilisation (% of loaded balance spent within 7 days — target: 75%+)
Failed transaction rate for Lite transactions (must stay <2%)
CS tickets related to UPI Lite confusion (target: <0.5% of Lite transactions)

Guardrail metrics (must not worsen)

Overall checkout success rate must not drop. UPI standard flow performance must not degrade. User trust scores (CSAT) must hold at ≥4.2/5.

Non-goals (what success is NOT)

This feature does not aim to increase average transaction value. We are not trying to shift large transactions to Lite (the ₹500 limit prevents this). We are not building a full wallet product — UPI Lite is specifically for the checkout flow.

User Stories

What users need to do

US-01 First-time UPI Lite setup P0

As a UPI-registered user who has never used UPI Lite,
I want to set up my UPI Lite wallet in <60 seconds when I'm at checkout,
so that I can pay for my ₹180 order without entering my PIN every time.

System detects transaction ≤₹500 and surfaces UPI Lite setup prompt
User can load ₹500–₹2000 into Lite wallet with a single UPI PIN entry
Wallet balance is visible on the payment screen
First Lite payment completes with zero additional authentication
User receives SMS + in-app confirmation showing Lite balance used and remaining

US-02 Returning UPI Lite user at checkout P0

As a user with an active UPI Lite wallet balance,
I want to pay for transactions under ₹500 without any PIN,
so that checkout is as fast as tapping a card.

Payment screen auto-selects UPI Lite when balance is sufficient and amount ≤₹500
Single tap "Pay ₹X" completes the transaction — no PIN, no OTP
Remaining Lite balance shown post-transaction
If Lite balance insufficient, system falls back to standard UPI with clear explanation

US-03 Lite wallet top-up P1

As a UPI Lite user whose wallet balance has dropped below ₹100,
I want to top up my wallet quickly from the app,
so that I'm not blocked from PIN-free payments when I need them.

Low balance notification triggers when Lite balance <₹100 (configurable by user)
Top-up flow accessible from payment screen and from profile/wallet section
Top-up requires one UPI PIN entry for the reload transaction
Maximum Lite balance of ₹2,000 enforced per RBI guidelines

US-04 Lite transaction history P2

As a UPI Lite user,
I want to see a clear history of my Lite transactions separately from my standard UPI history,
so that I can reconcile my spending and understand where my balance went.

Lite transaction history accessible from wallet section
Each entry shows: merchant, amount, date, time, Lite balance after transaction
Downloadable statement available (PDF, last 90 days)

Scope

In / Out

✓ In scope (V1)

UPI Lite wallet setup during checkout for new users
PIN-free payment for transactions ≤₹500 when Lite balance sufficient
Wallet balance display on payment screen
Low balance notification and in-flow top-up
Lite transaction history in wallet section
Graceful fallback to standard UPI when balance insufficient
Android + iOS native apps

✗ Out of scope (V1)

Web/PWA support (V2 backlog)
Lite-to-Lite P2P transfers (RBI restriction)
Auto top-up / standing instruction
Merchant-specific Lite cashback
International transactions (Lite is India-only)
Lite for transactions >₹500

Assumptions

PSP bank (Yes Bank) supports UPI Lite on-device APIs. User's linked bank supports Lite (all major Indian banks do as of Q4 2025). User's device is Android 6.0+ or iOS 14+.

Dependencies

NPCI UPI Lite SDK integration (Eng team — 2 weeks). PSP bank Lite API access (in progress, ETA 1 Mar). Compliance sign-off on Lite disclosure language (Compliance team — 1 week).

Design & UX Notes

For design team

Key UX principles for this feature

Zero surprise deductions — user must always know they're paying from Lite balance vs bank balance. Show balance prominently before any tap.
Educate at first use, not before — show Lite setup prompt at the moment of checkout friction (small transaction), not as onboarding content no one reads.
Fallback must be seamless — if Lite balance is insufficient, system silently degrades to standard UPI with a one-line explanation. No error state, no confusion.
Compliance language in plain Hindi/English — "This payment will use your UPI Lite wallet. No PIN needed." Not legalese.

Figma reference

figma.com/[link-to-be-added] — Payment screen V4, Lite setup flow, Lite history screens

Accessibility requirements

Lite balance indicator must meet WCAG 2.1 AA contrast. All new screens must support TalkBack (Android) and VoiceOver (iOS) for balance amounts.

Technical Notes

For engineering team

Architecture considerations

UPI Lite operates on-device — wallet state is stored in the secure element of the mobile device, not in our servers. Our backend only handles: (1) initiating the Lite setup request to NPCI via PSP bank, (2) recording Lite transaction metadata for display in history, (3) triggering low balance notifications via our existing push infrastructure.

API dependencies

POST /upi/lite/enable → Initiate Lite wallet creation POST /upi/lite/topup → Load balance (requires UPI PIN) GET /upi/lite/balance → Read current on-device balance POST /upi/lite/pay → Execute Lite payment (no PIN) GET /upi/lite/history → Fetch Lite transaction log

Edge cases to handle

Device change — user should be prompted to re-enable Lite on new device
App uninstall/reinstall — Lite wallet state must be recoverable via PSP bank lookup
Low balance + transaction amount exactly equal to balance — allow, show ₹0 balance after
Network failure during Lite payment — show pending state, do NOT retry automatically (avoid double debit)
RBI daily limit (₹1L total UPI) — Lite transactions count toward this; handle 40002 error code gracefully

Launch & Rollout Plan

Phased delivery

Phase	Audience	Success gate	ETA
Alpha	Internal team (50 users)	No critical bugs, Lite setup <60s	7 Mar
Beta	5% of Android users	Completion rate ≥85%, error rate <2%	14 Mar
50% rollout	50% Android + 10% iOS	Metrics trending toward targets	21 Mar
Full launch	100% Android + iOS	Primary metric hit or on track	28 Mar

Rollback trigger

Automatic rollback to 0% if: Lite transaction error rate exceeds 5% in any 2-hour window, or overall checkout success rate drops more than 2 percentage points from baseline.

Open Questions & Decisions

To be resolved

#	Question	Owner	Due
Q1	Should we show Lite setup as a full-screen modal or inline within the payment screen? (Inline preferred for lower drop-off but needs Design validation)	Design Lead	20 Feb
Q2	Default top-up amount: ₹500 or ₹1000? ₹1000 reduces re-load frequency but increases initial friction for first-time users	PM	22 Feb
Q3	Compliance: does the Lite disclosure language need RBI-mandated exact wording or can we use plain language? Checking with legal.	Compliance	25 Feb

The Daily Brief — a daily update across 12 industries

One actionable growth breakdown every morning, across 12 industries — with an audio version in 21 languages. No fluff, just hard product teardowns and India benchmarks.