PhonePe

India trusts PhonePe with its money. That's not a small thing.

When you're moving real money not likes, not followers, not items in a shopping cart, the margin for error is zero. A bug in a fashion app means a wrong filter. A bug in a payments app means someone's salary doesn't land. Or a merchant doesn't get paid. Or a transaction gets stuck in limbo and a user loses trust in digital payments altogether.

PhonePe isn't just an app. It's infrastructure. It runs across Android, iOS, and Web. It operates across backend services, service layers, and client-side platforms simultaneously. It needs to work flawlessly in Prod, Stage, UAT, and Pre-Prod every environment, every time. And it ships fast, because in fintech, if you're not shipping, you're dying.

‍The problem? Bugs were leaking into Release Candidate builds. That means defects were surviving the entire testing pipeline and showing up right when the code was supposed to be locked for release. Timelines were already aggressive, and the team was under constant pressure to ship without breathing room to catch what was slipping through. On top of that, critical backend migrations needed to happen during off-hours we're talking late-night windows where one missed edge case could cascade into a production incident affecting millions of transactions.

PhonePe needed testers who wouldn't just run scripts and file tickets. They needed people who could think like the product was their own, who understood that a missed bug in a payments app isn't a JIRA ticket, it's someone's money.

We started where it mattered most: stopping the bleed. We brainstormed and ran root cause analysis on why bugs were leaking into RC builds, then systematically closed those gaps. This wasn't about adding more test cases, it was about understanding where the testing process was failing and fixing the process itself.

Our scope covered the full depth of PhonePe's stack. Functional testing, UI testing, UX testing, database testing, and API testing all running across Android, iOS, Web, backend, and service layers. We didn't just test surfaces. We tested the plumbing.

When PhonePe's Soundbox, their merchant-facing hardware device needed testing, our team became the critical resource for it. Firmware issues, OTA updates, signoff all handled. This wasn't standard mobile app testing territory. This was hardware meeting software, and we owned it.

The timelines were brutal, and we matched them. When a critical backend migration needed to happen between 10 PM and 1 AM to minimize impact on live users, our team was there not because they were asked to be heroes, but because that's what the release demanded. When a feature needed to be tested and signed off within the current sprint to avoid derailing the next one, we worked alongside dev to get it done. No drama, just delivery.

We worked with the development team as one unit not as an external vendor lobbing bug reports over the wall, but as embedded partners who understood the codebase, the release cadence, and the business consequences of letting something slip.

Somewhere behind that seamless experience is a team that tested at 1 AM during a migration window, that caught firmware bugs on a Soundbox before merchants ever saw them, that traced a bug leak back to its root cause and made sure it never happened again. That's the kind of testing that earns a testimonial from PhonePe's CTO — Rahul Chari — who said Moolya invested in their product as much as they did.