Skip to main content

Clari5

India Regional Intelligence Brief | October 2026

For risk, compliance, and fraud leaders at Indian banks

Summary

Regulators and courts are setting a shared standard: act fast on a fraud report, show the evidence, and stop mule accounts early. The Supreme Court wants RBI’s new cyber-fraud rules to carry a liability clause, and RBI’s customer-protection directions start January 1, 2027. The timeline gives banks room to prepare.

Rules are taking shape, with time to prepare

    • Supreme Court (October 29): The Court asked the RBI to include a liability clause in its cyber-fraud rules, with compensation of at least the amount lost where a bank’s due diligence falls short, plus safeguards against unusual transactions. The Attorney General proposed notification by November 30 and operation by December 31. Source
    • RBI customer-protection directions (January 1, 2027, one-year scheme): For electronic transfers up to ₹50,000, victims who report within five days can receive 85% of net loss, capped at ₹25,000. The bank carries the burden of proving customer liability. On losses below ₹29,412, RBI funds 65% and the victim’s bank and the beneficiary bank pay 10% each, so early mule detection benefits every institution. Source
    • Draft mule-hold procedure: RBI’s September 11 draft sets time-bound debit holds on suspected mule transactions or accounts, for up to 60 days, effective April 1, 2027 if finalized as drafted. Final directions are pending, with December reported as a target. Source

Worth reviewing: Whether hold, alert, and complaint workflows can run to these timelines with clear audit trails.

Courts ask for evidence and a prompt response

Recent rulings share one theme: outcomes turn on whether the bank can show system records and a prompt response after a report.

  • Kerala High Court (October 5): ₹3.73 lakh refunded to a customer who shared a one-time password (OTP) under deception. The OTP alone does not prove negligence. Source
  • Kalaburagi consumer commission: ₹4.84 lakh refunded because records did not establish that an OTP was shared. Source
  • Barnala consumer commission: ₹3 lakh plus ₹20,000, with the commission looking for a record of steps to trace the beneficiary and recover funds. Source

Worth reviewing: Whether authentication, complaint handling, and recovery steps can be reconstructed quickly in a contested case.

Mule networks and insiders: what recent cases teach

  • Payment-message integrity (alleged): In a ₹13.96 crore case, 187 transfers on October 15 to 17 reached 107 accounts across 36 banks. Maharashtra Cyber alleges the Real Time Gross Settlement (RTGS) system was tampered with. Receiving banks are not named, so any institution may hold beneficiary accounts. Lesson: monitor payment-message integrity, not only customer behavior. Source
  • Insider and privileged-user risk: In a suspected ₹25 crore case, one employee allegedly used colleagues’ credentials for nearly three years and switched off customer alerts. It surfaced when a customer updated a passbook. Lesson: monitor shared credentials, staff overrides, and live Know Your Customer (KYC) checks at onboarding. Source
  • Linked accounts: In Assam, an account allegedly moved lakhs over 47 days with near-instant withdrawals and was identified through law-enforcement intelligence. In Champawat, 148 linked accounts across several banks were cashed out through ATMs and point-of-sale machines. Lesson: combine bank-side signals with external intelligence. Assam | Champawat

Worth reviewing: Inbound credits and onward movement for October 15 to 17, and links between accounts across institutions.

Supervisors are raising the bar on cyber and API assurance

  • India Today, citing Reuters and unnamed sources, reports that RBI wants banks to evidence cyber compliance, review application programming interface (API) links with NBFCs and fintechs, and detail readiness for attacks that use AI. No circular has been issued. Reported triggers include an advisory from the Indian Computer Emergency Response Team (CERT-In) of October 9. Source
  • Separately, the Economic Times reports about ₹300 crore in losses and about 150 complaints in two months from AI-enabled attacks on small NBFCs. Banks that host NBFC accounts are well placed to detect these flows in flight. Source

Worth reviewing: Whether payout and partner APIs receive the same monitoring as customer channels.

Global context: the same direction

  • EU Court of Justice (case C-70/25): A bank must refund an unauthorized payment immediately, and by the end of the first working day after it learns of it, provided the customer notifies without delay. Suspected gross negligence is not a ground to refuse, and the bank may seek recovery later. Source
  • UK Financial Conduct Authority: Firms closed 238,396 suspected mule accounts in 2025. Criminals usually cash out between the second and fifth account, and older accounts made up a larger share of closures at retail banks, so mule monitoring pays off on existing relationships too. Source
  • Financial Action Task Force (FATF) plenary: The October plenary approved a report on scam compounds, drawing on more than 100 case studies, to help countries disrupt the fraud supply chain. FATF’s President noted that in Thailand funds can leave the financial system within minutes, while victims often take about 20 hours to realize they have been scammed. He added that instant payments and AI-enabled impersonation make money easier to move and hide. FATF | ANI

Dates

  • Expected by about November 8: India AI regulation consultation paper (announced October 8, “within a month”).
  • November 30: Supreme Court hearing; RBI cyber-fraud rules proposed for notification.
  • December (target, unconfirmed): Final RBI mule-account directions; all banks on the Indian Cyber Crime Coordination Centre (I4C) portal.
  • December 31: Proposed date for RBI cyber-fraud rules to operate.
  • January 1, 2027: Customer-protection directions start.
  • April 1, 2027: Draft mule-hold procedure takes effect, if finalized as drafted.

Clari5 is glad to walk through any of these developments with your teams.