← Back home

Account safety

Is that verification request real — or a trap?

Real verification requests and phishing attempts now look almost identical. This guide gives you a 20-point check you can run in a few minutes before you click, reply, or upload anything.

A person pausing before responding to a verification request on a laptop

Why this guide exists

Verification is a normal part of owning a verified account. Platforms ask for documents when you sign up, when limits change, and when their rules are updated. That normality is exactly what makes a fake request dangerous: it arrives looking like a routine step you have already done before, and it asks for the very things — an ID photo, a selfie, a document — that a real request would also ask for. The difference is rarely in what is asked. It is in who is asking, where the link goes, and how the message tries to make you hurry. This guide focuses on those differences, because they are the ones you can check yourself, with no special tools, before you hand anything over.

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.

The sender check (checks 1–5)

  • Read the full sender address, not just the display name — a real platform message comes from its own domain, not a lookalike with an extra letter or a free mailbox.
  • Compare the sender with a message you already know is real, such as the welcome email from when the account was created, and look for any difference in the domain.
  • Be suspicious of a message that arrives on a new channel — if the platform normally writes by email and this one comes by SMS or a chat app, treat it as unverified.
  • Check whether the message addresses you by your full account name; a genuine verification request usually does, while a mass-sent fake often uses a generic greeting or none at all.
  • Never trust a phone number or reply address printed inside the message itself — look the platform's official support contact up separately before you respond.

The link and attachment check (checks 6–10)

  • Hover over every link before you click and read the real destination in the status bar — if it does not match the platform's own domain, do not open it.
  • Watch for shortened links in a verification message; a real platform rarely needs to hide where its own verification page lives.
  • Refuse unexpected attachments in a verification request — a genuine document request normally points you to upload inside your account, not to a file sent to you.
  • If a link asks you to sign in, close it and open the platform yourself from a bookmark or by typing the address — then check for the same request inside your account.
  • Treat a QR code in a verification message the same way as a link: it can point anywhere, so only scan it if you already trust the sender and the context.

The document and data check (checks 11–15)

  • A real verification request asks for a specific document for a specific reason; a fake one often asks for everything at once — ID, selfie, card, password — in a single message.
  • Never send a full password, a one-time code, or a 2FA seed in reply to any verification request — no legitimate platform asks for those by message.
  • Check what the request already knows about you: if it quotes details only the platform should hold, that is reassuring, but if it asks you to confirm details it should already have, slow down.
  • Ask yourself whether the document requested matches the step you are actually at — a request for a tax form when you only opened the account yesterday does not fit.
  • Keep a copy of exactly what you sent, when, and through which channel, so you can show support what happened if anything goes wrong later.

The tone and timing check (checks 16–20)

  • Urgency is the phisher's favourite tool — a message that says your account closes in a few hours is trying to stop you thinking, so pause and verify through another channel.
  • Look for threats mixed with help: a message that scares you and then offers a single link as the only rescue is a classic pattern, not how real support writes.
  • Read the message twice for small errors — odd grammar, mismatched dates, or a greeting in the wrong language can all be signs that it was copied and reused.
  • Check the time it arrived: a verification request sent in the middle of the night for a platform that operates on business hours deserves a second look before you act.
  • If the message claims a deadline, confirm it inside your own account first — a real deadline will usually be visible on your dashboard or in your notification centre.

Red flags that mean walk away

Any one of these on its own is a reason to stop and verify through another channel. Two or more together is a reason to treat the message as fake until the platform itself tells you otherwise. Do not try to argue with the sender or test the link to see what happens — a single click on a crafted page can be enough to hand over a session or install something you did not ask for.

  • The sender domain is close to the real one but not identical — one letter changed, a hyphen added, or a different ending.
  • The message asks you to reply with a password, a one-time code, or your full card number.
  • A link leads somewhere other than the platform's own website when you hover over it.
  • The request arrived out of the blue, with no matching notice inside your account.
  • You are told to act within hours or the account will be closed, deleted, or frozen.
  • The message contains an unexpected attachment you were never told to expect.
  • The tone flips between threatening and friendly in the same short message.
  • It asks for documents that have nothing to do with the step you are on.

What a real verification request looks like

A genuine request is usually boring, and that is a good sign. It names the platform, names you, and names the exact document or step that is needed. It gives you a way to complete it inside your own account rather than through a link in the message, and it does not need you to reply with sensitive information. If you sign in on your own and find the same request waiting there, with the same wording and the same case or reference number, you have strong confirmation that it is real. If the message and the account disagree — the email says urgent, the dashboard says nothing — trust the account, and ask support about the email before you do anything else.

Real requests also respect the boundaries of the step they belong to. A request for proof of address asks for proof of address, not for your password as well. A request to confirm a payout method asks about that method, not for a photo of your card held next to your face. When a request keeps growing — one more document, one more code, one more confirmation — that growth is itself a warning sign. A legitimate process tells you the full list of what it needs up front, and it does not keep adding items after you have already complied.

If you already clicked or replied

If you clicked a link, entered a password, or sent a document before realising the message was fake, do not panic — act in the right order. First, stop the damage: secure the account from inside the platform itself. Then tell the platform what happened, with the message attached, so it can check for misuse. Then watch the account closely for a few days. Most of the harm from a phishing attempt comes not from the first click but from the hours after it, when the account is left unchanged while someone else tries the credentials. A quick password change and a check of recent logins closes most of that window.

Change the password

From the platform itself — not from any link in the suspicious message — change the account password and sign out of other sessions if the platform offers that option.

Turn on 2FA

If two-factor authentication was off, switch it on with an authenticator app and save the backup codes somewhere only you can reach them.

Tell the platform

Forward the suspicious message to the platform's official abuse or support address so its team can confirm it and warn other users.

Watch the account

Check recent logins, connected devices, and payout details for anything you do not recognise, and keep an eye on them for the next few days.

If you sent a photo of an ID document, keep a note of exactly which document and when. You cannot un-send it, but knowing what was shared helps you and the platform judge the risk — and it helps if you later need to explain the incident to your bank or to support. Do not send the same document again to anyone who asks for it in the same conversation, even if they claim to be fixing the problem.

Pause first

A real deadline survives a ten-minute check. A fake one depends on you skipping it.

Verify in the app

Open the platform yourself and look for the same request inside your account before you trust any message.

Ask a human

When in doubt, contact support through the channel you already trust and quote the message back to them.

Not sure about a message you received?

Send it to us before you act on it. We will help you check whether it matches a real verification step for your account.

This guide is educational information only and is not legal, financial, or security advice. Verification rules differ by platform and change over time — always confirm the current requirements inside your own account or with the platform's official support.