Confirm the request source
Sign in through the independently verified domain and check the account notification. Treat emailed upload links, remote-access requests and password requests as stop signals.
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.
Match document to purpose
Separate identity, address, payment ownership and funds-source evidence. Ask which field failed and why another document is required before resubmitting.
Reduce exposed data
Use the official secure uploader and follow stated redaction rules. Never reveal passwords, one-time codes, wallet seeds or full security credentials.
Log review milestones
Record submission, receipt, rejection reason, resubmission and approval. Keep the KYC clock distinct from the later withdrawal approval and rail settlement.
Verification speed is not worth losing account security
A legitimate review can explain its data controller, retention rules and complaint path. Pause where identity, domain or upload destination remains unresolved.
Questions this page resolves
Should FastPay KYC be completed before withdrawal?
Early verification can expose issues, but use only the verified account route.
Can support request a wallet seed?
No. A seed or private key must never be disclosed.
What should a rejection include?
The failed requirement and a proportionate route to correct it.