> 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 - November 4, 2026

## Changed

### PSC Sessions created only after the main session is validated

On the [multi-session PSC flow](/guides/users/verification/hosted/business), PSC Sessions are now created only once the main IDV Session's `Status` becomes `VALIDATED` (automatically, or following manual review) — not as soon as the end-user submits the main session.

Once the main session is `VALIDATED`, Mangopay generates PSC Sessions for all PSCs and sends notification emails (unless your platform has opted to manage the initial communication).

The `PSC_ROLE_CHECK` and `PSC_CONSISTENCY_CHECK` checks still run on the main session before this point, based on the declared PSC data. If the main session is `REFUSED` or remains in `REVIEW`, no PSC Session is created.

This change only impacts the timing of the PSC Session creation, to help avoid potential issues arising from inconsistencies in the PSC declaration if the main session has to be retried.

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

---

## Added

### List PSC Sessions for a User endpoint

Retrieve all PSC Sessions declared for a user directly, independently of the main IDV Session under which they were declared.

[GET List PSC Sessions for a User](/api-reference/idv-sessions/list-psc-sessions-user) returns each PSC Session's `Status` and `HostedUrl`, its declared `Data`, and the `MainSessionId` of the IDV Session under which the PSC was declared.

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

---

## Added

### Mock to simulate IDV Session outcomes in Sandbox

[POST Create an IDV Session](/api-reference/idv-sessions/create-idv-session) now supports a Sandbox-only mock to force a session directly to a given `Status`, without completing the hosted flow.

Set the `Tag` parameter to `VALIDATED`, `REFUSED`, `REVIEW`, or `EXPIRED` (case-insensitive) to force the session to the corresponding `Status`. Any other value, or an empty `Tag`, follows the normal flow.

[Read more about testing hosted KYC/KYB sessions](/guides/users/verification/hosted/business#testing) **→**