Moneycontrol
HomeTechnologyLack of a transaction status check limiter resulted in incessant requests by banks, leading to UPI downtime
Trending Topics

Lack of a transaction status check limiter resulted in incessant requests by banks, leading to UPI downtime

According to an NPCI rule, the banks could check a transaction's success only thrice, and the requests need to be used only once with an interval of 90 seconds

April 16, 2025 / 15:26 IST
Story continues below Advertisement
NPCI did not have transaction status check limiter which brought down UPI

The National Payments Corporation of India did not have a transaction status check limiter in its technology architecture, which resulted in incessant API call requests by banks bringing down the UPI system on April 12, a couple of sources told Moneycontrol.

NPCI runs the country’s most popular digital payments platform, UPI. Application Programming Interface is a technology solution that helps two different institutions communicate.

Story continues below Advertisement

On April 15, Moneycontrol reported that NPCI, in its root cause analysis, found banks making non-stop transaction success checks continuously hitting the system beyond what was permitted, causing the platform to face downtime for around five hours, the longest in more than three years.

According to an NPCI rule, the banks could check a transaction's success only thrice, and this instruction was to be set up by the banks and not NPCI, said one of the sources. As per NPCI operating circulars, the "Check Transaction" API call needs to be used only once in the interval of 90 seconds.