Changed
PSC Sessions created only after the main session is validated
On the multi-session PSC flow, 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 →
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 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 →
Added
Mock to simulate IDV Session outcomes in Sandbox
POST Create an 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.