Use this before filing or updating a cybercrime complaint. It shows which proof usually matters first: UTR/reference, debit alert, bank ticket, scam chat, suspect phone or UPI ID, URL, APK, account takeover proof, and one clean timeline.
Proof should show who contacted you, what they asked, where money or access moved, and what official follow-up already happened.
Do not upload OTP, UPI PIN, CVV, full passwords, private keys, recovery codes, or unnecessary identity documents.
This guide is reviewed by the ScamScan Safety Desk for practical public-safety guidance, evidence organization, and clear official-route limits. It is not legal, police, bank, platform, or guaranteed recovery advice.
For active money loss, account takeover, device compromise, or identity misuse, use the relevant official bank, wallet, platform, 1930, cybercrime.gov.in, police, or cyber cell route.
If UPI, wallet, card, netbanking, loan app, investment, or fake support fraud caused a debit, prioritize proof that lets the bank, wallet, 1930, or official complaint trail identify the transaction quickly.
Amount, date/time, UTR/reference, debit SMS, payment app receipt, bank statement line, receiver UPI ID/account, IFSC, or wallet transaction ID.
Bank/wallet ticket, freeze request, card block reference, branch note, dispute number, or email acknowledgement.
Phone number, WhatsApp/Telegram username, UPI ID, QR image, website, email, app name, profile link, group link, or support number.
1930 complaint ID, cybercrime.gov.in acknowledgement, police/cyber cell diary note, and every follow-up date in one note.
A complaint becomes easier to understand when proof is in order. A pile of cropped images can hide the important details: who contacted you, exact date/time, transaction reference, URL, payment route, and what changed after the scam.
Before uploading, make a simple folder or note: 01 timeline, 02 transaction, 03 chats/calls, 04 links/files, 05 bank/platform/1930 follow-up. Use the same facts everywhere.
ScamScan is not an official government, police, bank, platform, or recovery service. It helps organize risk signals, evidence, and next steps.
One clean timeline beats twenty disconnected screenshots.
Write 5-8 lines: first contact, risky request, payment/account event, amount, transaction time, suspect detail, and current status.
Attach UTR/reference, debit alert, bank statement line, receiver UPI/account, bank ticket, and freeze or dispute reference.
Save chat screenshots with sender number, username, group name, dates, payment instruction, threat, fee demand, or refund promise visible.
Preserve URL, APK/file name, email headers if available, app permission screens, browser history, login alerts, and remote-access app details.
Keep 1930 ID, cybercrime.gov.in acknowledgement, bank/wallet ticket, platform report, police/cyber cell note, and follow-up dates together.
Use simple names such as 01-timeline, 02-debit-alert, 03-utr, 04-chat-payment-demand, 05-bank-ticket, 06-1930-id.
Do not delete original chats, SMS, emails, APK/file downloads, statements, or call logs. Keep an untouched copy before making a smaller upload copy.
Leave sender, date, time, amount, URL, transaction ID, and surrounding context visible. Cropped images can make follow-up harder.
Use the same amount, date, UTR/reference, suspect ID, and complaint ID in bank, 1930, cybercrime.gov.in, police, and platform follow-up.
| Case type | Proof to collect | Next action |
|---|---|---|
| UPI, card, wallet, netbanking fraud | UTR/reference, debit alert, bank statement, receiver UPI/account, bank ticket. | Call bank/wallet and 1930 quickly; use same proof in official complaint. |
| WhatsApp, Telegram, job/task, investment scam | Profile, group link, admin handle, task dashboard, fee demand, payment instruction. | Save before blocking; add transaction proof if money moved. |
| Phishing link or fake website | Full URL, sender, landing page screenshot, login alert, email headers if available. | Change exposed passwords from official route and preserve the link trail. |
| APK or remote-access app | APK filename, source chat/link, permissions, app icon/name, remote session clue, OTP/debit alerts. | Stop using the compromised flow and move to device/account recovery plus official reporting. |
| KYC, Aadhaar, PAN, document misuse | Form URL, document upload screen, email/SMS sender, ID shared, account or loan-app follow-up. | Monitor official accounts and keep document exposure timeline separate from money-loss proof. |
If this case affected money, account access, identity documents, device control, or threats, do not rely on a random helper. Use the official provider route that matches the harm.
Upload proof that explains the timeline: transaction UTR or reference, debit alert, bank or wallet ticket, scam chat, phone number, UPI ID or account, URL, app/APK details, account-login alerts, and a short written summary.
UTR or transaction reference is very useful when money moved, but do not delay urgent 1930 or bank reporting only because one detail is missing. Save the complaint ID and add missing proof through the official route later.
Avoid over-cropping. Keep full screenshots with date, time, sender, phone number, URL, group name, profile, amount, and context visible. Make a copy if you need to mask private data for non-official sharing.
Amount, date/time, UTR, debit SMS, bank statement line, receiver UPI/account, bank or wallet ticket, freeze request, 1930 ID, portal acknowledgement, and scam chat or call details help connect the case.
Save sender number or username, group invite link, profile screenshots, APK filename or URL, task dashboard, fee demand, payment instruction, transaction proof, and any message where the scammer asks for OTP, PIN, install, fee, tax, or refund unlock.
No. ScamScan is not an official portal and cannot access government, police, bank, or wallet databases. Use it only to organize proof before using cybercrime.gov.in, 1930, bank, wallet, police, or cyber cell routes.
Search SMS, email, screenshots, bank ticket notes, and downloads for the acknowledgement. Keep UTR, registered mobile or email, complaint date, and bank ticket ready for official follow-up.
No. Do not pay recovery, refund, unlock, verification, tax, or complaint-processing fees to random callers or helpers. Save the demand as proof if someone asks for money to change status or recover funds.