The KYC Document object
The KYC Document Object
is a container to store document pages in it. There is one KYC Document Object for one Type
of document
The process to send a KYC document is divided into 3 parts.
• Step 1 : Creation of a KYC Document
• Step 2: Creation of KYC Pages within the document. A document can have several pages.
• Step 3: Submission of the KYC Document. You will have to edit the object Document and set the Status field to "VALIDATION_ASKED" (instead of "CREATED")
The documents will be validated by our compliance team. Please note that in the sandbox environment you will need to validate submitted KYC documents manually via the 'Sandbox operations' tab.
Note that you are not allowed to store KYC documents on your side unless you have permission from the approriate authorities in your country
Parameters
UserId
string:
Maximum length is 255 characters
The object owner's UserId
Status
DocumentStatus:
CREATED, VALIDATION_ASKED, VALIDATED, REFUSED, OUT_OF_DATE
The Status
of the Document
The status of this KYC/Dispute document
RefusedReasonMessage
string:
Maximum length is 255 characters
The message accompanying a refusal
RefusedReasonType
KYCDocRefusedReasonType:
DOCUMENT_UNREADABLE, DOCUMENT_NOT_ACCEPTED, DOCUMENT_HAS_EXPIRED, DOCUMENT_INCOMPLETE, DOCUMENT_MISSING, DOCUMENT_DO_NOT_MATCH_USER_DATA, DOCUMENT_FALSIFIED, UNDERAGE_PERSON, SPECIFIC_CASE
The type of refusal reason
The type of reason for refusal
ProcessedDate
timestamp
The date when the document was processed by MANGOPAY