Authenticate the request
Open the account from a verified bookmark and compare the in-account notice with the message. Do not upload through a reply email or unfamiliar support link.
Identity checks can relate to age, account ownership, payments or risk review, but a vague message is not enough. Confirm the exact account, requested document, purpose and secure upload destination before sharing sensitive data.
Open the verified play routeThis 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.
Open the account from a verified bookmark and compare the in-account notice with the message. Do not upload through a reply email or unfamiliar support link.
Separate identity, address, payment ownership and source-of-funds questions. Request the minimum acceptable document and whether nonessential fields may be redacted.
Use the verified portal, inspect the final hostname and avoid public Wi-Fi. Never send passwords, one-time codes, full banking credentials or wallet seeds.
Timestamp request, upload receipt, additional questions, decision and any withdrawal impact. Repeated requests should identify what remained insufficient.
Read retention, access, processor and deletion information in the current privacy notice; keep a redacted copy of what was submitted.
Sending unrelated statements or unredacted identifiers increases exposure and can complicate the case. Ask support to identify the missing fact and acceptable secure evidence before uploading again.
Use only a separately verified secure channel and ask whether a safer portal is available.
Ask which fields are necessary; preserve the required name, dates and ownership details while hiding unrelated data where permitted.
No. It resolves one review layer; payment, terms and account checks can remain.