Skip to main content
The stage of the payments workflow is highly regulated. Mangopay has legal obligations to verify the identity of users who wish to pay money out to their bank account. For more information about the precise KYC/KYB limits that apply to unverified users of your platform, see the KYC/KYB limits article. The obligations placed on payments companies like Mangopay are designed to prevent the misuse of the financial system for illegitimate purposes. The rules imposed are referred to as .

​
Scope

To request identity verification, a User must have the UserCategory of OWNER. The OWNER category requires the user to provide additional basic information and enroll in Mangopay’s SCA. To be verified, an Owner user must provide at least one official document as evidence of the information they have declared. The documents provided by the user are examined by Mangopay for authenticity and consistency with the information the user has declared. Once a user’s required documents have been validated, they receive verified status. When verified, the User object’s KYCLevel parameter has the value REGULAR instead of LIGHT (value by default). With the REGULAR status, the user can exceed the KYC/KYB limits (typically, for example, by requesting a payout). Verification is available for all user types, but the required information and documents are different for Natural Users and Legal Users. For details, see:

KYC/KYB requirements

Verification requirements depending on user type

​
Integration

Mangopay provides a hosted frontend experience that lets you redirect your user to complete their verification at an appropriate moment in your user journey. The session allows the user to input all necessary data, upload documents, and complete a liveness check against their ID.
Note - Hosted KYC/KYB verification mandatory for new platformsPlatforms integrating with Mangopay for the first time are required to integrate Mangopay’s hosted KYC/KYB experience, relying on the POST Create an IDV Session endpoint.

Integrate hosted KYC/KYB sessions

Redirect users to complete their verification
In addition to the hosted solution, platforms may in some cases need to send static files of additional documents to Mangopay for their users. These files must be sent via the API in the form of a KYC Document object. There are two Types of object that you may need to use:
  • IDENTITY_PROOF - For any additional ID documents requested
  • ADDRESS_PROOF - For any other additional documents requested that aren’t ID proofs (i.e. even if it’s not an address proof either)
For more guidance on integrating these endpoints, see information about document submission guide and how to submit a KYC document. For platforms using the hosted experience, integration of the UBO Declaration endpoints is not necessary, as these individuals can be declared by the user through the frontend session.