A merchant dashboard saying “refunded” is not the same as a posted card credit. Ask for the refund date and trace/reference information available from the merchant/acquirer. Then give that information to the issuer if the credit does not appear.
Use the RBI refund timeline logic
The RBI credit-card FAQ distinguishes refunds received before bill generation, after bill generation but before the cardholder pays, and after the bill has already been paid. That timing affects how the refund is adjusted and whether the cardholder must request credit to a bank account in some overpayment situations.
| Situation | Owner of next trace |
|---|---|
| Merchant cannot prove refund initiation | Merchant |
| Merchant has valid refund trace/reference | Issuer/acquirer network trace |
| Refund posted but statement balance still confusing | Issuer ledger reconciliation |
| You already paid and refund creates credit balance | Check issuer/RBI treatment and request transfer where applicable |
Keep paying the undisputed amount
A pending refund does not automatically suspend the rest of the card bill. Unless the issuer gives written instructions otherwise, pay the undisputed amount due and continue the trace separately. This reduces the risk of creating a late-payment problem while arguing about a merchant credit.
Create a transaction chronology
Purchase date → cancellation date → merchant refund initiation → refund reference → statement generation → your payment → issuer complaint. Put the amount next to every event. This immediately shows whether the dispute is “refund never initiated” or “refund initiated but not posted”.
Escalate after the issuer has something traceable
Use the issuer’s grievance channel with the refund reference and timeline. If an eligible unresolved service complaint remains, use the current RBI CMS. Decision rule: do not bounce between merchant and bank with screenshots; identify the first system that cannot prove the refund’s next step.