- If it's an unauthorized transaction: Call the card issuer's 24x7 helpline or block the card in-app immediately
- Follow up with a written complaint via net banking, email, or the app within the same day
- Note the complaint reference number
- If it's a billing error or non-delivery: Raise a dispute through the "Report Transaction" or "Dispute" option in your card's app or net banking portal
- Attach evidence: order confirmation, delivery tracking, merchant communication
- If the online dispute option isn't available: Send a written email to the bank's customer care with your card's last 4 digits, transaction date, amount, and reason
- Request an acknowledgment with a complaint or reference number
- If the bank doesn't resolve it within 90 days: Escalate to the Banking Ombudsman via the RBI's CMS portal
- Keep all correspondence as evidence for the ombudsman complaint
← Full guide: How to Dispute a Wrong Credit Card Charge in India
How to Report and Dispute the Charge
Report and Dispute the Charge. Check the cause, evidence to keep, exact recovery steps, and escalation. Based on How to Dispute a Wrong Credit Card Charge.
Start here
If it's an unauthorized transaction: Call the card issuer's 24x7 helpline or block the card in-app immediately. Follow up with a written complaint via net banking, email, or the app within the same day.
What applies to this exact problem
Check these first
- Reconcile the final balance first; closure paperwork cannot fix an account that is not actually at zero.
- Treat the NOC, returned originals, registered security release, and bureau update as separate closure jobs.
- Verify each external record independently instead of assuming one closure letter updates everything.
Fix it in this order
- Reconcile the final balance first; closure paperwork cannot fix an account that is not actually at zero.
- Treat the NOC, returned originals, registered security release, and bureau update as separate closure jobs.
- Freeze the transaction record: amount, date, merchant/payment channel, issuer reference, UTR/RRN or transaction ID.
- Check the card ledger, current outstanding, available limit, and payment/refund history. A bank debit or merchant message alone is not enough.
- Ask the payment channel or merchant for the final status in writing: successful, failed, pending, reversed, or refunded.
- If the bill due date is close, contact the issuer before the deadline and ask how to protect the account while the first transaction is traced.
- After the issue is corrected, inspect the next statement for duplicate credit, interest, late fee, or an incorrect value date.
Build the proof pack
- Issuer statement and current outstanding
- Payment/refund reference and bank debit/credit proof
- Merchant or payment-channel confirmation
- Complaint/ticket number and written response
Avoid making the case harder
- Paying repeatedly without preserving the first reference
- Assuming a merchant refund means the card issuer has posted it
- Ignoring the due date while a dispute is open
How you know it is really fixed
- The lender ledger is closed, required originals are reconciled, and any applicable security record is released.
- A fresh credit/registry record no longer contradicts the closure evidence.
If it is still not fixed
- Issuer grievance officer or nodal officer
- Payment-system complaint route where relevant
- RBI CMS for an eligible unresolved complaint against a regulated entity
Official sources from the full guide
Need the complete context?
This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.