View an IDV Session
See details of a hosted KYC/KYB session, outcome of checks, and verified data
Path parameters
The unique identifier of the IDV Session.
Responses
200
200
Max length: 128 characters (see data formats for details)
The unique identifier of the object.
Max. length: 255 characters
Custom data that you can add to this object.
The URL to redirect the user to for the hosted identity verification session.
Max. length: 500
The URL to which the user is returned after the hosted identity verification session, regardless of the outcome.
The status of the overall IDV Session:
PENDING
– The uniqueHostedUrl
for the session has not yet been submitted by the user. This temporary state can transition toVALIDATED
,REFUSED
, orREVIEW
.REVIEW
– One or more automated checks was neither successful nor refused, so the session was sent for manual review by Mangopay’s teams. This temporary state is only applicable to Legal users and can transition toREFUSED
orVALIDATED
.VALIDATED
– - The session was validated and the User became KYC/KYB verified (indicated by the User object’sKYCLevel
). When theStatus
changes toVALIDATED
, the verified data inChecks.Data
is used to replace existing data in the User object.REFUSED
– The session was refused and the User is not KYC/KYB verified. TheChecks.CheckStatus
shows which checks wereREFUSED
and theChecks.Reasons
shows the refused reason types and comment (which is custom text in the case of manual review for Legal users).OUT_OF_DATE
– The session is not valid because the user’s KYC/KYB verification status was downgraded by Mangopay.
The unique identifier of the user.
The date and time at which the object was created.
The date and time at which the session was last updated.
The checks performed automatically during the session.
This array is empty when Status
is PENDING
and may contain any number of objects depending on the outcome.