LegalRecoveryLegalRecovery Home
RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18•In Force Since 6 July 2017 (Updated Nov 2026)

Unauthorised Bank Transaction? RBI's Zero and Limited Liability Rules

Statutory Rulebook Summary (RBI Circular RBI/2017-18/15 • Clauses 6, 7, 9 & 12)

Under RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18, bank customers enjoy 100% Zero Liability for unauthorised electronic transactions caused by bank deficiency or third-party breaches if reported within 3 working days (and capped liability of ₹5,000–₹25,000 if reported in 4–7 working days). Your bank bears the burden of proof and must credit a value-dated shadow reversal within 10 working days.

3 Days

100% Zero Liability Window

10 Days

Mandatory Shadow Reversal

₹5k–₹25k

4–7 Day Limited Liability Cap

On Bank

Clause 12 Burden of Proof

1. When Does a Bank Customer Have 100% Zero Liability for an Unauthorised Transaction?

Under Paragraph 6 of RBI Circular No. RBI/2017-18/15 (DBR.No.Leg.BC.78/09.07.005/2017-18) dated 6 July 2017, a customer is legally entitled to 100% Zero Liability in two situations: (a) whenever the unauthorised transaction arises from contributory fraud, negligence, or deficiency on the part of the bank (even if not reported by the customer); or (b) in any third-party breach where neither the bank nor the customer is at fault and the customer notifies the bank within 3 working days of receiving the bank's transaction alert.

The Reserve Bank of India enacted this binding statutory directive under Section 35A of the Banking Regulation Act, 1949 to stop commercial banks from hiding behind one-sided account terms. Under Paragraph 6(a), if the loss occurs due to a bank server vulnerability, an insider employee leak, card skimming at an ATM, or an international transaction processed without mandatory Additional Factor of Authentication (AFA/OTP), the customer's liability is zero from Day 1—irrespective of whether or when the customer reports it.

Under Paragraph 6(b), where the fraud originates from a third-party system breach—such as a compromised merchant database, a telecom SIM-swap attack, or a malicious APK/remote-screen exploit where the customer never voluntarily shared their OTP or MPIN to authorise the payment—the customer incurs zero financial loss provided they notify the bank within three working days of receiving the communication from the bank regarding the unauthorised debit. Crucially, Footnote 1 to Paragraph 6(b) specifies that the 3-working-day count excludes the exact date on which the customer received the alert.

2. What Is Your Limited Liability If You Report Between 4 and 7 Working Days?

Under Paragraph 7(b) and Table 1 of the 6 July 2017 RBI Circular, if a third-party breach is reported with a delay of 4 to 7 working days after receiving the bank's transaction alert, the customer's per-transaction liability is strictly capped at the transaction value or ₹5,000 (BSBDA accounts), ₹10,000 (regular Savings Accounts, Prepaid Wallets, Credit Cards up to ₹5 lakh limit, and MSME/Individual Current or OD accounts), or ₹25,000 (large Current/OD accounts and Credit Cards above ₹5 lakh limit)—whichever is lower.

Banks frequently mislead customers into believing that missing the 3-working-day window forfeits the entire refund claim. That is false under the RBI rulebook. If ₹1,80,000 is siphoned from your regular savings account in a third-party breach and you report it on the 5th working day after receiving the SMS alert, the bank can deduct at most ₹10,000 (your limited liability cap under Table 1) and must statutorily refund the remaining ₹1,70,000 to your account.

Only when a customer delays reporting beyond 7 working days after receiving the bank's alert does liability fall under the bank's Board-approved policy (Paragraph 7(b)(ii)). Even then, the bank must publicly display that Board-approved policy and provide every customer with its details at the time of account opening. For active recovery assistance on disputed debits, review our dedicated hub on recovering fraudulent UPI, card and bank transaction amounts.

3. Within How Many Working Days Should Shadow Reversal Be Credited by the Bank?

Under Paragraph 9(i) and 9(ii) of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18, the bank must credit (shadow reversal) the amount involved in the unauthorised electronic transaction to the customer's account within 10 working days from the date of notification by the customer—value-dated to the exact date the unauthorised transaction occurred, and without waiting for any insurance settlement.

This is one of the most heavily searched banking rules in India (and a core benchmark in JAIIB/CAIIB banking examinations and Ombudsman adjudications): 10 working days from the date of customer notification. A "shadow reversal" (or provisional credit) restores the disputed funds to your account ledger while the bank conducts its internal forensic or chargeback investigation.

  • •Value-Dated to the Date of Fraud (Paragraph 9(ii)): For a savings or overdraft account, back-dating the shadow credit to the date of the unauthorised debit ensures you lose zero savings interest and pay zero penal overdraft interest. For a credit card, it ensures zero 36%–42% finance charges or late-payment penalties accrue on the fraudulent swipe.
  • •No Insurance Delay Excuse (Paragraph 9(i)):Banks carry Bankers' Indemnity and Cyber Crime Insurance policies, but Paragraph 9 explicitly forbids banks from delaying your 10-working-day shadow credit while waiting for their insurer to approve or settle the claim.

4. Who Bears the Burden of Proof in an Unauthorised Electronic Transaction Dispute?

Paragraph 12 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 states in a single, unconditional sentence: "The burden of proving customer liability in case of unauthorised electronic banking transactions shall lie on the bank."

In practice, almost every retail bank in India initially rejects fraud complaints with a standard two-line email stating: "The transaction was authenticated via 2FA/OTP/MPIN; hence the bank is not liable." Under Paragraph 12, that mechanical assertion does not discharge the bank's statutory burden.

