User KYC/KYB verificationHosted KYC/KYBFlows per user type

Soletrader users

The page presents the user steps and validation checks for the hosted IDV flow for the Soletrader user type.

Prerequisites

Before launching a hosted IDV Session for a Soletrader, please ensure that:

  • The ID proof they will use is accepted by Mangopay
  • The Registration Proof they will upload conforms to the one expected by Mangopay
  • They have details about the registration of their sole proprietorship
  • The data in the following Legal User object fields matches their ID proof:
    • LegalRepresentative.FirstName
    • LegalRepresentative.LastName

Flow description

When a hosted IDV session is generated for a Legal Soletrader:

  1. The session Status is PENDING and can be submitted within 7 days, at which point it becomes EXPIRED
  2. The sole proprietor opens the session and sees a welcome screen explaining:
    • That they will need to provide business details
    • That they may need to provide the Registration Proof (RP) document (a link to the KYB local page is provided later in the flow)
    • That they will need to complete the liveness check with their ID and smartphone, with a link to Mangopay’s accepted ID documents
  3. The sole proprietor enters details of their sole proprietorship:
    • Country of registration
    • Optionally, registration number provided by the relevant national authority
    • Registered business name
    • Registered business address
  4. Mangopay uses business details to attempt a lookup in the relevant national registry (check type BUSINESS_VERIFICATION)
  5. Regardless of the result, the sole proprietor uploads their accepted Registration Proof
  6. The sole proprietor completes the liveness 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
  7. The session is redirected to the ReturnUrl
  8. Mangopay performs automated liveness validation checks:
    • IDENTITY_DOCUMENT_VERIFICATION
    • IDV_NAME_MATCH_CHECK
    • IDV_AGE_CHECK
  9. If successful, Mangopay checks that the name from the ID proof is present in the registered name (BUSINESS_NAME_MATCH).
    • If successful, the session’s status becomes VALIDATED
    • If unsuccessful, the session is reviewed manually (REVIEW) before the final outcome

Checks performed

For Soletrader Users, the following checks are performed in the order listed:

TypeDescription
BUSINESS_VERIFICATIONLooks up the business details entered by the user during the session in the national registry to find a match.
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 LegalRepresentative.FirstName and LegalRepresentative.LastName of the Legal user object.

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

Only performed if IDENTITY_DOCUMENT_VERIFICATION is successful.
BUSINESS_NAME_MATCHChecks whether the name on the identity document is present in the name of the registered sole proprietor in the relevant national registry.

Performed manually if BUSINESS_VERIFICATION is unsuccessful.

Outcomes

For a Soletrader 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:
    • LegalRepresentative.FirstName (even if the fields previously referenced a different individual)
    • LegalRepresentative.LastName
    • LegalRepresentative.Birthday
    • Name
    • CompanyNumber (if entered in the session)
  • 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

In this case:

  • You can retrieve more information in the IDV Session’s:
    • Checks.CheckStatus - For which checks were REFUSED
    • Checks.Reasons – For the refusal reasons (Type and preset Value)
  • You need to generate a new session to retry (even if some of the checks were validated)

Manual review

Provided the IDENTITY_DOCUMENT_VERIFICATION and IDV_AGE_CHECK are successful, the Status becomes REVIEW if either of the following checks fail:

  • BUSINESS_VERIFICATION
  • BUSINESS_NAME_MATCH

In this case:

  • Mangopay reviews the session data and documents manually.
  • The Checks.CheckStatus shows which checks were REFUSED and triggered the manual review
  • Automatically validated checks are returned, including verified data, but the User object data is only overwritten if the session is validated

Validation after review

If the manual review is successful, the Status changes from REVIEW to VALIDATED. In this case:

  • The verified data is overwritten in the User object:
    • LegalRepresentative.FirstName (even if the fields previously referenced a different individual)
    • LegalRepresentative.LastName
    • LegalRepresentative.Birthday
    • Name
    • CompanyNumber
  • The User’s KYCLevel becomes REGULAR

Refusal after review

If the manual review is unsuccessful, then the status changes to REFUSED.

In this case:

  • Verified data may be returned in the IDV Session but no action is taken with it
  • You can retrieve more information in the IDV Session’s:
    • Checks.CheckStatus - For which checks were REFUSED
    • Checks.Reasons – For the refusal reasons – Type and, in the case of a manual review, a custom message in the Value
  • You need to generate a new session to retry (even if some of the checks were validated)