Cyber crime & financial fraud help across IndiaCall +91-9007000603
Home › Legal Articles › Digital evidence

Evidence checklist for credit card fraud cases

By Advocate Panchanand Shaw, Bar Council of West Bengal · Published 4 Nov 2026 · Digital evidence

The evidence that decides a credit card fraud case is almost never dramatic. It is the card statement, the alerts, the complaint logs with their timestamps, and the device the fraud passed through. Electronic records also need a certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023 before a court will admit them.

Every card fraud case comes down to one factual dispute: did you authorise the transaction? Everything else, the amount, the merchant, the mode, is secondary. The evidence you gather is therefore not a general history of the fraud; it is a targeted set of records that answers that one question and fixes the dates on which you acted.

There is a second layer that victims miss entirely. Even a perfectly preserved record will not be read by a court unless it is admissible, and for electronic records admissibility runs through a certificate. Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 governs the admissibility of electronic records, and section 63(4) requires a certificate to be submitted along with the electronic record at each time it is produced. That requirement, which was section 65B of the old Indian Evidence Act, 1872, is why the list below is organised around what you save and how you save it.

The two standards you have to satisfy

The bank and the court apply different tests to the same facts, and conflating them is a common error. The bank applies the Reserve Bank of India directions on limiting customer liability in unauthorised electronic banking transactions, in circular DBR.No.Leg.BC.78/09.07.005/2017-18 dated 6 July 2017. Those directions turn on when the issuer communicated the transaction to you and when you notified it, so the alert date and the complaint date are the decisive facts. The court, if a prosecution or a recovery suit follows, applies the ordinary law of evidence and asks whether the unauthorised use is proved and by whom it was committed.

What both need is the same thing: an unbroken record of dates. The checklist below is arranged from the day of the transaction forward.

The evidence checklist

  1. The card statement for the disputed billing cycle, in full. Not one line highlighted, but the whole statement, so the context, the prior spending pattern and the disputed entries are all visible.
  2. The transaction alerts, as originally received. The SMS in the message thread and the email in the mailbox, with the sender header, date and time intact. A forwarded copy is weaker than the original.
  3. The bank's record of the disputed transactions. The transaction log showing the authorisation code, the merchant identifier, the entry mode, whether chip, contactless or card-not-present, and the amount and time of each entry.
  4. Your written dispute to the issuer. The letter or dispute form in which you denied each transaction, with the date you sent it.
  5. Every complaint reference number. The number from the bank, the number from 1930 or the national cyber crime portal, and the number of any police complaint.
  6. The card block confirmation. Proof that you reported the card as compromised and the issuer blocked it, with the time.
  7. Proof that you had the card, or were elsewhere. A location record, a ticket, an office attendance record, a purchase made with the same card moments later, or the physical card itself.
  8. Communications with the merchant or the platform. The order confirmation, the delivery address, the consignee name for a fraudulent online purchase, and any response you received when you denied the sale.
  9. Records of the contact that preceded the fraud. The phishing email with the full headers, the spoofed SMS, the number that called you, the website address, and any chat in which your details were sought.
  10. The handset or device the fraud passed through. It is a communication device within the meaning of section 63 of the Bharatiya Sakshya Adhiniyam, 2023, and it may need to be produced in its original state.
  11. Bank statements for the beneficiary account, if you have them. These are usually obtained by the investigating officer rather than by you, but any partial record you have should be preserved.
  12. The certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023 for each electronic record you intend to produce in court.

What each item proves, and how long it survives

ItemWhat it provesRetention reality
Full card statementThe amount and date of each disputed entryAvailable from the issuer for the period it keeps records
Original alertsWhen the bank communicated the transaction to youOn your device, indefinitely, unless deleted
Transaction logThe entry mode and authorisation detailHeld by the issuer and network, not by you
Written disputeThat you denied the charge on a dateYours to keep permanently
Complaint numbersThat you reported, and whenYours, once saved
Card block confirmationThat further loss was preventedIssuer's record plus your acknowledgement
Proof of possession or alibiThat you did not make the transactionMust be collected early, before it expires
Merchant recordsWho received the goods and whereHeld by the merchant, and only briefly
CCTV footageWho used the card at a terminalOverwritten rapidly, days to weeks at most
The deviceThe messages and stored data it containsYours, if you do not reset or replace it
Section 63(4) certificateThat the record is admissiblePrepared when it is produced, not stored

Why the certificate matters more than the screenshot

The most common evidence mistake in card fraud cases is treating a screenshot as proof. A photograph of a phone showing an alert is a copy of a copy, and its authenticity can be challenged from several directions: the date is not verifiable from the image, the message thread can be edited, and the phone itself is the source. Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 brings electronic records into the law of evidence, but section 63(4) makes the record admissible only when accompanied by the prescribed certificate. The certificate must identify the record and describe how it was produced, give particulars of the device involved, and deal with the conditions in the section, and it must be signed by the person in charge of the computer or communication device or the management of the relevant activity, and by an expert.

What that means in practice is simple. Keep the original on the original device. Produce the device or a properly certified copy, not a casual photograph. Where the record sits with the bank, such as the alert delivery log or the transaction log, ask the bank to furnish it, because the certificate must come from the person in charge of that system, and you cannot sign it yourself.

Do not clean the device

Almost everyone does the one thing that destroys the most useful evidence. They delete the messages, clear the call log, or restore the phone to factory settings after the fraud. Do not. The message thread, the caller identification, the timestamps and the application data are the raw material of the case. If you must hand the phone in, do so with the original messages intact and with the phone still functional, so that its storage can be examined if the court requires it.

