How a fake verification request reaches you
Most fake requests arrive by email, because email is where real verification messages live too. But they also arrive by SMS, by WhatsApp or Telegram, and as a direct message on a social platform. The channel itself tells you nothing — a real platform can write to you on more than one channel, and a scammer can use any of them. What matters is whether the message can be confirmed somewhere else. A real request leaves a trace inside your own account: a notice on your dashboard, an entry in your notification centre, or a case number you can quote back to support. A fake one usually exists only in the message itself. That is the first test, and it is the most reliable one you have: if you cannot find the same request by signing in through your own bookmark, treat the message as unproven until someone at the platform confirms it.
The second thing to notice is the shape of the request. Real verification is a process with steps — you upload a document, it is reviewed, and you hear the result. A fake request often compresses the whole process into one message: verify now, upload everything now, confirm your identity now, or lose the account. That compression is deliberate. A person who has time to check will usually spot the problem, so the message is written to take the time away. Whenever a message makes you feel rushed, that feeling is information. Slow down, and run the checks below.
