NPCI Sets UPI API Limits After Repeated Outages
The National Payments Corporation of India (NPCI) has issued new guidelines for Unified Payments Interface (UPI) transactions in response to repeated outages and disruptions in the system. The new guidelines aim to improve the stability and security of UPI transactions, which have been plagued by frequent outages since March.
One of the key changes is the capping of balance check API calls at 50 per app per user per day. This means that users will not be able to check their balance more than 50 times per day using a particular app. This limit is intended to prevent excessive balance checks, which can cause delays and disruptions in the system.
Another significant change is the requirement for issuer banks to display the balance of the user’s account after every successful transaction. This will provide users with real-time information about their account balance, making it easier for them to track their transactions.
During peak UPI hours, non-user-initiated API calls will be restricted to prevent congestion in the system. This means that apps and payment service providers (PSPs) will not be able to initiate transactions during peak hours without user authentication.
PSPs will also be required to submit their API plans by August 31, ahead of a July 31 rollout. This will allow the NPCI to review and approve the plans, ensuring that they meet the new guidelines and requirements.
The new guidelines are intended to improve the overall stability and security of the UPI system, which has been plagued by frequent outages and disruptions. The NPCI has been working to address these issues, and the new guidelines are a major step in that direction.
The NPCI has also clarified that the new guidelines will not affect the overall functionality of UPI transactions, but will instead improve the user experience by providing more accurate and real-time information about their account balances.
The new guidelines are a welcome development for users of UPI transactions, who have been frustrated by the frequent outages and disruptions in the system. The NPCI’s efforts to improve the stability and security of the system will help to build trust and confidence among users, and will likely lead to increased adoption of UPI transactions.
The NPCI’s decision to cap balance check API calls and restrict non-user-initiated API calls during peak hours is a significant step in the right direction. By limiting the number of balance checks, the NPCI is reducing the load on the system and preventing congestion, which can cause delays and disruptions.
The requirement for issuer banks to display the balance of the user’s account after every successful transaction is also a major improvement. This will provide users with real-time information about their account balance, making it easier for them to track their transactions and avoid errors.
In conclusion, the NPCI’s new guidelines for UPI transactions are a major step forward in improving the stability and security of the system. The capping of balance check API calls, restriction of non-user-initiated API calls during peak hours, and requirement for issuer banks to display the balance of the user’s account after every successful transaction are all intended to improve the user experience and reduce the risk of outages and disruptions.
The NPCI’s efforts to improve the UPI system will help to build trust and confidence among users, and will likely lead to increased adoption of UPI transactions. As the NPCI continues to work to improve the system, it is likely that we will see even more improvements and innovations in the future.
