Identity proof best practices
Caution – Legacy solution
This page relates to the legacy solution for submitting KYC/KYB documents via the API KYC Document endpoints. New integrations must use the hosted KYC/KYB solution relying on the IDV Session endpoints.
Platforms with existing integrations should refer to email communications for details about the transition timeline.
The hosted KYC/KYB session provides guidance to the user during the process to maximize success rates. Many of the principles described below remain the same.
Both natural and legal users must provide an official identity document (ID) as proof of identity during the verification process. For legal users, it is the entity’s legal representative who must provide proof of identity.
Note - Accepted documents vary by country
Not all kinds of official identity documents are accepted for all countries. Check which documents can be submitted per country in the Accepted ID documents article.
Best practices
When uploading files, it is very important that the user respects the best practices below to ensure that the document can be read and verified.
If any of the guidelines are not respected, it may result in an error or delay in processing the document.
The document should be:
See the how-to guide for guidance in technical implementation:
Errors to avoid
Below are some common errors than can lead to a document being refused:
Edges not fully visible
Machine-readable zone (MRZ), data, or photo not fully visible
Covered by anything, especially a finger
Glare or flash obscuring readability
Blurred
Black and white
Card-type with both sides in one file
Two types of document submitted simultaneously (in the same file or not)