The Verified Identity object
Description
Note – Feature activation required
The GET View a User’s Verified Identity endpoint requires an access token with the underwriting.user.kyc read permission. Contact Mangopay to request access.
The Verified Identity object contains information that Mangopay obtained during the customer due diligence process.
The payload returned depends on the user’s UserType:
NATURAL– The verified personal identity of the user and their documents.LEGAL_BUSINESS,LEGAL_ORGANIZATION,LEGAL_PARTNERSHIP,LEGAL_SOLETRADER– The verified company information, the legal representative, and, where available, the persons with significant control (PSCs) and their documents.
Use the UserType to determine which payload is returned, rather than the presence of an optional property. Identity properties can be returned null, and the Documents, LegalRepresentatives, and Pscs arrays can be empty, even for a user whose KYC/KYB verification is validated, because the data available depends on the verification received for that user.
Caution – Document URLs expire
The DocumentUrls of each document are signed URLs generated when the endpoint is called, and they grant access for a limited validity period only. Download the document before the URL expires, and call the endpoint again to obtain a new URL if you need access afterwards.
Do not cache, persist, or share DocumentUrls, and do not use them as document identifiers.
Attributes
Response if the user's UserType is NATURAL.
Identity properties can be returned null even for a user whose KYC/KYB verification is validated, because the data available depends on the verification received for that user.
Response if the user's UserType is LEGAL_BUSINESS, LEGAL_ORGANIZATION, LEGAL_PARTNERSHIP, or LEGAL_SOLETRADER.
Identity properties can be returned null even for a user whose KYC/KYB verification is validated, because the data available depends on the verification received for that user.