Authenticate the request
Open SpinMacho through the previously verified domain and read the account notice there. Do not use upload links delivered only by social message, shortened URL or unsolicited email.
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.
Separate evidence categories
List proof of identity, legal age, address, payment ownership and source-of-funds requests individually. Ask which field or category is incomplete before resubmitting.
Use the minimum disclosure
Follow accepted-format rules and mask unrelated numbers where permitted. Passwords, CVV values, one-time codes, wallet seeds and remote screen access are never verification documents.
Record the data controller
Save the privacy entity, verification provider, receiving hostname, stated purpose, retention wording and contact route current on submission day.
Track the final decision
Log upload time, file category, acceptance or rejection reason and next deadline. A written status is more useful than repeated uploads to different support agents.
Verification should not require authentication secrets
A legitimate KYC workflow can inspect documents without taking control of email, bank, device or crypto-wallet access.
Questions this page resolves
Can KYC happen before a withdrawal?
Yes, depending on policy and risk checks; the requested category and secure route should be clear.
Should I send a live bank login?
No. Provide accepted ownership evidence without credentials or one-time authentication.
What if my address formats differ?
Ask which record controls the mismatch and provide a dated supported document through the verified channel.