As the Bombay High Court held in Jaiprakash Kulkarni v. Banking Ombudsman & Bank of Baroda (2024), the mere fact that an electronic system recorded an OTP or IP log does not prove that the customer negligently shared credentials—especially where SIM-cloning, malware SMS-forwarding APKs, man-in-the-middle attacks, or unverified beneficiary additions occurred. To deny a refund, the bank must furnish concrete forensic evidence establishing affirmative customer negligence.

Paragraph 9 & 12 RBI Enforcement • 10-Working-Day Shadow Credit Mandate

Reported Within 3–7 Working Days Still Waiting for Bank Refund?

Force your bank to discharge its statutory burden of proof under Clause 12 and credit value-dated shadow reversal with a formal advocate legal notice.

5. What If You Were Tricked Into Sharing an OTP—Who Bears Losses After You Notify the Bank?

Under Paragraph 7(a)(i) of the 6 July 2017 RBI Circular, where the loss is due to negligence by a customer (such as sharing payment credentials/OTP), the customer bears the loss only until they report the unauthorised transaction to the bank; 100% of any loss occurring after the reporting of the unauthorised transaction must be borne by the bank.

This is a vital legal lifeline in multi-tranche phishing frauds. Suppose a fraudster tricks an account holder at 2:10 PM into sharing an OTP for a ₹15,000 debit. Realising the scam immediately, the customer calls the bank's 24x7 toll-free fraud hotline at 2:14 PM or sends the mandatory SMS block command. If the bank's IVR fails to freeze the account immediately and the fraudster executes three more debits of ₹50,000 each at 2:22 PM, 2:25 PM, and 2:30 PM, Paragraph 7(a)(i) makes the bank 100% liable for the ₹1,50,000 debited after 2:14 PM.

Furthermore, under Paragraph 7(a)(ii), banks are expressly encouraged by the RBI to waive even the pre-reporting customer liability in cases of tricked credentials via a Board-approved policy. If you instead transferred money yourself to an unintended recipient or wrong account number, use our wrong account transfer refund application format to initiate beneficiary-bank lien marking and reversal.

6. What Happens If the Bank Fails to Resolve Your Complaint Within 90 Days?

Under Paragraph 11 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18, a bank must resolve the complaint and establish customer liability, if any, within a period not exceeding 90 days from the date of receipt of the complaint. If the bank is unable to resolve the complaint within 90 days, the bank must permanently pay the customer the full compensation prescribed in Paragraphs 6 to 8.

The RBI inserted Paragraph 11 to prevent banks from keeping a customer's shadow credit in perpetual "lien" or "under investigation" status for years. The bank has a strict 90-calendar-day outer ceiling from the complaint date to complete its forensic audit and prove customer liability. If Day 90 expires without conclusive proof of customer negligence, the provisional shadow reversal becomes absolute and irrevocable, with zero loss of debit-account interest or imposition of credit-card interest.

7. Does the RBI Zero Liability Circular Cover UPI, Credit Cards, and Prepaid Wallets (PPIs)?

Yes. Paragraph 4 of the 6 July 2017 Circular covers all remote/online electronic banking transactions (Internet Banking, Mobile Banking, UPI, IMPS, NEFT/RTGS, and Card-Not-Present CNP transactions) as well as face-to-face ATM and POS transactions. Additionally, RBI Circular DPSS.CO.PD.No.1414/02.14.006/2018-19 dated 4 January 2019 extends the exact same 3-day Zero Liability and 10-day shadow reversal rules to Prepaid Payment Instruments (PPIs) and mobile wallets.

Whether an unauthorised debit hit your savings account via a UPI collect/push exploit on Google Pay, PhonePe, or Paytm, or via an unauthenticated credit card swipe or wallet transfer, the statutory protections are identical. Under the 4 January 2019 PPI Circular, even non-bank wallet issuers must provide 24x7 reporting channels, send mandatory SMS alerts for every debit, cap 4–7 day reporting liability at ₹10,000, and credit shadow reversal within 10 days. If your bank instead deducted wrongful auto-debits or bounce fees, see our guide on serving a legal notice for unauthorised ECS/NACH debit reversal and recovering unauthorised bank charges and liens.

8. Why Did the Supreme Court Rule That State Bank of India Must Refund Unauthorized Withdrawals?

In State Bank of India v. Pallabh Bhowmick & Ors. (SLP (C) Diary No. 55621/2024, decided 3 January 2025), the Supreme Court upheld the Gauhati High Court Division Bench ruling that State Bank of India must refund ₹94,204.80 siphoned from a customer's account via a malicious third-party app, because the customer reported the fraud within 24 hours (inside the 3-working-day Zero Liability window) and never voluntarily shared an OTP or MPIN to authorise the debits.

This landmark 2025 Supreme Court order destroys the two most common excuses banks use to reject cyber-fraud victims: (1) claiming that the transaction happened through a third-party UPI app like Google Pay or PhonePe, and (2) claiming that installing an app during a customer-service call automatically equals "customer negligence". The Supreme Court observed that banks hold the statutory duty to deploy robust anomaly-detection technology capable of flagging suspicious, rapid-fire withdrawals, and must honour Clauses 8 and 9 of the 2017 RBI Circular when customers report promptly.

9. What Duties Does Paragraph 5 Impose on Banks Regarding SMS Alerts and Loss Reporting?

