idvSessions

View an IDV Session

Changed on

See details of a hosted KYC/KYB session, outcome of checks, and verified data. For a Business User on the multi-session PSC flow, this also returns the PSCs array with each declared PSC's own status and hosted link.

Read more about hosted KYC/KYB →

get/v2.01/{ClientId}/identity-verifications/{IdvSessionId}

Request

  • Base URL
    https://api.sandbox.mangopay.com
  • URL
    https://api.sandbox.mangopay.com/v2.01/{ClientId}/identity-verifications/{IdvSessionId}
  • Auth
    HTTP bearer

Path parameters

ClientIdstring required

Platform's API account identifier, associated with the API key.

IdvSessionIdstring required

The unique identifier of the IDV Session.

Response

Success

Idstring

Max length: 128 characters (see data formats for details)

The unique identifier of the object.

Tagstring

Max. length: 255 characters

Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: "{\"id_1\":AB123,\"id_2\":DE456}".

HostedUrlstring

The URL to redirect the user to for the hosted identity verification session.

ReturnUrlstring

The URL to which the user is returned after the hosted identity verification session, regardless of the outcome.

Statusstring

The status of the overall IDV Session:

  • PENDING – Session created. The HostedUrl is valid for completion, regardless of whether the user has started or submitted the session.
  • REVIEW – One or more automated checks was neither successful nor refused, so the session was sent for manual review by Mangopay's teams. This temporary state is only applicable to Legal users and can transition to REFUSED or VALIDATED.
  • VALIDATED – - The session was validated and the User became KYC/KYB verified (indicated by the User object's KYCLevel). When the Status changes to VALIDATED, the verified data in Checks.Data is used to replace existing data in the User object.
  • REFUSED – The session was refused and the User is not KYC/KYB verified. The Checks.CheckStatus shows which checks were REFUSED and the Checks.Reasons shows the refused reason types and comment (which is custom text in the case of manual review for Legal users).
  • EXPIRED – The IDV Session expired and can no longer be used. By default, this happens 7 days after the CreationDate. However, if the IDV Session contains the liveness step and that step has been started (the QR code was generated), the session instead expires 1 hour after the liveness step started. The IDV Session contains the liveness step for Natural users, Soletrader users, and Business/Organization users on the legacy integrated flow. In the multi-session PSC flow, the main IDV Session never contains the liveness step (so it always follows the 7-day rule) – the liveness check is performed in each PSC Session instead, which follows the same 7-day/1-hour rule independently.
  • OUT_OF_DATE – The IDV Session is not valid because the user's KYC/KYB verification status was downgraded by Mangopay.
UserIdstring

The unique identifier of the user.

CreationDateinteger

Unix timestamp (UTC) of the date and time the object was created.

LastUpdateinteger

Unix timestamp (UTC) of the date and time the session was last updated.

Changes

  • f44a59c76515Revision changes
    • warning

      deleted the header request parameter Authorization

    • info

      the endpoint scheme security oauth2 was added to the API

  • 8e731ec4a85bRevision changes
    • info

      api operation id view_idv_session removed and replaced with idvSessions_view_idv_session