> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# API - August 18, 2026

## 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](/api-reference/idv-sessions/view-idv-session).

Read more about the [multi-session PSC flow](/guides/users/verification/hosted/business) **→**

Platforms with existing integrations should refer to email communications for activation timelines. Contact Mangopay [via the Dashboard](http://hub.mangopay.com/) 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](/api-reference/idv-sessions/retry-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](/api-reference/idv-sessions/idv-session-object) object:

<table>
  <tr>
    <th class="header">
      Event type
    </th>

    <th class="header">
      Description
    </th>
  </tr>

  <tr>
    <td class="table-content">
      `IDENTITY_VERIFICATION_EXPIRED`
    </td>

    <td class="table-content">
      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.
    </td>
  </tr>
</table>

\


For the [multi-session PSC flow](/guides/users/verification/hosted/business), the following event type has been added:

<table>
  <tr>
    <th class="header">
      Event type
    </th>

    <th class="header">
      Description
    </th>
  </tr>

  <tr>
    <td class="table-content">
      `IDENTITY_VERIFICATION_PENDING_PSC_ACTION`
    </td>

    <td class="table-content">
      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](/api-reference/idv-sessions/view-idv-session) and communicate it to them directly, if you don't rely on Mangopay to email PSCs. The `RessourceId` is the `IdvSessionId`.
    </td>
  </tr>
</table>

\


Read more about [setting up webhooks](/webhooks) or see the full list of [event types](/webhooks/event-types) **→**

### Webhooks to support PSC Session state changes

For the [multi-session PSC flow](/guides/users/verification/hosted/business), the following event types have been added to track the `Status` changes of the `PSCs` objects. The `RessourceId` is the `PscId`.

<table>
  <tr>
    <th class="header">
      Event type
    </th>

    <th class="header">
      Description
    </th>
  </tr>

  <tr>
    <td class="table-content">
      `IDENTITY_VERIFICATION_PSC_PENDING`
    </td>

    <td class="table-content">
      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).
    </td>
  </tr>

  <tr>
    <td class="table-content">
      `IDENTITY_VERIFICATION_PSC_VALIDATED`
    </td>

    <td class="table-content">
      A PSC's `Status` changed to `VALIDATED`.
    </td>
  </tr>

  <tr>
    <td class="table-content">
      `IDENTITY_VERIFICATION_PSC_REJECTED`
    </td>

    <td class="table-content">
      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](/api-reference/idv-sessions/retry-psc-session) endpoint to generate a new session link for the PSC.
    </td>
  </tr>

  <tr>
    <td class="table-content">
      `IDENTITY_VERIFICATION_PSC_ABANDONED`
    </td>

    <td class="table-content">
      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.
    </td>
  </tr>
</table>

\


Read more about [setting up webhooks](/webhooks) or see the full list of [event types](/webhooks/event-types) **→**