Credit Card Chargeback: How to Dispute Failed, Duplicate or Fraudulent Charges
A card-dispute workflow distinguishing merchant refund, billing error, failed service, duplicate charge, unauthorised transaction and network chargeback evidence.
A chargeback is an evidence-led issuer process, not an automatic refund button and not a substitute for reporting card fraud immediately.
First classify the dispute: unauthorised use, duplicate billing, cancelled service, non-delivery, defective service, failed refund or cash-withdrawal issue.
Unauthorised transactions should be reported immediately under the RBI customer-liability framework rather than waiting for merchant discussion.
Merchant disputes normally require invoice, cancellation, delivery and correspondence evidence.
Card issuers must operate grievance channels and explain billing and refund treatment under the card directions.
What the customer or business should understand
- First classify the dispute: unauthorised use, duplicate billing, cancelled service, non-delivery, defective service, failed refund or cash-withdrawal issue.
- Unauthorised transactions should be reported immediately under the RBI customer-liability framework rather than waiting for merchant discussion.
- Merchant disputes normally require invoice, cancellation, delivery and correspondence evidence.
- Card issuers must operate grievance channels and explain billing and refund treatment under the card directions.
- If the issuer does not respond within thirty days or gives an unsatisfactory response, the RBI Ombudsman route may be available subject to eligibility.
The five-point review
| Check | What to examine |
|---|---|
| Nature | Fraud, duplicate, non-delivery, cancellation or refund. |
| Timeline | Transaction, promised delivery/refund and complaint dates. |
| Merchant | Order, invoice, cancellation and response. |
| Issuer | Dispute form, temporary credit and document request. |
| Escalation | Issuer grievance and RBI CMS eligibility. |
Practical example
A hotel agrees in writing to cancel a booking but the charge remains. The cardholder should provide the booking terms, cancellation confirmation, statement and merchant correspondence. This is different from an unknown fraudulent card transaction.
How to apply the framework
Do not describe every dissatisfaction as fraud. Accurate classification helps the issuer apply the correct dispute reason and evidence window.
Track whether any temporary credit is provisional. Continue monitoring the statement until the case is finally closed.
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 nature, timeline and merchant 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
- Notify the issuer promptly.
- Classify the dispute accurately.
- Contact the merchant where safe and relevant.
- Submit complete documents together.
- Track temporary and final credit.
- Escalate with the full complaint history.
Evidence to keep
- Card statement
- Order and invoice
- Cancellation/refund confirmation
- Merchant communication
- Issuer dispute acknowledgement and decision
Warning signs
- Waiting beyond the dispute window
- Claiming non-delivery despite proof of receipt
- Cancelling the card but not disputing the transaction
- Spending temporary credit as final
- No merchant evidence
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.