- Practice
- About 14 min
- 5 practice questions
Unauthorised transactions: fault, reporting speed and liability
Decide who bears the loss when money leaves an account without the customer's consent, by asking whose fault it was and how quickly the customer reported, and compute the customer's share.
If something looks wrong, please tell us.
Unauthorised electronic transactions are a favourite scenario in grievance questions because they combine a story, a rule and a small sum. The rules come from the Reserve Bank's framework on customer protection, and the framework's exact time limits and ceilings can change, so this lesson teaches the reasoning and uses invented numbers marked 'suppose'. If an exam question gives a limit, use the one it gives.
Three questions that decide the case
- Whose fault was it? The bank's own deficiency, a breach somewhere else in the system (a third party), or the customer's negligence.
- How fast did the customer report? Prompt reporting protects the customer; delay can move more of the loss to the customer.
- How much was lost, and when? Money taken before the report and money taken after it are treated differently.
The pattern of liability
| Situation | Who bears the loss (general principle) |
|---|---|
| Bank's own deficiency (system fault, staff error) | The bank, whenever the customer reports |
| Third-party breach; neither bank nor customer at fault; customer reports within the time the framework allows | The bank; the customer's liability is nil |
| Same breach, but reported after that time | Customer's liability is limited, to the smaller of the transaction value and a ceiling the framework sets |
| Same breach, reported later still | As the bank's board-approved policy states |
| Customer's negligence (shared PIN, password or OTP) | The customer, for the losses before reporting; the bank, for losses after reporting |
Two ideas run through the whole table. First, reporting stops the customer's exposure: once a loss is reported, later unauthorised debits are the bank's. Second, negligence shifts the burden: a customer who hands over a PIN or one-time password has helped the fraud, so the earlier losses stay with the customer. A bank must also give the customer a way to report at any hour, send alerts for transactions, and, after a report, treat the matter seriously within the time the framework sets.
Worked examples
Example 1. Suppose ₹18,000 is taken from Meera's account after a data breach at an online merchant. She did nothing wrong and reported it the next day, which is within the time the framework allows. This is a third-party breach reported in time, so her liability is nil (₹0). The bank is expected to restore the ₹18,000 to her account and then investigate.
Example 2. Suppose Naveen shared his one-time password with a caller who claimed to be from the bank. Two debits followed: ₹14,000 before he reported the fraud and ₹10,000 after he reported it. The total loss is 14,000 + 10,000 = ₹24,000. Because of his negligence, he bears the ₹14,000 taken before the report. The bank bears the ₹10,000 taken after the report, since the report ended his exposure.
Example 3. Suppose, using an invented ceiling of ₹5,000, a third-party fraud is reported late and the framework limits the customer to the smaller of the transaction value and the ceiling. If the fraudulent transaction is ₹3,200, liability is the smaller of 3,200 and 5,000, which is ₹3,200. If it is ₹7,500, liability is the smaller of 7,500 and 5,000, which is ₹5,000, and the bank bears the other 7,500 - 5,000 = ₹2,500.
Bank's fault: customer pays nothing. Third party, reported in time: customer pays nothing. Customer's negligence: customer pays until the report. Always report at once.
Traps
A common trap says the customer is always liable because the transaction used the customer's own card. That is false: fault decides. Another says the bank is liable for everything even after the customer's negligence; that is also false. A third mixes up the dates: the amount taken after reporting is never charged to a customer who reported. Read for the words bank's deficiency, third party, shared and reported before choosing.
Key takeaways. Ask whose fault, how fast, and how much. The bank bears its own deficiency; third-party breaches reported in time cost the customer nothing; negligence leaves earlier losses with the customer; reporting ends the customer's exposure.
Check your understanding
-
1. A customer shares an OTP with a stranger and ₹9,000 is debited before she reports it. A further ₹6,000 is debited after she reports it. How much does she bear under the negligence principle?
- ₹9,000
- ₹15,000
- ₹6,000
- Nothing at all
Show answer
Answer: A. Her negligence leaves the losses before reporting with her: ₹9,000. The ₹6,000 taken after the report is the bank's. The total loss is 9,000 + 6,000 = ₹15,000.
-
2. An unauthorised debit happens because of a fault in the bank's own system. The customer's liability is:
- Shared half and half with the bank
- Limited to a fixed ceiling
- Nil, whenever it is reported
- Whatever the bank decides
Show answer
Answer: C. Where the deficiency is the bank's, the customer is not made to bear the loss, however long the report took. Half-and-half sharing is not the principle.
-
3. Which action best protects a customer who finds an unexpected debit?
- Wait a few weeks to see whether it reverses
- Report to the bank at once and block the card
- Post about it online before telling the bank
- Change only the email address on the account
Show answer
Answer: B. Prompt reporting stops the customer's exposure and starts the bank's investigation. Waiting can move more of the loss to the customer.
-
4. Suppose the ceiling for late-reported third-party fraud is ₹5,000. A ₹7,500 fraudulent transaction is reported late. The customer's liability is:
- ₹2,500
- ₹7,500
- ₹12,500
- ₹5,000
Show answer
Answer: D. Liability is the smaller of the transaction value and the ceiling: smaller of 7,500 and 5,000 = ₹5,000. The bank bears the remaining ₹2,500.
-
5. Which statement is true?
- A customer who is careless is never liable
- The bank is liable only if the customer reports in a year
- A customer is always liable if the card was used
- Reporting ends the customer's exposure to later debits
Show answer
Answer: D. After a report, later unauthorised debits are the bank's. The other statements ignore fault and timing, which are what decide liability.
Sign in to keep track of the lessons you finish.