Retry a PSC Session
Retry a PSC Session based on its Id. Send an empty body ({}) to use the existing details declared for the individual and only retry the liveness check, or else send updated details 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. To add a missing PSC, contact Mangopay via the Dashboard, who will create the new PSC and provide you with a session link.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.
Path parameters
Request
Unix timestamp (UTC) of the date of birth of the PSC.
Response
Unix timestamp (UTC) of the date of birth of the PSC.
The country of the PSC (ISO 3166-1 alpha-2 format).
The nationality of the PSC (ISO 3166-1 alpha-2 format).
The type of the PSC:
LEGAL_REP– The PSC is a legal representative only.LEGAL_REP_AND_UBO– The PSC is both a legal representative and a beneficial owner.UBO– The PSC is a beneficial owner only.
The status of the PSC session:
PENDING_VALIDATION– The PSC session link has been generated and is awaiting completion.VALIDATED– The PSC session was validated.REJECTED– One or more checks failed, or the PSC did not complete the verification within the allowed timeframe. By default, the PSC Session expires 7 days after itsCreationDate, but if the PSC’s liveness step has been started (the QR code was generated), it expires 1 hour after the liveness step started instead.ABANDONED– The PSC session was abandoned by Mangopay, for example if it was a duplicate of another declared PSC.
Unix timestamp (UTC) of the date and time the object was created.
Unix timestamp (UTC) of the date and time the PSC session was validated. Returns null if not yet validated.