Latest news with #ApplicationProgrammingInterface
Time of India
5 days ago
- Business
- Time of India
Faster UPI transaction now as NPCI cut UPI Application Programming Interface response time, know how it will impact users
Academy Empower your mind, elevate your skills What did NPCI say about UPI APIs? Serial number UPI API Entities Existing response time Revised response time 1. Request Pay, Response Pay (Debit and Credit) Remitter Bank and Beneficiary Bank 30 seconds 15 seconds 2. Check transaction status Remitter Bank and Beneficiary bank 30 seconds 10 seconds 3. Transaction reversal (debit and credit) Remitter Bank and Beneficiary Bank 30 seconds 10 seconds 4. Validate Address (Pay, Collect) Payer PSP, Payee PSP, Beneficiary Bank (Account+IFSC based transactions) 15 seconds 10 seconds What does this mean? Will a faster response time of UPI APIs result in higher cost? Consumers can now experience faster UPI transactions, especially when making merchant payments. This is because the National Payments Corporation of India (NPCI) has gone for a significant update in the UPI server's software. These changes that are made in the Unified Payment Interface (UPI) server's software have become effective from June 16, 2025, will enable faster response simple terms, merchant's bank account which accepts UPI payments from a customer needs to communicate with the customer's bank account through a server to execute various tasks such as validate the transaction, know its status, reverse any failed transactions, etc. This communication bridge between two banks is done by the UPI APIs for UPI the UPI API (Application Programming Interface) which makes this communication bridge between the merchant's bank terminal and your UPI enabled bank account takes anywhere between 15 to 30 seconds to respond to the request. This is where NPCI has made the current changes. NPCI has cut the response time this API request to anywhere between 10 to 15 seconds i.e. up to 66% reduction in time if we take the maximum reduction from 30 seconds to 10 to this move by the NPCI, consumers making UPI payments can expect a faster transaction time and faster reversal of failed UPI transactions. Read below to know more about which particular consumer UPI transactions will get faster now due to this UPI API level a circular dated April 26, 2025, NPCI said:With the objective of streamlining the performance of UPI, it is hereby informed that the response time for UPI APIs initiated by NPCI is revised as follows:Source: NPCI circularNPCI said in the circular: 'The aforementioned revisions are intended to improve the customer experience. The members are required to ensure that they make the necessary changes in their system so that responses are handled within the revised time. If the members have any dependency/configuration changes at partner/ merchant's end, then the same also has to be taken care accordingly. Further, Members are requested to ensure that the changes to the response time should not adversely impact the technical decline (TD) thresholds.'Rahul Jain - CFO, NTT DATA Payment Services India explains what happens in the scenario where you scan a merchant QR code to pay them.'The cycle works like this for a consumer scanning a merchant QR code and paying: first the remitter bank raises a query to the UPI server through the UPI APIs, then the beneficiary bank answers the query and accepts the payment. If the payment could not be accepted then the money will be returned to the remitter bank and the customer gets a refund. The changes made by the NPCI are in this UPI API response time.'According to Jain, this means now the remitter and beneficiary banks will communicate amongst themselves faster and hence the transaction's status will be updated faster. Jain explains using an example: if earlier it took maximum 30 seconds to process the response for a UPI transaction request now the same transaction will take half of this time i.e. 15 seconds. So in 30 seconds now two transactions can be done instead of only one earlier.'Vishal Maru- Global Processing Head Financial Software and Systems- FSS, says: "In order to process the higher volume of UPI transactions, its' API response time has been reduced as stated in this circular. Accelerated API cycles effectively address this issue. Consumers will now receive faster transaction confirmations, particularly during reversals or collection requests, instances that usually induce stress."Maru highlights how the faster response time of UPI APIs diminishes system-level retry storms, which not only congest the system but can also lead to cascading timeouts. "By narrowing response windows, UPI is evolving into a self-regulating and failure-resistant network. Quicker timeouts also facilitate a more equitable distribution of traffic among PSPs and banks, enhancing consistency even during peak periods and benefiting users of smaller or regional banks not solely those utilizing the largest applications."Maru from FSS, says that the faster response time of UPI APIs may initially increase the cost by a slight margin, but in the long run it can decrease.'What sets this apart is that shorter response times also enhance cache efficiency and lessen unnecessary database interactions, thereby making each transaction less demanding on system resources. Consequently, although initial expenditures may see a slight increase, the cost per transaction is anticipated to decrease over time, benefiting banks, payment providers, and ultimately consumers. This is not merely an enhancement in speed; it represents a profound systemic optimization that aligns with India's goal to scale UPI to 1,000 crore monthly transactions by 2026 without sacrificing trust, cost, or user says this faster response time feature may not add any cost burden for anybody.'This may add some incremental volume to UPI transactions but more so it will help consumers and merchants. For consumers it would mean faster UPI transactions and for merchants it would mean faster payment received. Also I don't think this is going to add any additional costs of running UPI servers for banks and NPCI,' says Jain.
India.com
10-06-2025
- Business
- India.com
Big news for Paytm, Google Pay, PhonePe users: Starting August 1, you won't be able to check..., even linked accounts, mobile numbers, autopay...
New Delhi: There is news for crores of users who use apps like Google Pay, PhonePe, Paytm. From August 1, National Payments Corporation of India (NPCI) is bringing new rules regarding the use of its Application Programming Interface (API). According to the report, this technical change will be implemented from August 1. According to a report by Financial Express, the purpose of bringing the new rule is to reduce the burden on the UPI system. The effect of this will be that there will be a limit on the balance you check from the UPI app. There will be a change in the auto payments you have set. Let us understand this in detail. Increased load on UPI system According to the report, the number of UPI payments is increasing day by day. Every month around 16 billion transactions are being processed. Due to such a large number of transactions, the load on the UPI system is increasing. In recent times, cases of misuse of the system by banks have come to the fore. Also, some technical weaknesses were also seen. To deal with these, some changes are being made from August 1. UPI service outage According to the report, in the last two-three months, there have been many incidents when UPI payment was down. It is said that on April 12, people were very upset due to the payment being down for 5 hours. This was the longest outage in three years. Because of UPI, many people have stopped keeping wallets or do not keep money in their wallets. In such a situation, if UPI goes down, people face a lot of trouble. The rules are being changed to deal with this situation. The report shows that even a slight interruption in UPI service causes trouble to millions of users. It is said that every second 7 thousand transactions are being processed through UPI. If UPI goes down for even a minute, then 4 lakh people are affected. At present, the number of people making UPI payments is said to be more than 40 crores. A recent investigation revealed that the main reason for UPI going down is the repeated API requests, due to which there is a load on the system. UPI was affected in March and April due to the high number of 'check transaction' API requests. Changes happening from August 1 NPCI has asked all banks and PSPs i.e. PhonePe, Paytm, Google Pay etc. payment service providers to control the 10 most used APIs by July 31. That is, if users check balance more often on UPI app, then now they will not be able to do so. According to the report, users will now be able to check balance 50 times a day on their app. How many accounts are linked to the mobile number, this too will not be seen more than 25 times a day. Apart from this, autopay payments like any SIP or Netflix membership payment will be done only in non-peak hours. Nonpeak hours include before 10 am, from 1 pm to 5 pm, and after 9:30 pm.
Indian Express
30-05-2025
- Politics
- Indian Express
High Court seeks response from L-G, Centre in plea authorising Delhi Police to block online content
The Delhi High Court on Wednesday sought a response from the Delhi Lieutenant Governor and the Ministry of Electronics and Information Technology within six weeks in a public interest litigation challenging a notification appointing the Delhi Police as the nodal agency, under IT Act and Rules, for blocking online content or issuing take down notices. The notification was issued by the L-G in December last year. The challenge comes even as the Indian Cyber Crime Coordination Centre under the Ministry of Home Affairs told the Delhi High Court on April 29 that it is in the process of integrating the Application Programming Interface (API) with around 1,100 entities, including internet service providers, social media intermediaries and telecom network providers on its Sahyog portal. With the API integration with the IT intermediaries and other entities on the cyberspace, any request for a takedown raised by a law enforcement agency, will automatically be pulled down in real-time without any human intervention. For example, the moment a law enforcement agency (LEA) puts a request on the portal for takedown of content, the platform, if its API is already integrated with Sahyog, will take down the content immediately. This will also empower local police stations to order for take down of content. According to a source, over 15,000 LEAs are now onboarded on the portal. The Sahyog portal, launched in 2024, is aimed at expediting the process of sending notices to IT intermediaries by the appropriate government or its agency under Section 79 (3)(b) of the IT Act, 2000 to facilitate the removal or disabling of access to any information, data or communication link with an objective to curtail/detect unlawful/criminal act. The provision of Section 79(3)(b), part of the safe harbour provision, requires that a content flagged as unlawful by the government or its agency, has to be taken down first whereafter any grievance or appeal is entertained. In the petition filed by Software Freedom Law Center India ( through its advocate Musheer Zaidi, the constitutional validity of the notification has been challenged, submitting that the same is without the authority of law, and adds that the IT Act 'does not envisage the creation or functioning of any nodal agency' in the manner as has been done through the notification. SFLC India has contended that such appointment of members of the police as a nodal agency and delegation of authority to law enforcement agencies, without necessary safeguards 'results in unbridled discretion and opens the door for unchecked censorship.' On December 26, 2024, the Home department of the Delhi government issued a gazette notification designating the Delhi Police as the nodal agency for performing functions under Section 79(3)(b) of the IT Act, 2000. The notification also appointed Joint Commissioner of Police, IFSO (Intelligence Fusion and Strategic Operations), Special Cell as state nodal officer, DCP IFSO as he assistant state nodal officer, and DCP of districts, IFSO, EOW, Crime, Special Cell, Special Branch, IGIA, Railways and Metro as designated officers for issuing takedown notice pertaining to cases reported in their respective jurisdictions and for notifying instances of unlawful act online. Seeking quashing of the notification, has argued in its plea that Section 69A of IT Act already establishes the procedure for blocking access to information. It has also argued that IT Act Section 79 (3)(b) 'explicitly establishes that only a notification by the appropriate Government or its agency can be considered for the issuance of takedown orders,' and the L-G, 'even while acting as the so-called 'nodal agency,' cannot unilaterally declare the authority of the Delhi Police to be the 'appropriate government or its agency' for the purposes of issuing such orders.' The petitioner has further submitted that 'allowing them to issue takedown notices without judicial oversight could lead to arbitrary actions, infringing upon the due process of law.' Issuing notice on Wednesday, the bench of Chief Justice D K Upadhyaya and Justice Tushar Rao Gedela kept the matter next for consideration on September 17.
India.com
28-05-2025
- Business
- India.com
UPI Big Update: NPCI to bring new rules from THIS date, issues new guidelines, asks users to...
New Delhi: In a significant development set to impact millions of UPI users, the Unified Payments Interface (UPI) system is expected to see major changes starting August 1, 2025. According to the reports, the National Payments Corporation of India (NPCI) will roll out new Application Programming Interface (API) usage rules for all banks and payment apps. These changes aim to make the system more secure and efficient—but users may face some restrictions. Here are some of the key details: The UPI users will only be able to check their account balance 50 times per day on each UPI. If they use two apps, they will get 50 balance checks on each. APIs allow Payment Service Providers (PSPs) to check if a transaction was successful. Under the new guidelines, PSPs should check transaction status only after a certain time delay. Users will now be able to check which bank accounts are linked to their mobile number only 25 times a day per app. This request will work only if the user selects their bank and gives consent. The NPCI has instructed all banks and payment service providers (PSPs), including Paytm, PhonePe, and others, to closely monitor their API usage. Violators may face penalties, usage restrictions, or even a ban on onboarding new users. All PSPs must also submit a system audit undertaking by August 31, 2025. NPCI says these limits will help improve system stability and security. 'PSP banks and/or acquiring banks shall ensure all the API requests (in terms of velocity and TPS — transactions per second limitations) sent to UPI are monitored and moderated in terms of appropriate usage (customer-initiated and PSP system-initiated)', highlights the circular dated May 21, 2025.
&w=3840&q=100)
Business Standard
27-05-2025
- Business
- Business Standard
Why your UPI app may soon restrict balance and account info requests
The corporation that manages the Unified Payments Interface (UPI) has issued fresh operational guidelines for apps to prevent system overloads and improve the reliability of the popular digital finance system. The guidelines of the National Payments Corporation of India (NPCI) will be effective from August 1, 2025, and are aimed at controlling the volume and frequency of certain high-load API (Application Programming Interface) calls. What it means for UPI users NPCI has identified several non-financial API calls, such as balance enquiries, account listings, and mandate checks, as contributing factors to system slowdowns. To manage these more effectively, NPCI has prescribed the following restrictions: Balance enquiry: Limited to 50 requests per app per customer in a 24-hour rolling window. Issuer banks must also include available balance in every successful UPI transaction message to reduce separate enquiries. List of linked accounts: Limited to 25 times per app per customer per day. Each retry must be customer-initiated in case of failure. Autopay mandates: Execution must happen outside peak hours (10 am to 1 pm and 5 pm to 9.30 pm). Only one attempt and up to three retries per mandate are allowed. List of public keys and verified merchants: Payment services providers (PSP) may only request these once per day, and only during non-peak hours. Transaction Status Checks: Must follow a staggered approach as per earlier guidelines issued by NPCI. Focus on system discipline NPCI has directed all PSP and acquiring banks to monitor and queue both customer-initiated and system-generated API traffic. Systems must not act as direct pass-throughs for backend requests, which can strain UPI's infrastructure. Peak hours are now officially defined as 10 am to 1 pm and 5 pm to 9:30 pm. All non-essential, non-customer-initiated API calls must be restricted during these times. Compliance deadline and audits All UPI members must implement these rules by July 31, 2025. Additionally, banks are required to conduct immediate audits of their systems via Cert-in empanelled auditors, and share the findings with NPCI by August 31, 2025.
