API - August 18, 2026 | Mangopay docs

Added

Liveness checks for all PSCs (legal reps and UBOs) in hosted KYC/KYB for Business users

The hosted KYC solution for Business (and Organization and Partnership) Legal Users now supports sub-sessions for all individuals that must complete liveness checks: all Persons of Significant Control (PSCs), meaning every declared beneficial owner (UBO) owning 25% or more of the company, as well as every legal representative.

Each PSC now completes their own hosted verification – a PSC Session – independently of the main IDV Session and of other PSCs’ sessions. Your platform can view the list of PSCs, their hosted links, and their statuses via the PSCs array on GET View an IDV Session.

Read more about the multi-session PSC flow →

Platforms with existing integrations should refer to email communications for activation timelines. Contact Mangopay via the Dashboard to proactively request activation of the multi-session PSC flow for your platform.

Added

Endpoint to retry a PSC Session

In case a liveness check for a PSC fails or expires, your platform can retry it using a dedicated endpoint:

PUT Retry a PSC Session

Send an empty body ({}) to retry the liveness check using the PSC’s existing declared details, or provide updated details (first name, last name, email, date of birth) in the request body.

If the PSC’s Status is PENDING_VALIDATION, the existing session link is returned. If the PSC’s Status is VALIDATED or REJECTED, a new session link is generated. A PSC whose Status is ABANDONED cannot be retried.

Added

Webhook for hosted KYC/KYB expiry and PSC action pending

The following webhooks have been added for your platform to be notified about changes in the Status of the main IDV Session object:

Event type	Description
`IDENTITY_VERIFICATION_EXPIRED`	The IDV Session’s `Status` changed to `EXPIRED`, without being completed. By default, this happens 7 days after its `CreationDate`, but if the liveness step had been started (the QR code was generated), it happens 1 hour after the liveness step started instead. A new session is needed to retry.

For the multi-session PSC flow, the following event type has been added:

Event type	Description
`IDENTITY_VERIFICATION_PENDING_PSC_ACTION`	The IDV Session has one or more PSCs whose hosted verification link is ready to be completed. Use this event to retrieve each PSC’s `HostedUrl` from GET View an IDV Session and communicate it to them directly, if you don’t rely on Mangopay to email PSCs. The `RessourceId` is the `IdvSessionId`.

Read more about setting up webhooks or see the full list of event types →

Webhooks to support PSC Session state changes

For the multi-session PSC flow, the following event types have been added to track the Status changes of the PSCs objects. The RessourceId is the PscId.

Event type	Description
`IDENTITY_VERIFICATION_PSC_PENDING`	A PSC’s `Status` changed to `PENDING_VALIDATION`. This occurs when a PSC Session is created, retried, or recreated (for example, after a partial match against an existing PSC).
`IDENTITY_VERIFICATION_PSC_VALIDATED`	A PSC’s `Status` changed to `VALIDATED`.
`IDENTITY_VERIFICATION_PSC_REJECTED`	A PSC’s `Status` changed to `REJECTED`. This occurs if one or more checks failed, or if the PSC did not complete the verification within the allowed timeframe (by default 7 days after the PSC Session’s `CreationDate`, or 1 hour after the liveness step started if it had been started). Use the PUT Retry a PSC Session endpoint to generate a new session link for the PSC.
`IDENTITY_VERIFICATION_PSC_ABANDONED`	A PSC’s `Status` changed to `ABANDONED`. This action can only be performed by Mangopay, for example if the PSC was a duplicate of another declared PSC.

Read more about setting up webhooks or see the full list of event types →