Under Paragraphs 4 and 5 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18, banks must mandatorily register all electronic banking customers for SMS alerts, send instant SMS alerts for every electronic debit, allow customers to report unauthorised transactions simply by replying to the SMS alert without searching for a helpline number, and send an immediate acknowledgment with a registered complaint number.

If a bank fails to send an instant SMS alert for an electronic banking debit, or if its toll-free fraud hotline/IVR was unreachable when you tried to report the loss, the bank violates Paragraph 5. Under the RBI circular, the 3-working-day reporting window is measured strictly from the date of receiving the communication from the bank—meaning if no SMS was delivered, your 3-day window begins only when you first receive your passbook update or email statement. Additionally, always report the incident on the 1930 National Cyber Crime Helpline and cybercrime.gov.in (see our Hindi guide on साइबर फ्रॉड का पैसा वापस कैसे मिलेगा for step-by-step 1930 freeze procedure).

10. How Does the 1 January 2027 RBI Revised Framework Change Fraud Compensation? (†)

Effective 1 January 2027†, the RBI's Revised Framework for Fraudulent Electronic Banking Transactions (issued via the June 2026 Responsible Business Conduct Amendment Directions) replaces the 2017 circular for transactions on or after that date—retaining the bank's strict burden of proof while introducing a new one-time compensation of 85% of net loss or ₹25,000 (whichever is lower)† for small-value frauds up to ₹50,000† reported within 5 calendar days†, even where the victim was tricked into authorising the payment.

Under the 2017 circular, if a victim was manipulated through social engineering, fake KYC threats, or "digital arrest" coercion into entering their own UPI PIN or reading out an OTP, banks routinely denied refunds under Paragraph 7(a) as "customer-authorised transactions". The 1 January 2027 framework† closes that gap for small retail losses (gross loss ≤ ₹50,000) by creating a tripartite compensation pool shared by the RBI, the customer's bank, and the beneficiary bank—provided the victim reports to both their bank and the 1930 / NCRP portal within 5 calendar days†. For a full breakdown of the new rules, read our dedicated guide on the RBI Fraudulent Transaction Framework 2027.

11. RBI Zero & Limited Liability Eligibility Checker (Static Yes/No + Interactive Calculator)

Verify the 5-point statutory Yes/No rulebook checklist below or use the interactive calculator to determine your exact refund entitlement under RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18:

Statutory 5-Point Yes/No Eligibility Checklist (Clauses 6, 7 & 9)

  • YES / NO1. Electronic Banking or PPI Channel: Did the debit occur via UPI, IMPS, NEFT, RTGS, Internet/Mobile Banking, Debit/Credit Card (POS/ATM/Online), or a regulated Prepaid Wallet? (If YES → Covered under RBI Circulars 2017-18/15 & 2018-19/101)
  • YES / NO2. Absence of Deliberate Credential Sharing (or Post-Notification Debit): Did the debit occur without you consciously sharing an OTP/PIN/MPIN for that transaction—OR did it occur after you had already alerted the bank helpline? (If YES → Eligible for Zero/Limited Liability)
  • YES / NO3. Reported Within 3 Working Days of Bank Alert: Did you notify your bank within 3 working days after the date on which you received the SMS/email debit alert? (If YES → 100% Zero Liability under Paragraph 6(b))
  • YES / NO4. Reported Between 4 and 7 Working Days: If you missed the 3-day window, did you notify the bank within 4 to 7 working days of the alert? (If YES → Bank must refund 100% of the loss above the ₹5,000 / ₹10,000 / ₹25,000 Table 1 cap)
  • YES / NO5. 10 Working Days Elapsed Without Shadow Reversal: Have more than 10 working days passed since your complaint without the bank crediting a value-dated shadow reversal? (If YES → Bank is in statutory breach of Paragraph 9; serve an Advocate Legal Notice & file on RBI CMS)
Interactive RBI Rulebook Calculator (Table 1 & Table 2)

Calculate Your Exact Liability & Bank Refund Under the RBI Circular

Clauses 6, 7 & 9
₹85,000
₹5,000₹50,000 (2027 Cap†)₹1,00,000₹2,50,000₹5,00,000
Paragraph 6(b) & Table 2 — 100% Zero Customer Liability (Reported Within 3 Working Days)Shadow Credit Due: Within 10 Working Days (Para 9)
Mandatory Bank Refund / Reversal₹85,000
Maximum Customer Liability₹0

Because neither you nor the bank was at fault and you notified the bank within 3 working days (excluding the date of SMS alert), your liability is ₹0. The bank must credit 100% shadow reversal within 10 working days.

Select Your Unauthorised Transaction Dispute Scenario

Money Siphoned via Malicious APK, Screen-Sharing App, or SIM-Swap Without Voluntarily Sharing OTP

How the Dispute Happens

Fraudsters trick the account holder into installing a fake courier/bank/utility APK or execute a SIM-swap, intercepting SMS alerts and draining funds via UPI, IMPS, or NetBanking without the customer consciously entering an MPIN or reading out an OTP.

Governing RBI Circular Clause & Case Law

Paragraph 6(b) & Paragraph 12 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 + Supreme Court in State Bank of India v. Pallabh Bhowmick (2025).

Statutory Customer Liability

₹0 (Zero Liability) if notified within 3 working days; capped at ₹5,000–₹25,000 if notified in 4–7 working days.

3-Step Legal Escalation Fix

Demand immediate 10-working-day shadow reversal under Paragraph 9. Cite the Supreme Court's January 2025 Pallabh Bhowmick ruling holding that downloading an app during a customer-care inquiry is not 'deliberate credential sharing' and the bank is liable for failing to block anomalous high-velocity transfers.

