Root Cause Diagnosis
The billing descriptor is not generated by your card issuer. The merchant’s acquirer or payment aggregator sets it at onboarding and sends it in the clearing record (card acceptor name and city in ISO 8583 DE 43, merchant category code in DE 18). The mismatch appears when the merchant bills under a parent or legal entity name, an aggregator or sub-merchant prefix, or an app-store or wallet intermediary, so the statement text differs from the brand you know. The issuer displays whatever the acquirer sent, so a descriptor mismatch is rarely a valid chargeback reason on its own. A dispute succeeds only when the underlying transaction is unauthorised, duplicated, billed at the wrong amount, a cancelled recurring charge, or for goods or services not received.
Quick Fix
- Open the entry in your issuer app and note the date, amount, currency, descriptor string, city and any reference number.
- Search your email and SMS for the same amount and date. Also check app-store subscription history and the tokenized-card list in your issuer app.
- If nothing matches, restrict the card first, then dispute. Look for Cards > Manage > Usage controls and switch off online and international use. Menu labels vary by issuer. Then use Dispute / Report transaction on the entry.
Use this text for the dispute form or call:
Card ending XXXX. Unrecognised transaction on DD-MMM-YYYY, INR/USD <amount>,
descriptor "<exact string>", city "<city>". No purchase, subscription or
token on my side matches this entry. Please block further charges from this
merchant, issue provisional credit, and share the acquirer name, RRN/ARN and
authorisation code. Reporting date/time: <date, time>.
Step-by-Step Resolution
1. Capture the transaction record
| Field | Where to find it | Why it matters |
|---|---|---|
| Transaction date vs posting date | Statement | Pre-authorisations and delayed settlement differ by days |
| Amount and currency | Statement, SMS alert | Foreign amounts include conversion markup and GST |
| Descriptor, city, country | Statement | Search key for steps 2 and 7 |
| MCC | Issuer app detail view, or ask the issuer | Reveals the merchant category |
| Auth code, RRN/ARN | Issuer on request | Needed for retrieval requests and chargebacks |
| Alert timestamp | SMS or email | Starts your reporting clock (step 5) |
2. Decode the descriptor
- Strip any aggregator prefix. Common intermediaries are Razorpay, PayU, Cashfree, CCAvenue, BillDesk, Stripe and PayPal. The text after the prefix is usually the sub-merchant.
- Search the exact string plus the city. Brands often bill under a registered legal entity (for example, a “Technologies Pvt Ltd” name).
- Take the GSTIN from the merchant’s invoice or website footer. Check the legal and trade names at gst.gov.in > Search Taxpayer. Company records are at mca.gov.in > MCA Services > View Company/LLP Master Data.
- Check the issuer app’s token or “cards saved on merchants” list for the merchant that holds a token for your card.
- Ask add-on cardholders to check their own usage.
3. Classify, then pick the dispute path
| Finding | Action |
|---|---|
| You recognise it, only the name looks odd | Do not dispute. Ask the merchant to fix the descriptor (step 7) |
| You recognise the merchant, but the amount is wrong, it was charged twice, or you cancelled a subscription | Billing dispute. Contact the merchant first, then the issuer |
| Goods or services not received, or a refund not credited | Billing dispute with proof of the order and any refund promise |
| Cannot link it to any purchase | Report as unrecognised or fraudulent immediately (steps 4 to 6) |
Typical network reason categories the issuer maps your claim to:
| Claim | Visa | Mastercard |
|---|---|---|
| Card-absent fraud, no authorisation | 10.4 | 4837 |
| Duplicate processing | 12.6.1 | 4834 |
| Cancelled recurring | 13.2 | 4841 |
| Services not received | 13.1 | 4853 |
| Credit not processed | 13.6 | 4853 |
RuPay disputes are raised by the issuer through NPCI’s dispute system.
4. Secure the instrument (unrecognised charges only)
- Block or hotlist the card if you suspect compromise, and request reissue.
- Remove stored tokens and delete saved cards in merchant apps.
- Do not share an OTP, CVV or PIN with anyone claiming to be support. Sharing credentials is classed as customer negligence under RBI frameworks.
5. Know which RBI liability regime applies
Transactions before 1 January 2027 fall under the earlier regime, based on the 6 July 2017 circular and now consolidated in RBI’s Responsible Business Conduct Directions:
- Reporting within 3 working days of the alert gives zero customer liability in third-party-breach cases.
- Reporting in 4 to 7 working days caps liability. For credit cards the cap is ₹10,000 for limits up to ₹5 lakh and ₹25,000 above that.
- After 7 working days, the issuer’s board-approved policy applies.
- The issuer must shadow-reverse within 10 working days of your report and resolve the complaint within 90 days.
- Zero liability also applies where the fault is the bank’s, whatever the reporting time.
Transactions on or after 1 January 2027 fall under the revised regime:
- The Third Amendment Directions of 24 June 2026 replace the old framework and apply to electronic banking transactions on or after 1 January 2027.
- The scope now includes transactions where a third party used fraudulently obtained credentials, and transactions a customer approved under coercion or duress.
- The bank must establish customer liability to deny relief, and for credit card fraud must give provisional credit within five calendar days of notification.
- Domestic fraud complaints must be resolved within 45 calendar days and cross-border ones within 60. Another summary reports 30 calendar days for the liability determination, so confirm both timelines in your issuer’s published policy.
- Small-value compensation is 85% of net loss up to ₹25,000. It requires a loss of up to ₹50,000, reporting to both the bank and the National Cyber Crime Reporting Portal or helpline 1930 within five calendar days, and it is available once per customer.
For a fraudulent charge, also report at cybercrime.gov.in or on 1930, and keep the acknowledgement number.
6. File the dispute and keep a paper trail
- Raise it in the issuer app and note the complaint or SR number.
- Call customer care and quote that number.
- Email the issuer’s grievance address (listed on its website) with the text from the Quick Fix section plus attachments: the statement page, alert SMS screenshot, merchant correspondence, and cancellation or non-receipt proof.
- Ask the issuer to raise a retrieval or copy request to get the merchant’s transaction record and the legal entity behind the charge.
- Pay the undisputed part of the bill by the due date. Ask in writing that the disputed amount be excluded from interest and late fees.
7. Contact the merchant (recognised-merchant disputes)
Request in writing: the invoice with GSTIN, the transaction or order ID, the acquirer or aggregator name, and confirmation of the legal entity billed. To fix a descriptor, the merchant must ask its acquirer or aggregator to update the soft descriptor for its merchant ID. The change applies to future transactions only. For subscription charges, also ask for the mandate or registration record.
8. Track the clock
- Check your issuer’s terms and conditions for the window to dispute. Many issuers want disputes within 30 to 60 days of the statement date.
- Visa and Mastercard chargeback windows are generally around 120 days from the transaction or expected delivery date, but your issuer’s internal deadline is shorter.
- Check each statement for the provisional credit and the final outcome letter.
9. Escalate in order
- Issuer customer care.
- Nodal officer, then Principal Nodal Officer (escalation matrix on the issuer’s website).
- RBI Integrated Ombudsman at cms.rbi.org.in, after the issuer rejects the complaint or does not reply within 30 days. File within one year of the issuer’s reply. RBI’s contact centre is 14448.
- Consumer forum via e-Daakhil, or National Consumer Helpline 1915.
Why This Fails for Some Users
- Descriptor mismatch is not itself a billing error. If the merchant shows it delivered the service, the issuer rejects the chargeback and re-bills the amount, possibly with interest from the original date.
- Late reporting. Missing the issuer’s window, or the 3 or 5 day reporting thresholds, weakens or removes zero-liability protection.
- Authenticated transactions. A charge confirmed with an OTP or 3-D Secure is treated as customer-authorised. A fraud claim then needs evidence such as a SIM swap or phishing. Courts and RBI frameworks put the burden of proving negligence on the bank, but expect the issuer to ask for details.
- International merchants may not trigger an OTP. A foreign card-not-present charge without an OTP is not by itself proof of fraud, though rules here have been tightening.
- Recurring charges. Cancelling at the merchant without proof of the date weakens a cancelled-recurring dispute. Under RBI’s e-mandate framework, recurring debits need a pre-debit notification at least 24 hours before. A missing notification is a valid ground. Higher no-AFA limits apply to some categories such as mutual funds, insurance premiums and card bill payments.
- Holds and delayed settlement. Hotel, fuel and car-rental pre-authorisations settle later at a different date or amount. These are not duplicates.
- Foreign currency charges. The merchant’s quoted amount, dynamic currency conversion, markup and GST on forex markup explain INR amounts that look wrong.
- Intermediary names. App stores, wallet top-ups, aggregators and UPI-on-credit-card payments can show the intermediary instead of the shop.
- Tokens and add-on cards. Forgotten tokenized cards and family add-on usage are the most common “unrecognised” cases.
- Issuer type. The revised liability directions amend the commercial banks’ rules. NBFC-issued cards may follow different directions. Confirm which regime your issuer is under.
- Descriptor fixes are merchant-side. An issuer cannot rewrite the descriptor. Only the acquirer’s merchant record can change it, and only for future transactions.
This guide is general information, not legal or financial advice. Check your issuer’s current terms and the latest RBI directions before relying on any timeline.