E-Fraud Watch
Suggest a fraud card
Draft awareness cards for TrustOps review before they enter the public library.
Compose a fraud card
TrustOps reviews every submission. Keep it short, specific, actionable, and free of sensitive codes.
Starts with reviewed structure for Marketplace safety. Edit every field to match the real pattern before submission.
Share diagnostics
2/7 readyHeadlineUse a specific 12 to 70 character headline.
Name the tactic and channel, for example Fake support call requesting OTP.
Compact storyUse one punchy 55 to 170 character sentence.
Use actor plus tactic plus pressure plus risk in one sentence.
Red flagsAdd 3 flags, each 24 to 120 characters.
Lead with observable warning signs people can recognise before paying or sharing access.
Safe actionUse 40 to 190 characters and start with a clear action.
Start with Pause, Verify, Report, Save, Contact, Block, or Change.
Incident storyExplain what happened in 40 to 320 characters.
Summarise the sequence without names, phone numbers, account details, or raw allegations.
CaptionKeep social copy within 240 characters.
PrivacyNo OTPs, PINs, passwords, seed phrases, recovery codes, or full card numbers.
Preview
E-Fraud Watch
Emerging scam headline
Concise summary appears here.
Red flags
- 1Urgent payment request
- 2Link sent outside official app
- 3Request for OTP or PIN
What to do now
Actionable guidance: verify company domain, call bank hotline, pause until verified.
Share caption
Fraud alert: TrustOps reviewed this scam pattern. Pause, verify through the official channel, and keep evidence private.
120/240 characters