12. Official RBI Customer Liability Tables (Table 1, Table 2 & 2017 vs. 2027 Framework)

Below are the exact statutory liability slabs reproduced from Paragraph 7 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 alongside a side-by-side comparison with the upcoming 1 January 2027 Revised Framework†:

RBI Circular Table 2 — Summary of Customer Liability by Reporting Time
Nature of Breach & Time Taken to Report from Date of Receiving Bank AlertCustomer's Liability (RBI Circular Clause)Mandatory Bank Reversal Duty
Contributory fraud / negligence / deficiency on the part of the bank (irrespective of reporting by customer)Zero Liability (₹0) — Para 6(a)100% value-dated reversal within 10 working days
Third-party breach reported within 3 working days (excluding date of alert communication)Zero Liability (₹0) — Para 6(b)100% shadow reversal within 10 working days (Para 9)
Third-party breach reported within 4 to 7 working daysCapped at ₹5,000 / ₹10,000 / ₹25,000 (Table 1) — Para 7(b)Bank refunds 100% of amount exceeding the Table 1 cap within 10 working days
Third-party breach reported beyond 7 working daysAs per Bank's Board-Approved Policy — Para 7(b)Policy must be transparently disclosed; 3-day clock starts only when alert delivered
Loss occurring AFTER customer notifies the bank (even in OTP negligence cases)Zero Liability (₹0) — Para 7(a)(i)100% of post-reporting debits borne unconditionally by the bank
RBI Circular Table 1 — Maximum Customer Liability by Account Type (4 to 7 Working Days)
Type of Bank Account / Card / Payment Instrument (RBI Table 1)Maximum Customer Liability (4–7 Working Days)
Basic Savings Bank Deposit (BSBD) Accounts₹5,000 (or transaction value, whichever is lower)
All other Savings Bank accounts • Pre-paid Payment Instruments (PPIs) & Gift Cards • Credit Cards with limit up to ₹5 lakh • Current / Cash Credit / Overdraft accounts of MSMEs • Current / CC / OD accounts of Individuals with annual average balance up to ₹25 lakh₹10,000 (or transaction value, whichever is lower)
All other Current / Cash Credit / Overdraft accounts • Credit Cards with limit above ₹5 lakh₹25,000 (or transaction value, whichever is lower)

13. Statutory Escalation Flowchart: From Unauthorised Debit to 10-Day Shadow Credit & Ombudsman Award

Follow this 5-stage statutory escalation rail to lock in your 3-working-day Zero Liability timestamp and force your bank to release your refund:

Step 1 • Day 0 to Day 3

Notify Bank & Call 1930 Immediately

Reply to bank SMS alert, block card/UPI via 24x7 helpline, and log NCRP docket on 1930 / cybercrime.gov.in within 3 working days.

Step 2 • Within 10 Working Days

Demand Paragraph 9 Shadow Reversal

File written dispute form at branch & Nodal Officer demanding value-dated shadow credit within 10 working days.

Step 3 • Day 11 to Day 15

Challenge Generic 'OTP Shared' Denial

Invoke Paragraph 12 burden of proof & SBI v. Pallabh Bhowmick (2025) demanding forensic server/IP logs.

Step 4 • 15-Day Statutory Notice

Serve Advocate Legal Notice to Bank MD & Nodal Cell

Dispatch formal advocate legal notice via Speed Post + Email demanding principal + interest.

Step 5 • Day 30 Onwards

RBI Ombudsman (CMS) or Consumer Court (e-Jagriti)

Escalate to cms.rbi.org.in (RB-IOS 2021) or file deficiency petition on e-Jagriti for 100% refund + damages.

RBI Zero-Liability Escalation FlowchartSwipe horizontally →
STEP 1 (≤ 3 DAYS)Report to Bank & 1930SMS Reply + HelplineLocks Zero Liability (Para 6)STEP 2 (≤ 10 DAYS)Shadow ReversalMandatory Provisional CreditValue-Dated (Para 9)STEP 3 (PARA 12)Burden on BankDemand Forensic LogsMax 90d Resolution (Para 11)STEP 4 (DAY 11+)Advocate Notice15-Day Statutory DemandBank Nodal Officer + MDSTEP 5 (DAY 30+)Ombudsman / Courtcms.rbi.org.in (RB-IOS)or e-Jagriti + HC WritSTATUTORY BENCHMARKS UNDER RBI CIRCULAR DBR.No.Leg.BC.78/09.07.005/2017-18 & 2027 FRAMEWORK (†):• Within 3 Working Days (excluding alert date): 100% Zero Customer Liability in third-party breaches (Paragraph 6(b))• Within 10 Working Days of Notification: Bank must credit value-dated Shadow Reversal without waiting for insurance (Paragraph 9)• Within 90 Calendar Days: Outer limit for bank to prove customer negligence under Paragraph 12; else full claim stands allowed• From 1 Jan 2027†: Losses ≤ ₹50,000 reported within 5 calendar days get 85% or ₹25,000 one-time payout even in social-engineering scams

14. Landmark Supreme Court, High Court & NCDRC Precedents Enforcing RBI Zero Liability

Verifiable Judicial Rulings
Precedent #1 • SLP (C) Diary No. 55621/2024, Supreme Court of India (Aff'g WA 282/2024, Gauhati HC)Order Dated 03 January 2025

State Bank of India Must Refund Unauthorised Withdrawals Reported Within 3 Working Days

