Confirm the authenticated request
Open the verified domain independently and compare the account notification. Treat emailed upload links and remote-access requests as stop signals.
This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Map document to requirement
Separate identity, address, payment ownership and funds-source checks. Ask which field failed before resubmitting.
Minimise exposed data
Follow stated redaction rules and never share a password, OTP, card security code, wallet seed or private key.
Log every decision
Record request, submission, receipt, rejection reason, correction and approval. Keep this clock separate from payout dispatch.
Verification is not a reason to surrender account security
A proportionate process explains why data is needed, where it is stored and how a complaint can be made. Pause when domain or controller identity is unresolved.
Questions this page resolves
Can support ask for a wallet seed?
No; a seed or private key must never be shared.
Why verify early?
It can expose identity or payment mismatches before a large withdrawal.
What should a rejection contain?
The failed requirement and a safe route to correct it.