← Full guide: Credit Card Chargeback for Non-Delivery: Evidence and Timeline

Build the non-delivery case before the dispute window closes

Build the non-delivery case before the dispute window closes. Check the cause, evidence to keep, recovery steps, and escalation.

Start here

A strong chargeback file proves three things: you paid, the promised delivery did not occur, and you tried to resolve the matter with the merchant. The exact card-network and issuer process can vary, so dates matter.

What applies to this exact problem

A strong chargeback file proves three things: you paid, the promised delivery did not occur, and you tried to resolve the matter with the merchant. The exact card-network and issuer process can vary, so dates matter.

Strip away the marketing

For this case, the answer can change when transaction date and merchant descriptor, promised delivery date or service date, merchant cancellation, refund or non-response history. Use the dispute reason that matches the facts. Non-delivery is different from unauthorised use, defective goods and a promised refund that never posted.

Verify the moving parts

Control point

Transaction date and merchant descriptor.

Check first

Promised delivery date or service date.

Confirm in writing

Merchant cancellation, refund or non-response history.

Create an audit trail

Keep order confirmation and invoice, tracking page or written proof of non-delivery, emails or chats requesting delivery or refund, issuer dispute reference and submitted documents in one folder for this case. Name files with dates and retain original PDFs where possible.

RecordUse it to verifyWhy keep it
Order confirmation and invoiceTransaction date and merchant descriptorCreates a dated record another reviewer can verify.
Tracking page or written proof of non-deliveryPromised delivery date or service dateLets you challenge the exact field, charge, date or obligation.
Emails or chats requesting delivery or refundMerchant cancellation, refund or non-response historyProtects the decision if a portal, account screen or verbal explanation changes.
Issuer dispute reference and submitted documentsTransaction date and merchant descriptorSeparates a written fact from a sales statement.

A crisp action path

  1. Pin down the first controlling fact: transaction date and merchant descriptor.
  2. Reconcile it against order confirmation and invoice and tracking page or written proof of non-delivery.
  3. Test the decision under one realistic adverse case instead of assuming the best outcome.
  4. Record dates, reference numbers and the institution responsible for the next step.
  5. Escalate only the unresolved point; do not restart the case with a vague complaint.

Red flags worth pausing for

Pause before the next irreversible step if you wait for the merchant indefinitely while the dispute window runs, the claim says 'fraud' when you actually authorised the purchase, you submit cropped screenshots that omit dates or merchant identity.

  • You wait for the merchant indefinitely while the dispute window runs.
  • The claim says 'fraud' when you actually authorised the purchase.
  • You submit cropped screenshots that omit dates or merchant identity.

Check these first

  • State the exact expected result and the exact result you have now.
  • Find the official record that owns the result and compare it with your evidence.
  • Change one thing at a time, then verify the final state before moving on.

Fix it in this order

  1. State the exact expected result and the exact result you have now.
  2. Find the official record that owns the result and compare it with your evidence.
  3. Freeze the transaction record: amount, date, merchant/payment channel, issuer reference, UTR/RRN or transaction ID.
  4. Check the card ledger, current outstanding, available limit, and payment/refund history. A bank debit or merchant message alone is not enough.
  5. Ask the payment channel or merchant for the final status in writing: successful, failed, pending, reversed, or refunded.
  6. 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.
  7. 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 official record and your real-world result agree.
  • You have enough written evidence to prove the issue is finished if it returns later.

If it is still not fixed

  1. Issuer grievance officer or nodal officer
  2. Payment-system complaint route where relevant
  3. 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.

Open the full guide