Skip to content
RegionSouth Asia

MediumII Cyber Warfare & Critical Infrastructure6 November 2026, Friday

RBI gives banks until 3 December to harden API payments

According to a MediaNama report on 6 November, the Reserve Bank of India (RBI) told banks in a confidential advisory dated 3 November to add at least one extra security control to fund transfers made via APIs. The deadline for existing integrations is 3 December 2026.

Location: MUMBAI

An API (application programming interface) is the software link that lets a bank accept automated payment instructions from fintechs and non-bank finance companies with a single command. The report says the RBI held a meeting of about two hours with banks; one banker said individual frauds ranged from 3 to 15 crore rupees (1 crore = 10 million). The advisory sets out three main controls: pre-registration of beneficiary accounts, per-transaction and daily limits, and dual authorisation of debit instructions. Transaction limits take effect immediately, and intraday velocity limits within a month.

Customers that are non-bank finance companies will have to pass an audit by a CERT-In-empanelled auditor; the deadline for existing customers is 3 February 2027. StudyCafe reported on 1 November that the RBI had earlier asked banks to prove compliance with existing cyber rules. The same report says two non-bank lenders in Mumbai lost about 2 million dollars on 8–9 October through more than 700 unauthorised instant transfers.

The text of the confidential advisory is not public; as of 6 November its provisions could be verified only through summaries in the press. No data could be found on whether the 2 million dollars in losses was covered by insurance. The RBI's requirement books the cost of preventing such losses to banks' operating budgets for the end of 2026.

Talay assessment

Bottom line

The RBI has turned CERT-In's warnings into dated, binding requirements. The 3 December deadline places the security burden of the bank–fintech API chain squarely on the bank. The most likely path is that smaller fintechs lose integrations because of audit costs, and the attack surface narrows.

Likely effects

  • Fintech and lendingNegativeWeeks

    Beneficiary pre-registration and dual authorisation slow automated payments; integrations that miss the 3 December deadline could be suspended.

  • Bank costsNegative1–6 months

    Annual audits and quarterly customer notifications permanently raise banks' compliance costs.

  • Cyber riskPositive1–6 months

    Limits and pre-registration break the transfer chain that begins with a one-rupee test transaction; individual losses could fall below the 3–15 crore range.

Possibilities, ranked

  1. 1
    Rules applied, timetable holds55%

    Banks deploy at least one security control by 3 December and API-related losses decline.

    Watch: The number of API-related incidents reported to CERT-In after 3 December

  2. 2
    Extension sought30%

    Banks and fintechs ask for more time beyond 3 December and the RBI grants partial flexibility.

    Watch: RBI statements around its 2–4 December meeting

  3. 3
    Attacks continue15%

    Despite the requirements, major new API frauds continue in November and December.

    Watch: Reports of a new crore-scale API fraud in November

Probabilities are calibrated judgement based on the sources, not measurement, and are revised as new information arrives. Not investment advice.

Market reaction

Indicators affected

  • Deadline (existing APIs)▼ 3 December
  • Individual fraud size▼ ₹3–15 crore

Sources

  1. MediaNama — RBI meets bankers amidst rising AI cyber-attacks, mandates security audits
  2. StudyCafe — RBI sounds alarm over rising cyberattacks, pushes banks to strengthen AI defences
Share