- This topic has 0 replies, 1 voice, and was last updated 26 minutes ago by .
“Verification Video” Asked for Much More Than a Face
This started as a normal withdrawal verification.
The user had already submitted identification when opening the crypto account. Later, when he tried to withdraw, support said one final security check was required.
A short video.
That didn’t immediately sound unreasonable.
Then the instructions arrived.
The user was told to record himself holding his ID while saying:
His full name
His account email
His current crypto balance
The amount he wanted to withdraw
But there was another instruction that bothered him.
He had to say:
“I authorize all transactions connected with this account.”
All transactions?
He asked support whether he could simply confirm the specific withdrawal instead.
They refused.
According to them, the sentence had to be spoken exactly as written or verification would fail.
That was enough for him to stop.
The issue here isn’t that every video verification request is suspicious. Legitimate financial services may use identity checks.
The question is what you’re being asked to authorize while doing it.
A video containing your face, identification document, voice, and a broad authorization statement could potentially be much more sensitive than an ordinary selfie verification.
I’d personally separate two things:
Proving identity is one request.
Giving broad financial authorization is another.
If those two things are being combined, I’d want a clear explanation before recording anything.
I’d also verify the request through the company’s established official channel rather than relying solely on whoever sent the instructions.
Sometimes people concentrate so much on protecting passwords and recovery phrases that they forget how valuable identity documents, voice recordings, and verification videos can be.
Read the script before you record it.
If you’re uncomfortable with what you’re being asked to say, don’t let a pending withdrawal pressure you into saying it anyway.
- You must be logged in to reply to this topic.