The same logic applies to email. Do not forward the phishing message to a personal folder and delete the original. Keep the original in the original mailbox, which preserves the header information, including the sending server and the time stamps that a forensic examination relies on.

Evidence the bank holds and you must demand

Some of the most decisive items will never be in your hands. Ask for them in writing, and keep the request, because a bank that fails to produce its own log has created a fact you can rely on later. What to ask for is the alert delivery log showing the date the transaction was communicated to you, the complaint log showing when your dispute was received and by whom, the chargeback or retrieval record raised with the card network, and the fraud-monitoring notes on the account if any are recorded.

What weakens a case

It is fair to say that the evidentiary position on a few questions is unsettled. Whether a bank's fraud-monitoring system should have detected an unusual pattern, and how much weight to give a card issuer's delivery log when the customer denies receiving the alert, are points on which courts and adjudicators have taken different views. None of that is within your control. What is within your control is whether the record shows that you denied the charge on a dated document, and whether the original electronic record still exists.

Filling the gaps with legal process

Certain items can only be obtained through legal process, and knowing that changes how you file. The transaction log at the network level, the subscriber and call records linked to a fraud number, and the CCTV footage at a terminal or an ATM are all in the hands of third parties who will release them to an investigating officer but not to a private complainant. The way to get them is to have them requisitioned by the investigating officer during investigation, or produced under an order of the court during the trial.

That is the practical reason to file the police complaint even where the bank route looks sufficient. The bank route produces money for the disputed transactions. The police route produces the records that identify a person. If the amount is significant enough to justify a recovery suit as well, the same records serve both, and our note on recovering money through a civil suit explains how that is sequenced. The behind-the-scenes sequence, from a preserved alert to a production order in court, is set out on our blog for victims who want to see the whole route at once.

When to involve a lawyer

Gathering evidence does not need a lawyer. Challenging its admissibility does, and the point at which admissibility becomes decisive is the point at which a case is actually before a court. Two situations justify advice earlier. The first is where the amount is large enough that the bank disputes liability under its board policy, because the file you built in the first week is then the whole case. The second is where a criminal case has been registered, either against the fraudster or against you, and the electronic records will be tested in cross-examination. On the first, a cyber crime lawyer in Kolkata can review the file and certify what is missing. On the second, timing and procedure matter, and the relevant guidance on criminal defence should be read before any statement is given. In either case, the first step is the same: keep the originals, and write down every date.

Need help with a cyber crime matter?

Tell me what happened and I will tell you what to file, where, and by when. First conversation is free.

Call +91-9007000603

Frequently asked questions

What evidence do I need for a credit card fraud case in India?

You need the full card statement for the disputed cycle, the original transaction alerts, the bank's transaction log, your written dispute, every complaint reference number, the card block confirmation, and independent proof that the card was with you. If the case goes to court, you also need a certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023 for each electronic record.

Are screenshots of transaction alerts enough evidence in court?

No. A photograph or screenshot of an alert is a copy, and its authenticity can be challenged because the source device and the date are not verifiable from the image. Keep the original message on the original phone and email, and if the record goes before a court, produce it with the certificate required by section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023.

What is the section 63(4) certificate for electronic records?

It is the certificate that must accompany an electronic record when it is produced in evidence. Under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023 it must identify the record and how it was produced, give particulars of the device involved, and deal with the section's conditions, signed by the person in charge of the device and by an expert. It replaces the old section 65B certificate.

Should I delete the messages and call log after a credit card fraud?

No. Deleting the messages, clearing the call log or resetting the phone destroys the most useful evidence in the case. The message thread, the caller identification and the timestamps are exactly what a court or an investigating officer needs. Keep the phone functional and the messages intact, and keep the original email in the original mailbox rather than forwarding it and deleting it.

Which evidence can I only get through the police or a court?

The network-level transaction log, the subscriber and call data records linked to a fraud telephone number, and CCTV footage from a terminal or ATM are held by third parties who release them to an investigating officer rather than to a private complainant. They are obtained during investigation or produced under an order of the court, which is one practical reason to file the police complaint.

Can I get the bank's alert logs and complaint records?

Yes, and you should ask in writing. Request the alert delivery log showing when the transaction was communicated to you, the complaint log showing when your dispute was received, and any chargeback record raised with the card network. These records decide the working-day calculation under the Reserve Bank directions, and a refusal to produce them is itself a documented fact.

What evidence weakens a credit card fraud claim?

A dispute letter that states one aggregate figure instead of denying each transaction, a claim that the card was with you that nothing independent supports, an admission that you shared a one-time password or card verification value, an unexplained delay before the first report, and screenshots offered in place of original records. A reset or replaced phone is the most damaging of all.

Does the bank have to prove the transaction was authorised by me?

The framework allocates the loss by reference to reporting timelines and to who was at fault. Where the deficiency is in the system, not with you or the bank, notifying within three working days gives you zero liability. Where the loss results from your own negligence, such as sharing credentials, you bear the whole loss until you report the transaction, and the bank bears it after.

Information for general guidance only and not legal advice. Provisions cited follow the Information Technology Act 2000, the Bharatiya Nyaya Sanhita 2023 and the Bharatiya Nagarik Suraksha Sanhita 2023.

Related articles

Cyber crime lawyer in your city · Bank account freeze help · Contact