> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mangopay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

export const Kyc = ({content}) => <Tooltip tip="Term used to refer to the identity verification of natural persons (i.e., individuals).">
        {content}
    </Tooltip>;

export const Kyb = ({content}) => <Tooltip tip="">
        {content}
    </Tooltip>;

export const Aml = ({content}) => <Tooltip tip="Regulations which require companies like Mangopay to implement measures that help ensure the money transacting through their system is legitimate.">
        {content}
    </Tooltip>;

The payment activity of your platform's users is subject to regulatory obligations. These obligations, often referred to as AML/CFT (for anti-money laundering and countering the financing of terrorism), are designed to prevent the misuse of the financial system for illegitimate purposes and protect your platform and users.

Mangopay applies [KYC/KYB limits](/guides/users/limits) to users on your platform as part of its compliance with these regulations. To exceed the limits, Mangopay must verify the identity of the user. This process is often referred to as KYC (know your customer) for individuals and KYB (know your business customer) for legal entities.

Mangopay provides a frontend web experience on which your Natural Users and Legal Users can complete all necessary steps.

<CardGroup cols={2}>
  <Card title="Hosted IDV for KYC/KYB" href="/guides/users/verification/hosted">
    Redirect users to complete verification
  </Card>
</CardGroup>

## Scope

You can only request verification for users whose `UserCategory` is `OWNER`. This means they have provided basic information and [enrolled in Mangopay's SCA](/guides/sca/users#enrollment-in-the-user-lifecycle).

When an `OWNER` User ([Natural](/api-reference/users/natural-user-object-sca) or [Legal](/api-reference/users/legal-user-object-sca)) has been successfully verified, their `KYCLevel` becomes `REGULAR` (instead of `LIGHT` by default). This allows them to exceed the [KYC/KYB limits](/guides/users/limits), for example by requesting payouts.

## Proactive Owner verification

In future, Mangopay will be requiring KYC/KYB verification earlier in the user journey for `OWNER` users. They will need to be verified **before** they start receiving funds on your platform.

KYC/KYB verification will be required for the following users:

* Pay-in – The credited user of a pay-in. This is the user holding the `CreditedWalletId` (but not the `AuthorId` initiating the payment)
* Transfer – Both the debited and credited users involved in a transfer. These are the holders of the `DebitedWalletId` and the `CreditedWalletId`

If any of these three users has `KYCLevel` of `LIGHT`, then the pay-in or transfer transaction will no longer be possible.

Mangopay will be introducing a new error message that will be returned:

* `ResultCode` – 002951
* `ResultMessage` – Beneficiary OWNER user(s) not KYC verified (KYCLevel is not REGULAR): UserId

This restriction will also apply in the case of a KYC downgrade or during renewal – at any moment that the User’s `KYCLevel` is `LIGHT`.

##### Anticipate integration

The introduction of KYC/KYB verification for `OWNER` users before they can receive funds will require your platform to integrate Mangopay's [hosted IDV redirection](/guides/users/verification/hosted) during your user's onboarding journey.