Parties: State Bank of India v. Pallabh Bhowmick & Ors.

The Dispute & Facts:

In October 2021, an SBI savings account holder attempted to return an online apparel order and received a phone call from a fraudster impersonating customer support. Tricked into installing a malicious remote-access application, three unauthorised debits totalling ₹94,204.80 were siphoned from his SBI account. The customer notified SBI within 24 hours (well inside the 3-working-day RBI window). Both SBI and the RBI Ombudsman rejected the refund claim, contending that the transactions occurred via Google Pay and alleging customer negligence.

Judicial Holding:

A Supreme Court bench comprising Justice J.B. Pardiwala and Justice R. Mahadevan dismissed SBI's appeal and upheld the Gauhati High Court Division Bench order directing a 100% refund. The Court held that under Clauses 8, 9, and 12 of the RBI Circular dated 6 July 2017, a customer who reports an unauthorised electronic transaction within 3 working days enjoys Zero Liability where no deliberate sharing of OTP or MPIN is proved by the bank. The Supreme Court emphasised that banks possess advanced fraud-monitoring infrastructure and cannot shift blame onto customers when high-velocity unauthorised debits bypass bank security filters.

Judicial Relief / Binding Order100% Refund of ₹94,204.80 Ordered Against State Bank of India
Statutory Authority CitedClauses 6, 8, 9 & 12 RBI Circular (6 July 2017)
What this means for your bank dispute: If you were duped into downloading an APK or remote-support tool without consciously authorising the specific debit via OTP/MPIN and you notified your bank within 3 working days, your bank cannot reject your claim with generic 'customer negligence' templates.
Precedent #2 • Writ Petition No. 1150 of 2023, 2024 SCC OnLine Bom 1666 (Bombay High Court DB)Judgment Dated 06 May 2024

Bank Bears Strict Burden of Proof Under Clause 12; Cyber-Police Pendency Cannot Block Refund

Parties: Jaiprakash Kulkarni & Anr. v. The Banking Ombudsman & Bank of Baroda

The Dispute & Facts:

A total of ₹76,90,000 was siphoned from the petitioners' account at Bank of Baroda through 23 unauthorised online transactions to unknown beneficiaries added without the customer's consent or OTP sharing. The petitioners notified the bank within hours of receiving the alerts. Both the bank and the Banking Ombudsman refused reversal, claiming that police cyber-cell investigation was still pending.

Judicial Holding:

The Division Bench of the Bombay High Court quashed the Ombudsman's rejection and ordered Bank of Baroda to refund the entire ₹76.90 lakh with 6% annual interest. The Court held that Paragraph 6(b) and Paragraph 12 of the RBI Circular dated 6 July 2017 place the statutory burden of proving customer negligence exclusively on the bank. Once a customer reports a third-party breach within 3 working days and forensic/bank logs show no voluntary OTP sharing, the bank must credit the account within 10 working days without waiting for police recovery or insurance settlement.

Judicial Relief / Binding Order₹76,90,000 Full Principal Refund + 6% Annual Interest
Statutory Authority CitedClauses 6, 8, 9 & 12 RBI Circular (6 July 2017)
What this means for your bank dispute: Your bank cannot tell you to 'wait until the cyber police catch the fraudster'. Under Paragraph 9 of the RBI Circular, bank liability under Zero Liability is independent of criminal recovery.
Precedent #3 • RSA No. 1097 of 2018, 2019 (1) KLT 305 (Kerala High Court)Judgment Dated 29 January 2019

Bank Strictly Liable for Unauthorised Overseas Withdrawals When Card Is in Customer's Possession

Parties: State Bank of India v. P.V. George

The Dispute & Facts:

An SBI account holder in Kerala received midnight SMS alerts showing ₹2,40,000 withdrawn across multiple ATM transactions in Brazil while his physical debit card remained safely in his possession in India. He immediately reported the cloning fraud to the branch. SBI refused to reimburse the loss, arguing that ATM withdrawals cannot occur without a PIN.

Judicial Holding:

The Kerala High Court held State Bank of India strictly liable to refund the unauthorised withdrawals with interest and costs. Distinguishing between customer fault and third-party skimming/system vulnerability, the Court ruled that when a customer promptly notifies the bank of impossible geographic transactions, the bank must protect the depositor's money under the RBI Zero Liability directive.

Judicial Relief / Binding Order₹2,40,000 Full Reversal + Statutory Interest & Litigation Costs
Statutory Authority CitedClauses 6, 8, 9 & 12 RBI Circular (6 July 2017)
What this means for your bank dispute: In card cloning, skimming, or unauthenticated international POS debits, physical possession of your card in India coupled with prompt reporting establishes Zero Liability.
Precedent #4 • Revision Petition No. 3333 of 2013, I (2021) CPJ 42 (NC) (NCDRC New Delhi)Order Dated 21 December 2020

Credit Card Issuer Cannot Demand Payment or Levy Interest on Unauthorised Fraudulent Swipes

Parties: HDFC Bank Ltd. v. Jesna Jose

The Dispute & Facts:

Multiple international POS transactions were executed on the complainant's credit card without her authorisation or pre-transaction OTP verification. Despite immediate dispute intimation, the bank demanded bill payment, levied finance charges, and damaged her credit profile.

Judicial Holding:

The National Consumer Disputes Redressal Commission (NCDRC) held that under the RBI Circular on Limiting Liability of Customers in Unauthorised Electronic Banking Transactions, the onus of proving that the cardholder intentionally compromised card security rests on the bank. Where a security breach occurs without customer fault, the bank is guilty of deficiency in service under Section 2(11) of the Consumer Protection Act if it refuses to reverse the charges.

