Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

HDFC Bank

PayZapp's UPI merchant payment success rate fell from 97% to 91% in two weeks. How would you find the root cause?

Prepared by NextSprints

14 mins
Report an error
Root Cause Analysis Data Analysis Payments Knowledge Fintech Payments Banking Payments Upi Root-Cause-Analysis Payzapp
Product Management Root Cause Analysis Question: PayZapp UPI merchant payment success rate drop

Introduction

PayZapp is HDFC Bank's payments app, built with Zeta, that combines UPI, a wallet, bill payments, brand vouchers and the Pixel credit cards. The prompt says: PayZapp's UPI payment success rate for scan-and-pay merchant transactions dropped from about 97% to 91% over the last two weeks, while peer-to-peer UPI looks normal. How would you investigate? A six-point fall in success rate is severe. In UPI, every failed payment at a shop counter is a moment of embarrassment for the user, and many will simply switch to PhonePe or Google Pay on the spot. I'll approach this systematically: clarify, rule out external factors, understand the journey, break down the metric, gather data, form hypotheses, find the root cause, validate, and decide on a fix.

Framework overview

Clarify, rule out external causes, map the journey, decompose the metric, gather data, form hypotheses, find the root cause, validate, decide and resolve.

Step 1

Clarifying Questions (3 minutes)

  • How exactly is "success rate" defined: successful transactions over initiated, or over submitted after PIN entry?

Why it matters: A drop before PIN entry points to app or QR parsing issues; after PIN entry it points to bank, NPCI or merchant-side failures. Expected answer: Successful / transactions submitted after UPI PIN entry. Impact on approach: We focus on failures after the user authorises payment.

  • Is the drop across all funding sources: HDFC savings accounts, other bank accounts linked on PayZapp, and RuPay credit cards on UPI?

Why it matters: Isolates whether the issuer side is the problem. Expected answer: The drop is concentrated in payments made from RuPay credit cards on UPI and from some non-HDFC bank accounts. Impact on approach: Points us towards credit-on-UPI and remitter-bank paths.

  • Did we ship any app release or backend change in the last three weeks?

Why it matters: Internal changes are the most common cause. Expected answer: A new app version with a redesigned scan-and-pay screen rolled out to 50% of Android users 16 days ago. Impact on approach: We compare by app version.

  • Are other UPI apps seeing a similar drop, based on NPCI dashboards or industry chatter?

Why it matters: An ecosystem-wide issue would change our response. Expected answer: No widespread outage reported. Impact on approach: The issue is likely specific to PayZapp.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Oct 31, 2026