Authenticate the channel
Open the upload route from a saved domain or signed-in cashier; never send identity files to an address introduced only by chat.
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 purpose
Label proof of identity, address, source of funds and payment ownership separately so one accepted document is not requested without explanation.
Redact safely
Follow the stated acceptance policy and hide unrelated numbers where permitted while keeping name, issuer, validity and required edges visible.
Log every review
Record upload time, file type, acceptance or rejection reason, reviewer message and the next promised response.
Protect retained copies
Store evidence securely, remove accidental metadata where appropriate and never share passwords, one-time codes or full card security codes.
More documents do not automatically mean more certainty
Repeated requests should identify the missing field or failed validation. Pause if the operator cannot explain why an accepted record is insufficient.
Questions this page resolves
Can KYC happen at withdrawal?
Many services review at or before payout; timing and document categories should be disclosed in current terms.
Should support ask for an authentication code?
No. One-time login or payment codes should not be disclosed to support.
What should a rejection notice contain?
It should identify the failed requirement and a safe route to correct it without exposing unnecessary data.