— Consumer Payments
Dynamic QR
Customers hesitated to act on a payment request pushed to their phone by a collections agent, even a legitimate one. The fix wasn't better copy on the notification. As product owner, I worked with the Paytech and IT teams on a different format: agents generate a QR code, customers scan it on their own terms, using whatever UPI app they already trust. Volume grew steadily over the next 18 months, and on average about 77% of QRs generated ended in a successful payment, against about 18% of payment links.
₹2 Cr → ₹82 Cr
Dynamic QR monthly volume, over 18 months
— Platform
Data-Led Platform
Field agents were visiting customers with day-old data. They had no way to know if someone had paid another loan that morning, or abandoned a payment an hour before they knocked. We designed a config-driven data layer with the engineering team that pushes near-real-time signals into the app without a code release. What used to take a release cycle now takes a day.
1–2 months → 1–2 days
Time to ship a new insight to a field agent
— Consumer Payments · Platform
Category Landing Page
The consumer app had 18+ notification types, 14+ nudges, and 6+ pop-ups pushing delinquent customers toward payment. Self-serve rates were still low. We mapped the full lifecycle of the Bucket X customer base (EMI bounce to loan closure) and found the problem: every customer saw the same experience regardless of where they were in their loan journey. One landing page, built around that gap, was our answer.
1% → 100%
Staggered rollout across the customer app