Judicial Relief / Binding OrderFull Reversal of Disputed Card Charges + ₹40,000 Compensation + ₹5,000 Costs
Statutory Authority CitedClauses 6, 8, 9 & 12 RBI Circular (6 July 2017)
What this means for your bank dispute: If your credit card is billed for an unauthorised transaction, Paragraph 9(ii) of the RBI Circular forbids the bank from charging any interest or late fees on the disputed component.

15. Worked Case Study: Account Holder Recovers ₹1,42,000 Unauthorised IMPS/UPI Debits After Bank Refused 10-Day Shadow Credit

Illustrative Banking Recovery Case StudyBengaluru Savings Account • APK SMS-Forwarding Exploit

The Incident (14 August 2026): Siddharth Nair, a software engineer in Bengaluru, received a WhatsApp message with a fake electricity-disconnection APK file. Without his knowledge, background malware intercepted incoming SMS messages while he was asleep. Between 1:15 AM and 1:28 AM, three unauthorised IMPS and UPI transfers of ₹49,000, ₹48,000, and ₹45,000 (totalling ₹1,42,000) were debited from his private-sector savings account.

Prompt Reporting (Within 7 Hours — Day 1): At 8:10 AM the same morning, Siddharth saw the debit alerts, called the bank's 24x7 fraud hotline to block his mobile banking and UPI, registered NCRP Docket No. 22908260041298 on the 1930 Cyber Helpline, and submitted a written dispute letter at his home branch.

The Bank's Illegal Refusal (Day 14): Instead of crediting a shadow reversal within 10 working days under Paragraph 9 of the 6 July 2017 RBI Circular, the bank closed his ticket on Day 14 stating: "Transactions were completed using valid device binding and OTP; hence bank is not liable."

The Statutory Action: Siddharth engaged LegalRecovery.in (flat ₹999 fee—see our legal notice charges). An advocate served a 15-day statutory legal demand notice on the Bank's Principal Nodal Officer and Managing Director, citing Paragraphs 6(b), 9(i), and 12 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 and the Supreme Court's 2025 ruling in State Bank of India v. Pallabh Bhowmick—demanding the bank's server logs explaining how a new payee cooling-off period was bypassed at 1:15 AM.

The Outcome (Day 12 After Legal Notice):Faced with an imminent RBI Integrated Ombudsman (CMS) escalation and Consumer Commission filing where the bank could not justify how three midnight transfers to a newly added beneficiary bypassed velocity controls, the Bank's Nodal Cell reopened the claim and credited the full ₹1,42,000back to Siddharth's savings account, value-dated to 14 August 2026.

16. Banking Evidence Checklist: 6 Essential Records Before Serving a Zero-Liability Legal Notice

Under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 (BSA), electronic banking logs, SMS timestamps, and NCRP dockets are primary evidence before the RBI Ombudsman and Consumer Commissions. Assemble these 6 records:

1
Original Bank Debit SMS / Email Alert Screenshot:

Proving the exact date and timestamp when the bank first communicated the unauthorised transaction to you (fixing the start of the 3-working-day clock).

2
Proof of Reporting to Bank Within 3 (or 4–7) Working Days:

Bank complaint ticket number, SMS reply log, outbound call log to the 24x7 bank helpline, or stamped branch dispute letter.

3
1930 Cyber Helpline / NCRP Acknowledgement PDF:

14-digit NCRP complaint acknowledgement downloaded from cybercrime.gov.in showing the transaction UTRs reported for lien-marking.

4
Account / Credit Card Statement Showing 12-Digit UTR / RRN:

Official PDF statement highlighting each unauthorised debit, beneficiary account/VPA, and absence of 10-day shadow reversal.

5
Bank's Rejection Email or Unresolved Ticket Log:

Showing that the bank mechanically blamed you without providing forensic proof under Paragraph 12 or ignored your complaint past 10 working days.

6
Telecom Operator Call/SMS History (For SIM-Swap / Post-Call Debits):

Demonstrating either sudden SIM deactivation or proving that subsequent debits occurred after your first call to the bank helpline.

17. Honest Recovery Scope: What LegalRecovery Can and Cannot Do in Banking Fraud Disputes

✓ What We Do: Enforce Your Bank's Statutory Liability

We pursue your bank or card/wallet issuer when it breaches RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18—including refusing the mandatory 10-working-day shadow reversal, failing to block your account after you called the helpline, permitting high-velocity midnight debits or non-OTP international swipes, or rejecting a 3-day Zero Liability claim without discharging its Clause 12 burden of proof. Our advocate legal notice sets up rapid escalation to the RBI Integrated Ombudsman (CMS) and e-Jagriti Consumer Commission.

✕ What We Cannot Do: Trace Anonymous Fraudsters or Unfreeze Police LiensWe cannot trace anonymous Telegram/WhatsApp cyber criminals once funds have been withdrawn in cash from mule accounts, nor do we handle unfreezing bank accounts that have been debit-frozen by state cyber police cells due to incoming P2P crypto or gaming credits. Where you voluntarily transferred funds over days in an investment or task scam, bank liability under the 2017 circular does not apply unless the bank ignored a freeze request or the loss falls within the 2027 small-value compensation cap†.

18. Frequently Asked Questions: RBI Zero Liability, Shadow Reversal & Bank Refunds

Authoritative Answers Grounded in RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18, Supreme Court Rulings & the 2027 Framework

