Authenticate the request
Open the known Caswino domain independently and read the account notice there. Do not upload identity files through a social message, shortened link, unknown mirror or ordinary chat attachment.
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 each document category
Separate identity, age, address, payment ownership and source-of-funds checks. Ask which field is missing and what accepted format applies before sending another copy.
Minimise sensitive exposure
Mask unrelated numbers where policy permits and retain originals securely. Never provide password, CVV, one-time code, private key, seed phrase or remote screen control.
Track controller and outcome
Record the data controller, verification provider, upload hostname, purpose, retention wording, submission time and written acceptance or rejection reason.
Crypto does not remove identity risk
A wallet transaction can be public while the operator still requests private KYC evidence; protect both trails and never connect them through secret disclosure.
Questions this page resolves
Can Caswino request KYC at withdrawal?
Terms may allow it, but the category and secure route should be explicit.
Should I send a wallet seed?
Never. Ownership can be evidenced without private keys or recovery phrases.
What if a document is rejected?
Request the exact field, format or mismatch before resubmitting.