India UPI nationwide payment outage
India's Unified Payments Interface, which handles the large majority of the country's retail digital payments, suffered a five-hour nationwide outage that dropped transaction success rates to as low as 50%, disrupting Google Pay, PhonePe, Paytm and major banks' own apps.
The damage was public. The root cause was preventable.
India's Unified Payments Interface, which handles the large majority of the country's retail digital payments, suffered a five-hour nationwide outage that dropped transaction success rates to as low as 50%, disrupting Google Pay, PhonePe, Paytm and major banks' own apps.
What the software actually got wrong
The National Payments Corporation of India found its system architecture lacked a limiter on how many times banks could re-check a transaction's status, and its own operating guidelines relied on banks to self-impose that limit rather than enforcing it centrally; a surge of repeated status-check requests from banks overwhelmed the shared infrastructure's capacity for everyone.
The National Payments Corporation of India found its system...
The National Payments Corporation of India found its system architecture lacked a limiter on how many times banks could re-check a transaction's status
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Its own operating guidelines relied on banks to self-impose...
its own operating guidelines relied on banks to self-impose that limit rather than enforcing it centrally
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
A surge of repeated status-check requests from banks overwhelmed...
a surge of repeated status-check requests from banks overwhelmed the shared infrastructure's capacity for everyone
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.