Bank & money paperworkIndia

Prepare a failed-payment complaint

Get your facts together with a trusted grown-up.

Put the debit, transaction reference, receiving-side information and bank response together before disputing a failed payment.

DisputeOrganisationPrep worksheet

Who it goes to: Bank or payment provider responsible for the identified transaction and its published complaint process

Where it applies: India; the bank, product, requester authority and current instructions determine the process

Prepare this
01 · What is this?

A transaction-and-evidence sheet for a payment complaint.

02 · When is it useful?

Use it when money was debited but cash, merchant confirmation or the expected credit is missing.

03 · Start here

Save the actual transaction reference and bank entry, then identify whether this is a technical failure, wrong recipient or suspected fraud.

Gather your pieces

  1. Use actual bank/payment entries, transaction references and timestamps; preserve originals.
  2. Distinguish a technical failure, merchant refund, wrong-beneficiary payment and an unauthorised transaction.
  3. For suspected unauthorised activity, report promptly through the bank's verified channel; financial cyberfraud can also be reported through 1930 and the official cybercrime route.

Your prep sheet

Replace each [bracketed label] with your own verified details. Open the editor to make it yours, then read it through before sending.

FAILED PAYMENT — PRIVATE FACT AND EVIDENCE SHEET
Prepared by: [Account holder / authorised requester]
Responsible bank/provider: [Bank and handling office]
Date: [Document date]
Masked account/service reference: [Account or loan reference]
Verified contact: [Reply channel]

1. IDENTIFY THE TRANSACTION
[Transaction details]

Use the actual reference and timestamp. Keep the payment system and incident type clear: an ATM cash problem, transfer non-credit and merchant confirmation problem may have different rules. Do not reclassify a wrong-recipient transfer or suspected fraud as an ordinary technical failure.

2. WHAT HAPPENED
[Relevant facts]

3. RECEIVING-SIDE INFORMATION
[Receiving-side information]

Separate evidence of an actual credit or merchant settlement from a person's statement or app status. Mark information that has not been verified. A successful-looking screen and a beneficiary's bank entry may describe different stages.

4. EVIDENCE INDEX
[Evidence index]

Preserve the original debit entry, transaction receipt and relevant communications. Use masked identifiers in this planning sheet. Supply any full details the provider genuinely needs through its verified channel.

5. REQUESTED RESOLUTION OR EXPLANATION
[Requested action]

State the problem accurately and ask for the actual transaction/reversal position. Ask the provider to identify the applicable incident category and rule before relying on a proposed deadline or compensation calculation. Do not insert a universal number of days or guaranteed refund.

6. COMPLAINT AND OUTCOME LOG
[Complaint and reversal log]

Record the first complaint, acknowledgment and every actual bank/provider response. Record a reversal or credit only when it is visible in the relevant issued account record, with its date and amount.

If the activity was unauthorised or appears fraudulent, use the bank's verified urgent reporting channel promptly and the official financial-cyberfraud reporting route where applicable. Keep that report separate from any technical-failure complaint.

This sheet is private preparation. It does not submit a dispute, establish liability, extend a time limit or guarantee recovery.

Your next moves

  1. Submit through the responsible bank/provider's actual dispute route and retain acknowledgment.
  2. Ask which payment-system rule, reversal period or compensation framework applies to the incident type; do not use one deadline for every payment.
  3. If unresolved, keep the response history and check the applicable escalation route and filing window.

Real-world check

Private evidence sheet, not a completed dispute form or a promise of recovery. RBI payment timelines depend on system and incident type; this sheet invents none. A screenshot alone may not prove settlement, and a pending merchant refund differs from an unauthorised transaction.

Sources & official links