Debit Card Skimming or ATM Fraud: Evidence Before Complaint
An ATM and debit-card dispute guide distinguishing cash-not-dispensed failures, unauthorised withdrawals, skimming, card capture and merchant-card fraud.
For broader context, see the NRI, RBI and International Transactions Hub.
A failed ATM transaction and an unauthorised cash withdrawal are different disputes with different evidence and liability analysis.
If the account is debited but cash is not dispensed, RBI’s failed-transaction framework requires reversal within T+5 days and ₹100 per day compensation beyond that timeline.
An unauthorised withdrawal should be reported immediately under RBI’s unauthorised-transaction framework.
Skimming can involve copied card data, PIN compromise, tampered devices or card-not-present misuse after compromise.
The customer should record the ATM ID, location, time, amount, SMS alert and whether the card remained in possession.
What the customer or business should understand
- If the account is debited but cash is not dispensed, RBI’s failed-transaction framework requires reversal within T+5 days and ₹100 per day compensation beyond that timeline.
- An unauthorised withdrawal should be reported immediately under RBI’s unauthorised-transaction framework.
- Skimming can involve copied card data, PIN compromise, tampered devices or card-not-present misuse after compromise.
- The customer should record the ATM ID, location, time, amount, SMS alert and whether the card remained in possession.
- Do not revisit a suspicious ATM alone to confront anyone or insert the card again.
For the connected rule, example or next step, see Loan Recovery Harassment: Evidence and Complaint Route.
The five-point review
| Check | What to examine |
|---|---|
| Incident | Cash not dispensed, partial cash, unauthorised withdrawal or card capture. |
| ATM | ID, bank, location and time. |
| Card | Possession, block time and other transactions. |
| Evidence | SMS, statement, photographs and complaint. |
| Rule | T+5 failed transaction or unauthorised liability framework. |
For the connected rule, example or next step, see Credit-Card Fraud: RBI Customer-Liability Rules in Plain English.
Practical example
A customer attempts to withdraw ₹10,000, receives no cash and sees an account debit. This is a failed ATM transaction. A separate ₹10,000 withdrawal at midnight when the card is at home is an unauthorised transaction requiring fraud containment.
How to apply the framework
Photograph the ATM ID and error screen only if safe. Do not photograph or expose the PIN.
Review nearby transactions because a compromised card can be used across channels.
Dispute workflow
Classify the problem before choosing the remedy
Identify the regulated entity, transaction or loan account, date, amount, contractual document and exact failure. Review incident, atm and card together. A failed transaction, authorised mistake, unauthorised fraud, merchant dispute, credit-report error and lawful account freeze require different remedies.
Create one written chronology
Record the event, alert, discovery, first report, complaint number, response and financial impact in date order. Attach only the documents that prove each step. Phone calls can stop urgent harm, but a written acknowledgement creates the escalation record.
Escalate to the correct authority
Start with the bank, card issuer, lender, credit institution, app or other regulated entity responsible for the service. Use cybercrime or law-enforcement channels for suspected fraud. Use RBI CMS only after the regulated entity process satisfies the Scheme’s timing or rejection condition and the issue is within Ombudsman scope.
Implementation checkpoint
Before treating the case as closed, verify the actual bank statement, loan ledger, credit report, account status or merchant refund rather than relying only on a ticket message. Record who confirmed the financial outcome, the date, remaining open amount and the next escalation deadline. This final check prevents a complaint from being marked resolved while the money, lien, overdue status or credit record remains unchanged.
Action checklist
- Block the card if compromise is suspected.
- Record ATM ID and exact time.
- Raise a bank complaint immediately.
- Preserve statement and SMS.
- Report unauthorised withdrawals as fraud.
- Track T+5 reversal and compensation for cash-not-dispensed cases.
Evidence to keep
- ATM receipt/error screen
- ATM ID/location
- Statement and alerts
- Card-block timestamp
- Bank complaint and reversal
Warning signs
- Waiting several days before reporting fraud
- Sharing PIN with ‘ATM support’
- Calling a number pasted on the machine
- Treating every ATM debit as skimming
- No record of ATM ID
Finin2min takeaway
Banking disputes are resolved through classification, speed, written evidence and the correct escalation route. No legitimate bank, regulator or recovery process requires disclosure of an OTP, UPI PIN or remote-control access.
Frequently Asked Questions
Source and review trail
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.
- Primary category
- Business Case Studies & Corporate Strategy
- Official starting point
- www.mca.gov.in