Skip to main content
For a Natural User, the hosted IDV solution presents the user with the liveness check.

​
Prerequisites

Before launching a hosted IDV Session for a Natural User, please ensure that:
  • The ID proof they will use is accepted by Mangopay
  • The data in the following Natural User object fields matches their ID proof:
    • FirstName
    • LastName

​
Flow description

When a hosted IDV session is opened for a Natural User:
  1. The session Status is PENDING and is valid for 24 hours
  2. The user opens the session and sees a welcome screen explaining:
    • That they will need to complete the liveness check with their ID and smartphone, with a link to Mangopay’s accepted ID documents
  3. User completes live ID check (via QR code or directly if session opened on a phone) by:
    • Taking a photo of their ID (or two photos if it’s a driver’s license or national ID card)
    • Taking a selfie of their face
  4. The session is redirected to the ReturnUrl
  5. Mangopay performs automated liveness validation checks:
    • IDENTITY_DOCUMENT_VERIFICATION
    • IDV_NAME_MATCH_CHECK
    • IDV_AGE_CHECK

​
Checks performed

For Natural Users, the following checks are performed in the order listed:
TypeDescription
IDENTITY_DOCUMENT_VERIFICATIONVerifies the authenticity of the identity document, the liveness of the selfie, and that the selfie matches the identity document photo.
IDV_NAME_MATCH_CHECKChecks whether the first name and last name of the identity document match the FirstName and LastName of the Natural user object.

Only performed if IDENTITY_DOCUMENT_VERIFICATION is successful.
IDV_AGE_CHECKChecks whether the individual on the identity document meets the minimum age requirement for Mangopay users (age 18).

Only performed if IDENTITY_DOCUMENT_VERIFICATION is successful.

​
Outcomes

For a Natural User, the following outcomes are possible (from a PENDING status):

​
Automated validation

The Status becomes VALIDATED if all automated checks performed were successful. In this case:
  • The verified data is overwritten in the User object:
    • FirstName
    • LastName
    • Birthday
  • The User’s KYCLevel becomes REGULAR

​
Automated refusal

The Status becomes REFUSED if any of these checks fail:
  • IDENTITY_DOCUMENT_VERIFICATION
  • IDV_NAME_MATCH_CHECK
  • IDV_AGE_CHECK
A manual review is not possible for a Natural user.