Confirm the request origin
Open the account through a saved verified domain and read the request there. Do not upload identity files through an email attachment, social message, shortened link or remote-support session.
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 purpose
Separate proof of identity, address, age, payment ownership and source-of-funds checks. Ask which category is incomplete and what field must be visible before resubmitting.
Minimise exposed data
Follow the published acceptance rules and mask unrelated numbers where allowed. Never reveal a CVV, password, one-time code, recovery phrase or full online-banking screen.
Record consent and retention
Save the privacy-controller identity, purpose, retention wording and contact route current on upload day. Note any third-party verification provider and the domain receiving the file.
Track a decision
Log submitted, accepted, rejected and expired statuses with reasons and next deadline. Request a written outcome instead of repeatedly sending different copies without a defined deficiency.
More data is not automatically better verification
A proportionate process explains the missing field and protects secrets; pressure to share live authentication or remote access is a stop signal.
Questions this page resolves
What documents can KYC require?
Common categories include identity, address and payment ownership, but use the account’s current secure request.
Can I email my passport?
Prefer the verified upload route and ask for a safer channel if ordinary email is proposed.
Why was a clear document rejected?
Possible causes include expiry, cropping, mismatch or unsupported format; request the exact reason before resubmitting.