report this fraud — methodology
you were scammed and the official forms feel designed to reject you. this guide is for the kitchen-at-11pm moment: preserve what you still have, quantify the loss in your own words, pick the right agency, and use fatcousin prep-kits to build draft-only filings you submit yourself. fatcousin does not file ic3, ftc, cfpb, or state ag complaints on your behalf — it normalizes your evidence locally in the browser. for deeper fraud types, branch to romance scam, tech support scam, or pig butchering when the story fits those paths better.
which agency when
| agency | use when | prep-kit |
|---|---|---|
| ic3 (fbi internet crime) | online scam · wire · crypto · impersonation · most cyber-enabled fraud | ic3 prep-kit |
| ftc reportfraud | consumer scams · marketplace fraud · impersonation · gift-card pressure | ftc prep-kit |
| cfpb | bank · lender · debt collector · mortgage · payment platform dispute | cfpb prep-kit |
| state attorney general (ny · ca v1) | local merchant · in-state business · ca/ny resident complaints | state ag prep-kit |
filing more than one report is normal. ic3 and ftc are not duplicates — they feed different federal systems.
the first 10 minutes
- stop sending money — screenshot the scammer profile, chat, and payment confirmations before they delete anything.
- export bank and p2p transaction history for the disputed dates (csv or pdf from your bank app).
- save email headers if the scam started in email — do not rely on the mailbox UI alone.
- write a one-paragraph timeline: first contact date, what they asked for, how you paid, total loss.
- pick the right agency (see table below) — you can file more than one report for the same incident.
- run the matching prep-kit locally — fatcousin builds a draft json you copy into the official web form yourself.
- hash and keep your evidence folder — do not delete originals after submitting.
- if someone is in immediate danger, call local emergency services — this page is not a hotline.
the path
preserve → quantify → pick agency → build draft → submit yourself → follow up. steps 2–5 are prep-kits; run only the kits that match your agencies. merge exports in fatcousin-multi-tool-super-timeline-correlator if you have multiple evidence files across tools.
1. evidence manifest generator
inventory every screenshot, csv, chat export, and receipt with sha-256 hashes. gives you a defensible index before you touch agency forms.why first: victims lose files while panicking. freeze what you have before you start copying fields into ic3 or ftc.
2. ic3 fbi cybercrime complaint prep kit
victim fields + evidence merge → ic3 section-labeled draft json and copy-paste summary. cybercrime, wire fraud, crypto, romance-investment scams.why second: ic3 is the federal criminal intake for internet-enabled fraud — file here when money left via wire, crypto, or impersonation online.
3. ftc report fraud submission prep kit
reportfraud.ftc.gov shaped draft + checklist txt. consumer protection track — scams, impersonation, marketplace fraud.why third: ftc feeds consumer sentinel — complements ic3; many victims file both. draft only — you submit at reportfraud.ftc.gov.
4. cfpb financial complaint prep kit
cfpb complaint database field draft when a bank, lender, debt collector, or payment platform mishandled your money.why fourth: use when the harm involves a regulated financial product — unauthorized transfer, mortgage scam, debt collection abuse.
5. state ag consumer complaint multi-state prep kit
ny and california attorney general complaint drafts only (v1). business-name, narrative, attachment index.why fifth: state ag can pressure local merchants and platforms — narrow scope; other states use your AG web form manually.
6. case report generator
bundle hashed evidence + prep-kit exports into a pdf timeline for counsel, legal aid, or family helpers.why last: one readable package survives when you hand the story to someone who was not in the kitchen at 11pm.
common false leads
- fatcousin filed my report — no. every prep-kit exports a draft; you paste or type into the government site yourself.
- i only need one agency — many victims file ic3 + ftc; add cfpb when a bank mishandled the dispute; add state ag when the scammer is a local business.
- the scammer deleted the chat so i cannot report — bank records, wire confirmations, and email headers still count; write the narrative from memory and mark gaps honestly.
- this is the same as tech support scam — remote-access scams need device evidence; this entry point is for victims who need official intake forms first.
what we can tell you, what we can't
we can tell you:
- draft-shaped json and copy-paste summaries for ic3, ftc, cfpb, and ny/ca state ag forms
- keyword hints for scam category, payment method, and loss amounts found in your evidence files
- sha-256 evidence manifest for what you preserved
- local pdf case report from hashed exports
we can't tell you:
- submit forms for you — draft only
- recover money — bank recall, platform dispute, and law enforcement follow-up are outside this tool
- give legal advice — talk to legal aid or counsel for strategy
- cover every state ag form — v1 is ny and california only
handing it off
- law enforcement: ic3 confirmation number (after you file), evidence manifest, transaction ids, and wallet addresses from prep-kit exports.
- legal aid / family helper: case report pdf + draft json files + plain-language timeline.
- bank fraud department: cfpb draft fields + wire recall status notes from your narrative.
vertical hub: consumer fraud reporting · compare: tech support scam case type