How to Report a Scam to Your Bank: Evidence Checklist
A bank fraud team works from a file. If the file is thin, the case is decided on the bank's default assumptions, which are rarely in your favour. If the file is complete and organised, the case is decided on your facts. The difference is usually a couple of hours of preparation.
Six documents decide most cases. Not sixty. The fraud team needs to see what was promised, what you paid, and that you acted promptly.
The Short Version
- The six core documents: transaction record, communication log, screenshots, written timeline, identity proof and any police reference.
- Capture screenshots with the URL bar, date and full page visible — cropped images are frequently rejected.
- Build a one-page timeline with dates in a single column; it is the document reviewers read first.
- Package everything as a single PDF with a contents page, named by date.
- Keep the whole file after the case closes; disputes can be reopened and appeals need the same evidence.
What the Bank's Fraud Team Actually Needs
A fraud reviewer is answering three questions, in this order. Everything in your file should serve one of them.
- Did the payment happen, and how? The transaction record answers this. Rail, amount, date, recipient, reference.
- Was the customer deceived or unauthorized? The communication log and screenshots answer this. What were you told, and by whom?
- Did the customer act promptly and honestly? The timeline and your contact attempts answer this. Delay and inconsistency are the two things that sink otherwise valid claims.
Notice that none of those questions is "how upsetting was this". Emotional detail does not move a case; dated facts do. Write the file for a reviewer who has four minutes and no prior knowledge of you.
The Six Documents That Decide Cases
| # | Document | What it must show | Where to get it |
|---|---|---|---|
| 1 | Transaction record | Date, amount, recipient name as it appears, reference number, and the rail used | Your statement or app transaction detail, exported as PDF |
| 2 | Communication log | Every message, email or call with the scammer, in order, with dates | Your phone, email client or platform message history |
| 3 | Screenshots | The listing, website, profile or wallet address as it appeared at the time | Captured by you, ideally before you contacted anyone |
| 4 | Written timeline | A single dated sequence from first contact to reporting | Written by you, one page |
| 5 | Identity and account proof | That the account and the payment are yours | Statement header, or the bank's own verification process |
| 6 | Police or agency reference | That you reported the matter formally | Your police report number, IC3 or FTC reference |
Document 6 is optional but disproportionately useful. A case with a police reference is treated differently from one without, even when the police are not investigating.
Screenshots: What to Capture and How
Screenshots are the most commonly botched evidence. A cropped image of a chat bubble proves very little; a full-page capture with the URL, the date and the surrounding context proves a great deal.
Capture rules:
- Include the URL bar for anything web-based. Without it, the image cannot be tied to a domain.
- Include the date and time where the interface shows it, or capture the device clock in the same frame.
- Capture the whole page, not just the relevant line. Context is what makes an image credible.
- Do not annotate or edit. An edited screenshot invites a challenge to its authenticity.
- Save the original file, not a re-share through a messaging app, which strips metadata and compresses detail.
If a website is still live, capture it today. Scam sites disappear quickly, and a screenshot taken before it vanishes is worth more than a description of what it used to say.
The Transaction Record
This is the spine of the file. Get it as a PDF export from your bank or app rather than a photograph of a screen.
It should show, for each disputed payment: the date and time, the amount and currency, the recipient name exactly as the bank recorded it, the reference or trace number, and the rail — card, ACH, wire, Zelle, or an internal transfer.
If the payment went through a payment app rather than the bank directly, export the app's own transaction detail as well. The bank's record may show only the app as the counterparty, which is not enough on its own.
For crypto payments, the transaction hash is the equivalent of a reference number and should be included. A public blockchain record is unusually strong evidence that a transfer occurred, though it does not identify the person behind it. You can read the public side of that record with the free wallet tracer.
The Communication Log
Assemble every interaction with the other party into one chronological list. Include the channel, the date, who said what, and any attachment or link exchanged.
What matters most in this log is the promise. A bank reviewer is looking for the specific claim that induced the payment: the guaranteed return, the investment platform, the item for sale, the service that was never delivered. Quote it verbatim where you can.
If the conversation happened on a platform, export or screenshot the thread rather than retyping it. If it happened by phone, write down what was said and when, and mark it clearly as your own recollection. Do not present a reconstruction as a transcript.
A Written Timeline
One page, one column of dates, plain language. This is the document reviewers read first, and a good one shapes how everything else is interpreted.
Format that works:
[DATE] — First contact from [name/handle] via [channel]. They claimed [claim].
[DATE] — I checked [what you checked] and saw [what you found].
[DATE] — I sent [amount] by [rail] to [recipient]. Reference [number].
[DATE] — [What made you realise].
[DATE] — I called the bank at [time] and spoke to [agent]. Case [number].
[DATE] — I filed a police report, reference [number].
Keep it factual and free of adjectives. "They claimed a 4% weekly return" is evidence; "they were obviously criminals" is not. If a date is uncertain, write "on or about" rather than guessing precisely.
How to Package It
Presentation affects how quickly a case moves. A single well-ordered PDF is processed faster than twelve loose attachments.
- One PDF with a contents page listing each document and its page number.
- Timeline first, then the transaction record, then the communication log, then screenshots.
- Name the file with your case reference and the date, not "documents.pdf".
- Keep the total under about 20 MB so it passes attachment limits.
- Send it through the bank's secure channel, and keep the submission confirmation.
If the bank's portal accepts only images, convert each page to a legible image rather than photographing a screen. Legibility is not optional; an unreadable document is treated as absent.
What to Keep After the Case Closes
Keep everything, for at least a few years. Disputes can be reopened, appeals have their own deadlines, and a later enforcement action or refund programme may ask for proof of loss.
Store the file in two places, one of them offline. Include the final decision letter, which states the reason for the outcome and is the document you need if you escalate to a regulator or ombudsman.
If the case is denied, the reason in that letter tells you what to do next. For the reporting side of the process, see what to say when you report a scam to your bank, and for the outcome by payment type, whether your bank will refund you.
Questions people ask
What evidence does a bank need for a scam claim?
Six documents cover most cases: the transaction record, the communication log with the other party, screenshots of the listing or website, a one-page written timeline, proof the account is yours, and any police or agency reference number.
Are screenshots enough evidence for a bank dispute?
Screenshots help but are rarely sufficient alone. They must show the URL, the date and the full context, and they need to be paired with the transaction record and a written timeline. Cropped or edited images are frequently challenged.
How do I prove I was scammed to my bank?
Show what was promised and what you paid. The strongest file pairs the transaction record with the specific claim that induced the payment, quoted verbatim, plus a dated timeline showing you reported promptly.
Should I send my bank a police report?
Yes, if you have one. A police reference is not required for most claims, but a case with one is treated differently from a case without. It also supports any later escalation to a regulator.
How long should I keep my scam evidence?
Keep it for at least a few years. Disputes can be reopened, appeals have their own deadlines, and later enforcement actions or refund programmes may ask for proof of loss. Store it in two places, one offline.
Check the address before you send anything
A free scan reads public chain data in your browser: balance, activity, counterparties and flags. No wallet connection, no seed phrase, no signup.
Primary sources and further reading
- Consumer Financial Protection Bureau — the US federal complaint route for bank and payment problems
- FBI Internet Crime Complaint Center — federal reporting portal for fraud and internet crime
- FTC Consumer Sentinel Network — how consumer fraud reports are collected and shared
- USA.gov legal aid — finding legal help for consumer and fraud matters
Related guides
Information only. We never promise recovery.