TrustCheck BD
Reporting Guidelines

Transform Your Experience into an Alert That Actually Protects People

An incident report is only powerful when the supporting evidence can be thoroughly validated. Learn exactly what files to attach, what to avoid, and how to submit a case that our moderation team can approve in minutes rather than decline.

Anatomy of a Valid Report

Six Structured Steps to a Verifiable Case Profile

This outlines the exact data flow you will complete during your submission. Click each step to see what our moderation panels look for — providing comprehensive details ensures rapid approval and entry into the database.

What a Strong Submission Looks Like

Identify the primary subject of your report

Required

Input the specific business name or alias they operate under. This serves as the primary anchor data point that all subsequent evidence connects to.

  • The active name or business alias they display online
  • At least one primary identifier — such as a phone number, mobile wallet, or link
  • The online network where you originally encountered them (e.g., Facebook, standalone website)

Standard Starting Point

Name: "BD Gadget Hub BD" · Location: facebook.com/bdgadgethubbd

Report Strength17%
Evidence Validation Check

One Incident, Two Independent Submissions — Only One Gets Approved

Select a validation category below to compare files. The systemic difference between a rejected profile and an approved, verified warning usually comes down to a few missing structural attributes.

Insufficient EvidenceLikely Terminated

Obscured, heavily cropped, missing TrxID

  • The screenshot is too blurred or low-resolution to verify numbers
  • The critical unique Transaction ID is cropped out or hidden
  • The transfer ledger lacks clear timestamp and pricing metrics

The provided file contains zero matching markers required for automated or manual verification.

Verified Evidence StandardApproved & Verified

Complete, high-resolution, traceable log

  • The absolute Transaction ID is entirely visible in a single frame
  • The precise financial volume and timestamp match network parameters
  • The target receiving mobile wallet is clearly identifiable

A single review allows the moderation panel to cross-check and validate the event instantly.

Report by Scenario

Unsure What Files to Attach? Select Your Specific Situation

Select the transaction environment that maps to your current experience. We will display the exact verification files required to ensure your database submission satisfies our standards.

An online page requested advance payment and ceased communications

Required Attachments

  1. 1Upload a complete screenshot of the page profile — showing the title, follower count, and the persistent URL
  2. 2Capture the specific commercial listing and the exact price parameters quoted
  3. 3Save the chat logs where advance transfers were explicitly requested to "authorize the shipment"
  4. 4Attach the official bKash or Nagad TrxID file confirming the advance transaction
Database Infrastructure

You Have the Proof. Let's Deploy It to Protect Others.

Every authenticated incident report you log creates a dynamic public threat warning — preventing the next consumer from completing a transaction with a known fraud risk. The process takes less than five minutes.