Field report N-27 / P3 · sheet /operations
Operations & RestructuringFiled from the territory
City Union Bank Shuts NEFT Gateway After Unauthorised Transfer
City Union Bank shut the NEFT and RTGS gateway for one customer account after an unauthorised transfer on 16 November 2026, disclosing the incident to exchanges two days later. The amount and cause remain undisclosed.
- Grid
- N-27 / P3
- Surveyed
- November 19, 2026
- Reading
- 4 min read
- Correspondent
- Sophie Lindqvist

Field notes
- Unauthorised NEFT transfer from one customer account occurred on 16 November 2026.
- CUB disclosed the incident to NSE and BSE on 18 November 2026 under SEBI LODR Regulation 30.
- The bank shut the NEFT and RTGS gateway for that account and is investigating with external experts.
- The amount involved, the cause and recovery status have not been disclosed.
- CUB recently reported a 27% rise in Q2 FY27 profit to ₹416 crore.
City Union Bank has confirmed an unauthorised NEFT transfer from a customer account on 16 November 2026, and shut down the payment gateway linked to that account within days. The Kumbakonam-headquartered private sector lender disclosed the incident to the NSE and BSE on 18 November 2026, two days after the transaction took place.
The filing, signed by Company Secretary and Compliance Officer Venkataramanan S, was made under Regulation 30 of the SEBI Listing Obligations and Disclosure Requirements Regulations, 2015 — the rule that obliges listed companies to report material events promptly. The bank said it closed the NEFT and RTGS gateway connected to the affected account as soon as it became aware of the incident.
What exactly happened?
According to the filing, one unauthorised transfer went out through the National Electronic Funds Transfer (NEFT) system from a single customer account. The response was targeted: the gateway closure applies to that customer's account, not across the bank. Root-cause analysis is under way, and the bank says corrective measures have started.
The bank is working with external experts on the investigation. That is the full extent of what the disclosure says.
What it does not say is considerable. CUB has not disclosed the amount involved, the identity of the customer, or whether any funds have been recovered. It has not said whether the incident involved compromised credentials, a technical vulnerability, or another form of unauthorised access. The bank stated only that it continues to monitor the situation and will act in line with statutory and regulatory requirements.
Was the bank's business affected?
The bank's own assessment is firm: no material impact on core business operations, financial performance or business continuity. Core functions continue to run normally, it said.
That claim deserves context rather than acceptance at face value. The incident follows a strong quarter for the lender — CUB recently reported a 27% rise in Q2 FY27 profit to ₹416 crore. A single unauthorised transfer in a bank of that scale is unlikely to move financials; the reputational and regulatory exposure is another matter, and the bank's silence on the amount leaves that dimension unmeasured.
The timing also matters. The Reserve Bank of India (RBI) is tightening its focus on cyber risk in payment channels. Earlier this month, the regulator mandated API safeguards for bank-NBFC fund transfers after fraudsters manipulated loan-disbursement instructions. It also issued cyber resilience rules for non-bank payment system operators requiring incidents to be reported within six hours.
Lenders have been hit through payment rails before. Microfinance lender Spandana Sphoorty reported a ₹7.8 crore cyber fraud in which funds were sent to 82 accounts. RBI data showed digital payment frauds rose to 3.58 lakh cases in September.
What does this change for customers?
For CUB customers, the practical position is largely unchanged — but the incident is a prompt to check their own exposure. NEFT and Real Time Gross Settlement (RTGS) are RBI-operated payment systems that run round the clock.
Under the RBI's existing customer protection framework for unauthorised electronic banking transactions, customers can have zero liability when a loss is caused by the bank's negligence, or by a third-party breach reported within three working days of receiving the transaction alert. Customers who notice a suspicious debit should report it to their bank immediately through official channels.
For the sector, the case underlines that monitoring of high-value transfer gateways, beneficiary checks and fast isolation of affected accounts are now core controls rather than back-office tasks. CUB's response — isolating one account's gateway rather than freezing systems bank-wide — followed that playbook.
Key facts from the disclosure
- Date of incident: 16 November 2026; disclosed to exchanges on 18 November 2026.
- Scope: one customer account; the NEFT and RTGS gateway for that account was shut down.
- Response: internal investigation with external experts; root-cause analysis and corrective measures in progress.
- Business impact: no material impact on core operations, financial performance or business continuity, according to the bank.
The open questions — how much money moved, how the access occurred, and whether it has come back — now sit with the investigation. Until CUB answers them, the bank's "no material impact" assurance rests on numbers it has chosen not to publish.
via bfsi.eletsonline.com (Source)
More from Sophie Lindqvist
Show full bio
Correspondent covering money, funding and market shifts around corporate strategy and chief-executive leadership at CEO Frontier.
483 articles
Adjacent sheets
- EFCC testimony links Emefiele to alleged $17 million forex scheme
- Nembe Says EFCC Recovered Pipeline Fees Owed to Its NNPCL Venture
- Nigeria's DisCos Accuse NNPC of 'Half-Truths' as Outages Spark Calls for Minister's Exit
- Standard Bank hit with R17m penalty for FIC Act breaches
- RBI Clears Pratap Singh as Fino Payments Bank MD and CEO for Three Years