> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mangopay.com/guides/users/verification/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server. # User KYC/KYB verification ## Docs - [KYC/KYB restriction changes and pay-in beneficiaries](https://docs.mangopay.com/guides/payin-beneficiaries.md): Understand the KYC/KYB restrictions on transfers and pay-ins, and how to declare verified Owners as beneficiaries of pay-ins - [KYC/KYB limits on payouts and user balance](https://docs.mangopay.com/guides/users/limits.md): Read about the KYC/KYB limits on payouts and wallet balance that are applicable under Mangopay's Payment Services (EEA) and Electronic Money Services (UK) - [All requirements by user type](https://docs.mangopay.com/guides/users/verification/requirements.md) - [Accepted identity documents](https://docs.mangopay.com/guides/users/verification/requirements/id-accepted.md): See all information required for individuals and the specific ID documents accepted depending on the country of issue. - [Accepted local KYB documents](https://docs.mangopay.com/guides/users/verification/requirements/kyb-local.md) - [Hosted IDV for KYC/KYB](https://docs.mangopay.com/guides/users/verification/hosted.md): Integrate Mangopay's web-hosted KYC/KYB verification solution - [Natural users](https://docs.mangopay.com/guides/users/verification/hosted/natural.md): UX steps, validation flows, and outcomes of the hosted IDV flow for Natural Users - [Soletrader users](https://docs.mangopay.com/guides/users/verification/hosted/soletrader.md): UX steps, validation flows, and outcomes of the hosted IDV flow for Legal Soletrader users - [Multi-session PSC flow for Legal Users](https://docs.mangopay.com/guides/users/verification/hosted/business.md): UX steps, validation flows, and outcomes of the hosted IDV flow for Legal Business, Organization, and Partnership users - [Business - Legacy single-session flow](https://docs.mangopay.com/guides/users/verification/hosted/business-legacy.md): Details of the legacy single-session flow for Business users, where a single legal representative is verified within the main session - [Organization - Legacy single-session flow](https://docs.mangopay.com/guides/users/verification/hosted/organization-legacy.md): Details of the legacy single-session flow for Organization users, where a single legal representative is verified within the main session - [Dealing with hosted KYC/KYB refusals](https://docs.mangopay.com/guides/users/verification/hosted/refusals.md) - [KYC/KYB renewal](https://docs.mangopay.com/guides/users/verification/renewal.md): How KYC/KYB verification affects users on an ongoing basis - [Verification downgrade](https://docs.mangopay.com/guides/users/verification/downgrade.md): Learn about the verification downgrade mechanism, the scenarios triggering a downgrade, and hook notifications for changes. - [Document submission process](https://docs.mangopay.com/guides/users/verification/documents/submission.md): Learn about Mangopay’s KYC/KYB document validation process: submission steps, constraints, and dealing with refusals. - [Document types](https://docs.mangopay.com/guides/users/verification/documents/types.md): Learn about types of KYC/KYB document with Mangopay: which are required for natural and legal users, plus submission constraints and guidelines. - [How to submit a KYC Document](https://docs.mangopay.com/guides/users/verification/documents/submission/how-to.md): Step-by-step guide to submitting verification (KYC/KYB) documents: uploading files, managing outcomes, and setting up webhooks. - [Identity proof best practices](https://docs.mangopay.com/guides/users/verification/documents/submission/id-best-practices.md): See best practices for submitting identity proof documents and errors to avoid to ensure that the document can be read and validated. - [Dealing with refusals](https://docs.mangopay.com/guides/users/verification/documents/submission/refusals.md): - [Company number](https://docs.mangopay.com/guides/users/verification/company-number.md): Manage the company numbers of legal users effectively, and see all expected formats per country, to accelerate the KYB verification process. - [Beneficial owners](https://docs.mangopay.com/guides/users/verification/beneficial-owners.md): Learn about disclosing beneficial owners for Mangopay users: required information and documents, submission process, and dealing with refusals. - [How to submit a UBO Declaration](https://docs.mangopay.com/guides/users/verification/beneficial-owners/how-to.md): Step-by-step guide to submitting beneficial owner (UBO) declarations of beneficial owners, including managing outcomes and setting up webhooks. > **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mangopay.com/guides/users/verification/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server. # Introduction 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 restrictions and limits to users on your platform as part of its compliance with these regulations. To services, Mangopay must verify the identity of the user. The identity verification process involves checking data about a user against evidence, such as official ID documents and selfies. In the case of legal entities, the process involves business data and documents and multiple individuals. Mangopay's system of [user types](/guides/users/types) exists to differentiate between the processes that must be applied. These processes are often referred to as KYC (know your customer), and for legal entities the term KYB (know your business customer) may also be used. The KYC/KYB verification topic can be broken down into the following sections: * Restrictions and limits enforced, based on [API attributes](#user-attributes) and your platform's [contractual status](#platforms-contractual-status) * [Requirements per user type](/guides/users/verification/requirements) regarding the evidence needed * Mangopay's [hosted KYC/KYB](/guides/users/verification/hosted) solution, which your platform must integrate for all user types > **Check** > > **Best practice - Check Mangopay's user types and local KYB guidance** > > The nature of your user base, especially for legal entities or sole proprietors, determines the [user type](/guides/users/types) they need in Mangopay’s system, and therefore the KYC/KYB process required. > > For a wide number of countries, Mangopay lists the [local legal structures](/guides/users/verification/requirements/kyb-local) that should be onboarded under the relevant type. > > Ensure you are familiar with the guidelines for the markets in which your users are based. #### Proactive Owner verification For EEA platforms contracted with Mangopay S.A. (using Payment Services), the restrictions applicable to pay-ins and transfers changed as of **July 1, 2026**. Existing integrations should refer to email communications for implementation timelines. The new restrictions applicable to new integrations, mean that an `OWNER` whose `KYCLevel` is `LIGHT` can no longer: * Receive a transfer to a wallet they hold (as the holder of the transfer's `CreditedWalletId`) * Receive a pay-in to a wallet they hold (as the holder of the pay-in's `CreditedWalletId`) **unless** the pay-in has `FlowDescriptor.Beneficiaries` declared **and all** declared beneficiaries are verified Owners (`KYCLevel` is `REGULAR`) or `PLATFORM` users The optional `FlowDescriptor.Beneficiaries` property on pay-ins therefore serves to declare the target owners of the pay-in under the new restrictions. For more information about the changes, refer to the [dedicated guide](/guides/payin-beneficiaries) **→** UK-based platforms contracted with Mangopay U.K. Ltd. (using Electronic Money Services) are not impacted. ## Scope The application of KYC/KYB verification is governed by API attributes of the user object. Your platform's contractual status with Mangopay determines the restrictions and limits that are applied. ### User attributes KYC/KYB verification is governed by API attributes of the user object. For more information about the differentiation between Payer and unverified Owners, see the [categories](/guides/users/categories) guide.
User attribute Description
`UserCategory` `PAYER` by default or can become `OWNER` when the user: * Provides additional data in the User object * Enrolls in [Mangopay’s hosted SCA](/guides/sca/users) * Accepts Mangopay’s T\&Cs An `OWNER` can request KYC/KYB verification.
`KYCLevel` `LIGHT` by default (and for `PAYER`) and becomes `REGULAR` when the user: * Successfully completes the KYC/KYB verification process The `KYCLevel` can be downgraded from `REGULAR` to `LIGHT` by Mangopay for two reasons: * Non-renewal as per the [periodic renewal](/guides/users/verification/renewal) process * A change of [key identity data](/guides/users/verification/downgrade) in the User object A downgraded `OWNER` is subject to the same restrictions and limits as one who has not yet been verified. If the User’s `KYCLevel` is `LIGHT`, the restriction applies.
\ ### Platform’s contractual status The limits that are applicable to your users differ depending on: * Where your platform is registered (EEA or UK) * Which Mangopay entity your platform contracts with (Mangopay S.A. or Mangopay UK Ltd.) * Which kind of Mangopay services you use (Payment Services (PS) or Electronic Money Services (EMS)) These factors are all defined at the start of your partnership with Mangopay by your platform's contractual agreement. Mangopay offers one of two kinds of services to platforms: * **Payment Services (PS)** as Mangopay S.A. to platforms registered in the EEA * **Electronic Money Services (E-Money Services, EMS)** as Mangopay U.K. Ltd. to platforms registered in the UK Mangopay S.A. is an EMI under Luxembourg law, authorized by the CSSF. Mangopay U.K. Ltd. is an EMI under UK law, authorized by the FCA. Read more about [Mangopay's EMI status](/guides/glossary#electronic-money-institution-emi).