Every KYC-verified account rests on a small set of documents. Understanding what each one is, why it is requested, and how it is used gives researchers a much clearer picture of what verification actually involves — and what data lives inside a modern financial platform's identity vault.
1. Government-issued photo ID. This is the anchor document. Passports are universally accepted because their format and security features are standardized. National ID cards and driver's licenses are also common, though acceptance varies by platform and jurisdiction. The image must be sharp, in color, uncropped, and match the details typed into the onboarding form — mismatched dates, blurred edges, or expired documents are the most common cause of automated rejection.
2. Selfie and liveness check. A static selfie proves the ID belongs to a real person; a liveness step proves that person is physically present at onboarding rather than a photograph or deepfake. Modern liveness modules ask users to blink, turn their head, or follow a moving dot; some capture short video clips analyzed by fraud vendors like Onfido, Jumio, Sumsub, or Persona.
3. Proof of address. Higher verification tiers layer on a recent utility bill, bank statement, tax notice, or government letter dated within a defined window — commonly 90 days. The document must show the user's full name, physical address, and issuer information. PDF downloads from a bank or utility portal are typically accepted; screenshots and photos of screens are typically not.
4. Source-of-funds documentation. High-volume users or those triggering enhanced due diligence may be asked to explain where their capital originated. Acceptable documentation includes recent payslips, employment contracts, business financial statements, sale-of-property records, or inheritance documents. This step exists because AML frameworks require platforms to understand economic activity, not just identity.
5. Business documentation. Business accounts require articles of incorporation, a certificate of good standing, a registered office address, and a beneficial-ownership disclosure that lists every individual holding 25 percent or more of the entity. The signing representative also completes a personal KYC flow on top.
6. Tax identifiers. In jurisdictions covered by FATCA (United States) or CRS (most OECD members), platforms collect the user's tax residency and tax identification number as part of onboarding. This information is reported to the relevant tax authority under bilateral information-exchange agreements.
7. How documents are handled. Reputable platforms encrypt uploaded documents in transit and at rest, retain them only for the period required by law (typically five to seven years after account closure), and expose access to a narrow set of compliance staff. Users have data-access and deletion rights under GDPR, CCPA, and comparable frameworks, though those rights are subject to retention obligations imposed by financial regulators.
8. Common rejection patterns. The most frequent causes of rejected verification are: expired documents, name spelling mismatches between the ID and the onboarding form, glare or shadows on the ID photo, cropped edges that hide security features, addresses on utility bills that do not match the address typed, and PDFs that have been edited or re-saved and therefore fail integrity checks.
Verification documentation exists at the intersection of user experience, fraud prevention, and regulatory compliance. Understanding each document's role helps researchers approach the process with informed expectations rather than treating it as an opaque hurdle. For related background, see the pieces on Binance verification and how modern exchanges approach security.