An unfamiliar line on a credit-card statement can be alarming. Sometimes it is a merchant’s legal name, a delayed subscription or an add-on card purchase. Sometimes it really is an unauthorised transaction. The correct response is to verify quickly without exposing further card details, then notify the issuer when the charge cannot be explained.
This guide distinguishes three situations: an unfamiliar description, a merchant disagreement and a genuinely unauthorised payment. The steps are practical, but the bank’s current complaint process and the applicable rules determine the outcome of an individual case.
First, check whether the charge is familiar under another name
Compare amount and time with recent orders, household card usage, subscriptions and digital-wallet receipts. A payment aggregator may appear as the billing descriptor rather than the shop. Also look for authorisation holds that later disappear or adjust to the final amount.
That initial check should be brief. If there is any sign that the card was used without your permission, do not delay reporting while searching every old receipt. A small unknown transaction may be a test charge before larger attempts.
Block the card and notify the issuer when fraud is suspected
Use the bank’s authenticated app, the official website or its verified helpline to block the card and raise a report. Tell the issuer the exact transaction date, amount and merchant descriptor. Ask whether a temporary freeze, permanent block and replacement card are required.
Record the complaint reference, time and channel. Avoid responding to callers who claim they can “cancel the fraud” by taking an OTP, UPI PIN or remote access to your phone. Never share full card details in a public social-media complaint.
Why reporting speed matters
The RBI’s framework on unauthorised electronic banking transactions links customer liability to the cause of the event and how promptly the bank was informed. That is why immediate notification is important, even before a full investigation determines how the transaction occurred.
Do not assume every unauthorised debit has the same refund schedule or liability result. A bank-caused deficiency, a third-party breach and a loss following disclosure of credentials can be assessed differently. Preserve evidence of your earliest report so any review can establish when you told the issuer.
Fraud, failed delivery and merchant disputes are different
A merchant dispute might involve an item not delivered, an incorrect amount charged or a promised refund not processed. Start by collecting order confirmation, shipping information and merchant correspondence. The bank may request these items under its dispute or chargeback process.
A fraudulent transaction, by contrast, is a payment you did not authorise. State that clearly if it is true, rather than mixing the report with a complaint about product quality. Misclassifying an ordinary shopping disagreement as fraud can make resolution slower and confuse the supporting evidence.
What documents should you keep?
- A screenshot of the unrecognised entry with date and amount.
- The complaint or dispute reference from your bank.
- Any block/replacement confirmation and relevant transaction alerts.
- Order receipts or merchant correspondence if the charge relates to a purchase.
- Dates of follow-ups, written responses and any provisional credits.
Keep copies securely. Do not email full card credentials or identity documents unless the issuer requires a specific secure channel. Review replacement-card subscriptions and recurring transactions after the incident to prevent accidental service disruption.
What happens while the bank investigates?
The bank may ask questions about whether the card was in your possession, whether an OTP was received and whether you recognise the device or merchant. Answer accurately. A temporary credit or a held charge does not necessarily mean the investigation has ended; confirm the final written outcome and whether any amount is still payable.
The RBI credit-card directions contain requirements around handling disputed and fraud-related charges. Read the current issuer policies for your card and follow any time limits communicated for providing evidence.
If the first complaint is not resolved
Use the issuer’s formal grievance escalation route and refer to your original case number. Ask for a written explanation if a dispute is rejected. If the complaint remains unresolved, consult the current RBI-integrated ombudsman process and eligibility conditions on the official RBI website rather than a third-party “refund agent”.
Keep pursuing genuine questions, but avoid opening unrelated tickets for the same event without linking the earlier references. A clear chronological record is often more useful than multiple unconnected messages.
Prevention after the incident
Enable alerts for all transactions, consider transaction controls available in the bank app and review statements weekly. Check browser extensions, device updates and saved cards on merchant sites. If a suspicious call started the problem, read our guide to phishing and vishing and change exposed passwords through trusted channels.
For identifying ordinary charges and statement details, our billing-cycle guide helps explain why postings and payment dates can differ.
Frequently asked questions
Should I wait for the monthly statement?
No. Report a suspected unauthorised transaction promptly when you discover it.
Does blocking the card automatically refund a payment?
No. Blocking helps prevent further use; a dispute or unauthorised-transaction claim follows a separate investigation.
Can I dispute a charge after contacting the merchant?
Depending on the issue, the issuer may allow a dispute with supporting evidence. Follow its stated steps and deadlines.
Bottom line
Move quickly, use official support channels and keep careful records. Checking a merchant descriptor is sensible, but protecting your account and reporting genuine fraud matter much more than waiting to be certain of every detail.