Within how many working days should shadow reversal be credited by the bank under RBI rules?↓
Under Paragraph 9(i) of RBI Circular No. RBI/2017-18/15 (DBR.No.Leg.BC.78/09.07.005/2017-18) dated 6 July 2017, the bank must credit (shadow reversal / provisional credit) the amount involved in the unauthorised electronic banking transaction to the customer's account within 10 working days from the date of notification by the customer, without waiting for the settlement of any insurance claim.
What is the time limit to report an unauthorised bank transaction for Zero Liability?↓
Under Paragraph 6(b) of the RBI Customer Liability Circular, if an unauthorised transaction occurs due to a third-party breach where the deficiency lies neither with the bank nor with the customer, you must notify the bank within 3 working days of receiving the transaction alert from the bank (excluding the date you received the alert) to qualify for 100% Zero Liability. If the fraud resulted from the bank's own contributory negligence or security failure under Paragraph 6(a), you have Zero Liability regardless of when you report it.
What is my maximum liability if I report an unauthorised transaction between 4 and 7 working days?↓
Under Paragraph 7(b) and Table 1 of the 6 July 2017 RBI Circular, if you report a third-party breach between 4 and 7 working days after receiving the bank's SMS/email communication, your maximum per-transaction liability is capped at the transaction value or the statutory ceiling—whichever is lower: ₹5,000 for Basic Savings Bank Deposit (BSBDA) accounts; ₹10,000 for regular Savings Accounts, Prepaid Wallets (PPIs), Credit Cards with limits up to ₹5 lakh, and MSME Current/OD accounts; and ₹25,000 for all other Current/Cash Credit/Overdraft accounts and Credit Cards with limits above ₹5 lakh.
Who bears the burden of proof in an unauthorised electronic banking transaction dispute?↓
Under Paragraph 12 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 (and reaffirmed under the 2027 Revised Framework), the burden of proving customer liability in case of unauthorised electronic banking transactions lies exclusively on the bank. The bank cannot reject your claim with a bare assertion that an OTP was used; it must produce verifiable technical logs proving customer negligence or deliberate credential sharing.
Why did the Supreme Court hold that State Bank of India must refund unauthorized withdrawals?↓
In State Bank of India v. Pallabh Bhowmick & Ors. (decided 3 January 2025), the Supreme Court upheld the Gauhati High Court judgment directing SBI to refund ₹94,204.80 siphoned after a customer was tricked into installing a fraudulent app during an online return inquiry. Because the customer notified SBI within 24 hours (within the 3-working-day window) and never voluntarily shared an OTP/MPIN to authorise those debits, the Supreme Court ruled that Clauses 8 and 9 of the 2017 RBI Circular mandate a full refund and banks must maintain robust fraud-detection systems.
Am I liable for transactions that happen after I have called the bank helpline to block my account or card?↓
Never. Even if you were tricked into sharing an OTP or PIN on an initial transaction, the second sentence of Paragraph 7(a)(i) of the RBI Circular explicitly mandates that 'any loss occurring after the reporting of the unauthorised transaction shall be borne by the bank.' Once you notify the bank via toll-free helpline, SMS block code, or portal, 100% of any subsequent debit is the bank's unconditional responsibility.
How does the 1 January 2027 RBI Fraudulent Transaction Framework change the 2017 Zero Liability rules?↓
While the 6 July 2017 circular protects victims of 'unauthorised' transactions (bank fault or third-party breaches without OTP sharing), the RBI Revised Framework for Fraudulent Electronic Banking Transactions (effective 1 January 2027†) expands protection to small-value social-engineering and scam-induced frauds up to ₹50,000. Bona fide individual victims who report to both their bank and 1930 / cybercrime.gov.in within 5 calendar days become eligible for a one-time lifetime compensation of 85% of net loss or ₹25,000, whichever is lower†.
Bank account ya UPI se binameri marzi paise kat gaye aur bank refund mana kar raha hai toh kya karein?↓
Agar aapke bank account, credit card ya UPI se bina OTP share kiye (jaise APK hack, SIM swap ya card cloning se) paise kate hain aur aapne 3 working days ke andar bank aur 1930 cyber helpline par complaint darj kara di hai, toh RBI ke 6 July 2017 Zero Liability Circular ke Paragraph 9 ke tahat bank ko 10 working days mein 100% rakam (Shadow Reversal) wapas karni hoti hai. Bank ke mana karne par aap advocate ke madhyam se Bank Nodal Officer ko 15-day Statutory Legal Notice bhejkar RBI Ombudsman (CMS) aur Consumer Court (e-Jagriti) mein dava kar sakte hain.

19. Primary RBI Circulars, Supreme Court Judgments & Official Regulatory References

  1. Reserve Bank of India (RBI) Circular No. RBI/2017-18/15 (DBR.No.Leg.BC.78/09.07.005/2017-18) dated 6 July 2017 — Customer Protection: Limiting Liability of Customers in Unauthorised Electronic Banking Transactions
  2. Reserve Bank of India Circular No. RBI/2018-19/101 (DPSS.CO.PD.No.1414/02.14.006/2018-19) dated 4 January 2019 — Customer Protection: Limiting Liability of Customers in Unauthorised Electronic Payment Transactions in Prepaid Payment Instruments (PPIs)
  3. Supreme Court of India — State Bank of India v. Pallabh Bhowmick & Ors., SLP (Civil) Diary No. 55621/2024 (Order dated 3 January 2025, upholding Gauhati High Court WA 282/2024)
  4. Bombay High Court (Division Bench) — Jaiprakash Kulkarni & Anr. v. The Banking Ombudsman & Bank of Baroda, Writ Petition No. 1150 of 2023 (2024 SCC OnLine Bom 1666)
  5. Reserve Bank – Integrated Ombudsman Scheme, 2021 (RB-IOS) & Complaint Management System (CMS) Portal
  6. Reserve Bank of India (Commercial Banks – Responsible Business Conduct) Amendment Directions, 2026 — Revised Framework for Fraudulent Electronic Banking Transactions (Effective 1 January 2027†)
  7. National Cyber Crime Reporting Portal (NCRP) & 1930 Citizen Financial Cyber Frauds Reporting System — Ministry of Home Affairs
  8. Bharatiya Sakshya Adhiniyam, 2023 (BSA) — Section 63 (Admissibility of Electronic Bank Statements, SMS Logs, Call Recordings & NCRP Dockets)

