Enter your facts
Your result
Enter the facts and calculate. The result appears here.
Map reporting delay and cause of an unauthorised electronic banking transaction to the RBI zero/limited-liability framework.
Enter the facts and calculate. The result appears here.
Map reporting delay and cause of an unauthorised electronic banking transaction to the RBI zero/limited-liability framework.
The RBI customer-liability framework is intentionally fact-sensitive. The most important first branch is who caused the loss: bank deficiency, customer negligence, or a third-party breach where neither bank nor customer is at fault.
For a qualifying third-party breach, reporting within three working days is a zero-liability band; reporting in four to seven working days can create limited liability subject to specified caps. Beyond seven working days, the bank’s Board-approved policy becomes important.
Where the customer caused the loss by sharing credentials or otherwise acting negligently, this checker does not manufacture a simple cap. RBI’s framework places the loss up to reporting on the customer, while loss after reporting is borne by the bank.
Separate process protections matter too: RBI’s circular provides for a shadow reversal within 10 working days of notification and complaint resolution within the prescribed framework, not exceeding 90 days.
Every field below changes the result. They are listed exactly as the form asks for them.
| Field | Type | What it controls |
|---|---|---|
| Unauthorised transaction amount | Number | |
| Cause category | Choice | 3 options: Third-party breach; customer not at fault; Bank negligence / deficiency; Customer negligence / credential sharing |
| Working days taken to report after bank communication | Number | |
| Account / card class for 4–7 day cap | Choice | 3 options: BSBD account — ₹5,000 cap bucket; ₹10,000 bucket — other savings accounts; PPI/gift cards; specified MSME/individual current/CC/OD; credit card limit up to ₹5 lakh; ₹25,000 bucket — other current/CC/OD; credit card limit above ₹5 lakh |
Liability depends on cause + working-day reporting band; 4–7 day cases use the lower of transaction value and the RBI class-specific cap.
The engine validates required values before calculating and rejects impossible combinations instead of converting them to zero silently. Dates, thresholds and category switches that drive the result remain visible to the user.
The logic on this page is built from the instrument(s) below. Where a rule did not clearly cover a scenario, that scenario is excluded rather than estimated.
The most common error in regulated calculations is not arithmetic; it is putting the facts into the wrong legal or product category. Check the transaction, entity, holding, policy or taxpayer classification before relying on the number.
Keep statements, acknowledgements, invoices, policy schedules, complaint IDs, tax workings or orders that support the inputs. A number without an evidence trail is difficult to defend in a complaint, return, claim or review.
Rules can change. This page records a source-check date, not a fabricated professional review date. If the event belongs to an older period, confirm that the rule version used here applies to that period.
No. Cause and reporting delay matter, and customer-negligence cases are treated differently.
The RBI reporting bands are expressed in working days.
That is an evidentiary dispute. The calculator cannot decide authentication facts; preserve alerts, complaint acknowledgements and device/account records.
The RBI framework refers the liability to the bank’s Board-approved policy for that band.
No. A failed transaction and an unauthorised/fraudulent transaction are different problems.
Source links below are the authority trail used to design the current rule logic. They remain more important than a generic secondary explainer.
Source checked: 14 August 2026. This denotes source verification for the package, not CA/legal review or approval of the individual case.
These cover adjacent decisions. Each owns a different question, so use the one that matches your actual event.
This calculator is published for general information and educational purposes only. It is not legal, tax, accounting or investment advice, is not personalised to your circumstances, and is not a substitute for reading the governing instrument or taking professional advice on your facts. Finin2min records a source-check date, which denotes verification of the authority trail and not a professional review or approval of any individual case.
Scope: Computes interest on delayed GST tax payment under Section 50 of the CGST Act.
Review status: reviewed and approved by CA Nikhil Gupta on 19 July 2026.
Background, worked examples and the rules behind these numbers.