Last verified & updated: October 2026
Reviewed by: FixMyIssues Banking Consumer Protection & Legal Desk
Discovering that funds have been deducted from your bank account or credit card without your authorization is distressing. But what is often more frustrating is the immediate reaction of bank branch staff, who frequently dismiss victims with statements like: "Since an OTP was generated by our system, our system shows no flaw; you must have shared it, so the bank cannot reimburse you."
Under the law of the land and directives issued by the Reserve Bank of India (RBI), this dismissal is legally incorrect.
Under RBI's Master Circular on "Customer Protection – Limiting Liability of Customers in Unauthorised Electronic Banking Transactions" (Circular No. DBR.No.Leg.BC.78/09.07.005/2017-18), the legal burden of proof does not rest on the customer—it rests entirely on the bank.
This guide outlines exactly how to build an airtight, legally fortified bank dispute dossier that forces your bank to adhere to statutory mandates, trigger inter-bank liens, and credit the disputed funds back to your account.
1. Statutory Foundations: Know Your Rights Under RBI Law
Before communicating with bank officials, understand the three pivotal clauses of the RBI Master Direction that govern electronic transactions (UPI, NEFT, IMPS, Debit Cards, and NetBanking):
A. The Burden of Proof Rests on the Bank (Clause 12)
"The burden of proving customer liability in case of unauthorised electronic banking transactions shall lie on the bank."
Banks cannot merely state that their system sent an OTP or that a transaction was authenticated by a PIN. If you assert on written record that you did not authorize the debit, the bank must provide forensic proof (such as IP logs, device fingerprinting, and session tokens) proving your personal involvement.
B. Zero Liability Tiers (Clause 6)
Your liability is strictly determined by how quickly you report the unauthorized debit to the bank after receiving the SMS alert:
| Reporting Window | Customer Financial Liability | Statutory Obligation of Bank | | :--- | :--- | :--- | | Within 3 Working Days | ₹0 (Zero Liability) | Full reversal of stolen funds | | Within 4 to 7 Working Days | Capped at ₹5,000 (Basic Savings) or ₹10,000 (Other Savings Accounts) | Bank absorbs all losses beyond the statutory cap | | Beyond 7 Working Days | Determined by Bank Board-approved policy | Subject to RBI Ombudsman review |
C. The Mandatory 10-Day "Shadow Credit" Rule (Clause 9)
"The bank shall credit (shadow reversal) the amount involved in the unauthorised electronic transaction to the customer's account within 10 working days from the date of such notification by the customer."
Even while the bank or police investigation is still ongoing, your bank is legally required to provide a temporary "shadow credit" or provisional reversal of the disputed sum within 10 working days, pending final resolution within 90 days.
2. Assembling the 6 Core Evidentiary Documents
A bank dispute cannot succeed on oral complaints or emotional appeals. When visiting the branch or submitting your grievance online, prepare the following Dispute Dossier:
graph TD
A[Dispute Dossier] --> B[1. Stamped Account Statement with Highlighted UTR]
A --> C[2. 1930 NCRP Acknowledgment Slip]
A --> D[3. Certified SMS Gateway Delivery Logs]
A --> E[4. Police Diary Receipt / Cyber Cell GD]
A --> F[5. Self-Declaration Affidavit of Non-Sharing]
A --> G[6. Formal Written Dispute Letter citing RBI Norms]
Document 1: Official Bank Statement with 12-Digit UTRs Highlighted
Download your official PDF account statement covering the 7 days prior to and 3 days following the incident.
- Use a highlighter to mark the unauthorized debit rows.
- Ensure the 12-digit Unique Transaction Reference (UTR) or NPCI RRN number is clearly legible. The bank's clearing desk cannot search the inter-bank reconciliation gateway without this 12-digit number.
Document 2: 1930 NCRP Acknowledgment Slip
Print the formal receipt generated when you dial 1930 or submit your incident on cybercrime.gov.in. This document proves you reported the incident to law enforcement within the "Golden Window" and provides the official National Cyber Crime Reporting Portal (NCRP) acknowledgment number.
Document 3: SMS and Carrier Records
Take high-resolution screenshots of the debit alert SMS showing:
- The exact timestamp (date, hour, minute).
- The sender header (e.g.,
VK-HDFCBKorAD-SBIINB). - If you did not receive an SMS until hours later due to network delay or SIM swap fraud, download your telecom carrier's itemized call and SMS record to prove notification latency.
Document 4: Police General Diary (GD) or Station Receiving Slip
Visit your local police station or district cyber crime cell. Submit your initial statement and obtain a stamped receiving slip with a General Diary (GD) or Daily Diary (DD) number.
Document 5: Non-Disclosure Self-Affidavit
A signed written declaration stating under oath:
- You did not disclose, forward, or share any OTP, UPI PIN, ATM PIN, or NetBanking password with any third party.
- The debit took place without your active initiation or consent.
- You did not authorize any screen-sharing application session at the exact minute of the transaction.
Document 6: Formal Dispute Letter
Never submit loose papers. Accompany the annexures with a formally structured complaint letter addressed to the Branch Manager and the Principal Nodal Officer.
👉 Tip: You can generate a formatted, court- and bank-compliant PDF letter using our free citizen tool: Generate Formal Bank Dispute Letter Draft.
3. How to Dismantle Common Bank Rejections
When bank officers attempt to close your dispute without compensation, they rely on standard boilerplates. Here is the legal and technical rebuttal for each:
Rejection 1: "The transaction was executed using OTP / 2-Factor Authentication, so it is your fault."
- The Legal Rebuttal: The Supreme Court of India and various State Consumer Disputes Redressal Commissions have repeatedly ruled that the mere generation or transmission of an OTP by a bank's SMS server does not constitute conclusive evidence that the legitimate accountholder received or authorized it.
- Mention modern attack vectors on record: SIM swap attacks, SS7 cellular signaling exploits, AePS silicone fingerprint cloning, and Trojan malware with SMS-reading permissions (
RECEIVE_SMS). - Demand that the bank provide the telecommunication delivery handshake receipt proving that the OTP was delivered to your physical device handset IMEI, and not diverted via an unauthorized e-SIM or telecom port.
Rejection 2: "You must contact Google Pay / PhonePe / Paytm; we are only the account provider."
- The Legal Rebuttal: Under NPCI and RBI operating regulations, Third-Party Application Providers (TPAPs) like Google Pay or PhonePe are merely technical conduits. The customer's legal banking relationship exists strictly with the Issuing Bank (Remitter Bank).
- Remind the Branch Manager that under RBI Circular
DBR.No.Leg.BC.78/09.07.005/2017-18, the remitter bank is legally responsible for customer liability and dispute settlement, regardless of whether a third-party UPI application was used to initiate the clearing request.
Rejection 3: "The money has already been withdrawn at an ATM by the scammer, so we cannot reverse it."
- The Legal Rebuttal: The recovery of funds from the fraudster's account is an inter-bank recovery and law enforcement matter; it has no bearing on the customer's statutory right to zero liability under RBI rules.
- If the unauthorized transaction was reported within 3 working days and resulted from third-party breach or system vulnerability, the bank is obligated to compensate the customer from its internal fraud insurance reserves, regardless of whether the beneficiary mule account balance is zero.
4. The 30-Day Dispute Escalation Timeline
Do not wait passively for your bank to call you. Follow this strict calendar to preserve your right to approach the RBI Ombudsman:
[Day 0: Incident Occurs]
│
├─► Hour 0-2: Dial 1930 & Call Bank Fraud Helpline (Block Cards/UPI)
├─► Day 1-3: Submit Dispute Dossier in person at Home Branch
│ (MUST obtain stamped duplicate receiving copy)
│
[Day 10: Statutory Milestone]
│
└─► If no resolution, verify if Provisional Shadow Credit has been posted
under Clause 9 of RBI Customer Liability Circular
│
[Day 15: Grievance Escalation]
│
└─► If branch is unresponsive, escalate via email to the bank's
Internal Principal Nodal Officer (PNO) attaching the stamped receiving copy
│
[Day 30: RBI Ombudsman Gateway Opens]
│
└─► If 30 calendar days elapse without complete resolution, or if the bank
rejects your dispute: Lodge an official complaint on the RBI CMS Portal
(cms.rbi.org.in) under the Reserve Bank - Integrated Ombudsman Scheme.
5. Submitting Your Dispute: Step-by-Step Instructions
- Do Not Rely on Phone Calls Alone: Customer care telephone calls are often recorded for quality purposes but rarely constitute formal evidentiary submissions under Indian Evidence Act standards. Always ensure a written trail exists.
- Submit via Registered Email: Send an email from your registered email address to the official Customer Care email and Principal Nodal Officer (PNO) email of your bank.
- Visit the Branch in Person with Two Hard Copies: Take two identical printed copies of your dispute letter with all annexures attached. Hand one copy to the Branch Manager and demand that the officer stamp, sign, date, and write a Docket/Reference Number on your copy.
- Log the Dispute in Your Recovery Tracker: Record your bank ticket reference number and monitor your statutory 30-day timeline using our Cyber Fraud Recovery Workspace.
6. Official Regulatory Citations & Statutory References
When drafting your complaint, cite these specific regulations:
- Reserve Bank of India (RBI): Master Circular
DBR.No.Leg.BC.78/09.07.005/2017-18on Customer Protection – Limiting Liability of Customers in Unauthorised Electronic Banking Transactions. - Reserve Bank - Integrated Ombudsman Scheme, 2021 (RB-IOS): Section 10 (Grounds of Complaint for Deficiency in Service).
- Bharatiya Nagarik Suraksha Sanhita (BNSS), 2023: Section 106 (Power of police officer to seize or freeze property related to crime, replacing Section 102 CrPC).
- Information Technology Act, 2000: Section 43 (Penalty for damage to computer system) & Section 66D (Cheating by personation by using computer resource).
🔗 Related Resources
Editorial Sourcing & Methodology
Researched in compliance with guidelines from the Reserve Bank of India (RBI) and the National Cyber Crime Reporting Portal (1930). Read our Editorial Policy.
Need to file a formal complaint?
Use our automated utility to draft a precise Cyber Cell application and escalate to your bank's nodal officer instantly.
Open Complaint Generator