† Statutory verification status: Clauses 4 to 12 and Tables 1 & 2 of RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 (dated 6 July 2017) and the Supreme Court ruling in State Bank of India v. Pallabh Bhowmick (3 January 2025) are in active force as of November 2026. Provisions marked with † relate to the RBI Revised Framework for Fraudulent Electronic Banking Transactions scheduled to take effect on 1 January 2027.

Serve an RBI Zero-Liability Legal Demand Notice to Your Bank

RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 • Statutory Bank Demand Notice

Bank Refusing Your 10-Day Shadow Reversal or Unfairly Blaming You for Cyber Fraud?

Have a verified banking recovery advocate draft and serve a formal statutory legal demand notice on your bank's Nodal Officer, Managing Director, and Branch Manager. We invoke Clauses 6, 7, 9, and 12 of the RBI Customer Liability Circular and the Supreme Court's 2025 Pallabh Bhowmick precedent—demanding value-dated reversal before escalating to the RBI Integrated Ombudsman (CMS) and Consumer Commission.

✓ 24h Advocate Drafting•✓ Speed Post + Email•✓ Flat ₹999
Contextual Legal Library

Related Cheque Bounce, Banking Auto-Debit & Cyber Fraud Guides

View All Legal Notice Categories →
Gaming Wallet

Gaming App Wallet Balance Stuck After the Ban? Refunds

Statutory escalation path for real-money gaming wallet balances stuck post-ban: platform duties, unutilised deposit rights, and advocate notices.

Read Legal Guide
SEBI & Broker Dispute

Dispute With Your Broker? SEBI SCORES and SMART ODR Explained

Escalate unauthorized trades, forced square-offs, and stuck funds through SCORES 2.0 and the SMART ODR binding arbitration portal.

Read Legal Guide
Job Scam Fee

Paid a 'Registration Fee' for a Job That Didn't Exist? Recover It

Statutory recovery roadmap for fake job offer fees, placement agency registration frauds, 1930 bank freeze, and advocate notices.

Read Legal Guide
Task Scam

Telegram Task Scam Money Recovery: Reporting & Legal Options

Statutory escalation for Telegram task and review scams: 1930 NCRP reporting, mule account freeze, Section 503 BNSS, and bank liability.

Read Legal Guide
साइबर फ्रॉड रिफंड

साइबर फ्रॉड का पैसा वापस कैसे मिलेगा? बैंक की जिम्मेदारी

UPI या कार्ड फ्रॉड के बाद 1930, बैंक शिकायत और RBI के जीरो लायबिलिटी नियम — पैसा वापस पाने की पूरी प्रक्रिया हिंदी में।

Read Legal Guide
Bank Reversal Format

Wrong Account Money Transfer Refund Application (Format)

Ready application formats in English and Hindi to request reversal of money sent to a wrong account or UPI ID under Section 72 Contract Act.

Read Legal Guide
Contextual Legal Library

Related Cheque Bounce, Banking Auto-Debit & Cyber Fraud Guides

View All Legal Notice Categories →
Gaming Wallet

Gaming App Wallet Balance Stuck After the Ban? Refunds

Statutory escalation path for real-money gaming wallet balances stuck post-ban: platform duties, unutilised deposit rights, and advocate notices.

Read Legal Guide
SEBI & Broker Dispute

Dispute With Your Broker? SEBI SCORES and SMART ODR Explained

Escalate unauthorized trades, forced square-offs, and stuck funds through SCORES 2.0 and the SMART ODR binding arbitration portal.

Read Legal Guide
Job Scam Fee

Paid a 'Registration Fee' for a Job That Didn't Exist? Recover It

Statutory recovery roadmap for fake job offer fees, placement agency registration frauds, 1930 bank freeze, and advocate notices.

Read Legal Guide
Task Scam

Telegram Task Scam Money Recovery: Reporting & Legal Options

Statutory escalation for Telegram task and review scams: 1930 NCRP reporting, mule account freeze, Section 503 BNSS, and bank liability.

Read Legal Guide
साइबर फ्रॉड रिफंड

साइबर फ्रॉड का पैसा वापस कैसे मिलेगा? बैंक की जिम्मेदारी

UPI या कार्ड फ्रॉड के बाद 1930, बैंक शिकायत और RBI के जीरो लायबिलिटी नियम — पैसा वापस पाने की पूरी प्रक्रिया हिंदी में।

Read Legal Guide
Bank Reversal Format

Wrong Account Money Transfer Refund Application (Format)

Ready application formats in English and Hindi to request reversal of money sent to a wrong account or UPI ID under Section 72 Contract Act.

Read Legal Guide