---
title: "View an IDV Session"
method: GET
path: "/v2.01/{ClientId}/identity-verifications/{IdvSessionId}"
tags: ["idvSessions"]
---

# View an IDV Session

`GET /v2.01/{ClientId}/identity-verifications/{IdvSessionId}`

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](/guides/users/verification/hosted) **→**

## Path parameters

- `ClientId` string, required
- `IdvSessionId` string, required

## Headers

- `Authorization` string, required

## Response `200`

Success

- ViewAnIDVSessionResponse
  - `Id` string — Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
  - `Tag` string — Max. length: 255 characters Custom data that you can add to this object.
  - `HostedUrl` string — The URL to redirect the user to for the hosted identity verification session.
  - `ReturnUrl` string — The URL to which the user is returned after the hosted identity verification session, regardless of the outcome.
  - `Status` string — 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](/guides/users/verification/hosted/natural#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](/guides/users/verification/hosted/refusals) 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](/guides/users/verification/downgrade) by Mangopay.
  - `UserId` string — The unique identifier of the user.
  - `CreationDate` integer — Unix timestamp (UTC) of the date and time the object was created.
  - `LastUpdate` integer — Unix timestamp (UTC) of the date and time the session was last updated.
  - `Checks` ViewAnIdvSessionResponseChecksItems[], nullable — The checks performed automatically during the session. This array is empty when `Status` is `PENDING` and may contain any number of objects depending on the outcome.
    - `CheckId` string — The unique identifier of the verification check.
    - `Type` string — Type of check carried out during the session depending on the user type: * `IDENTITY_DOCUMENT_VERIFICATION` - Verifies the authenticity of the identity document, the liveness of the selfie, and that the selfie matches the identity document photo. * `IDV_AGE_CHECK` - Checks whether the individual on the identity document meets the minimum age requirement for Mangopay users (age 18). * `BUSINESS_VERIFICATION` - Looks up the business details entered by the user during the session in the national registry to find a match. * `IDV_NAME_MATCH_CHECK` - Checks whether the first name, last name and date of birth of the identity document match the `FirstName`, `LastName`, and `Birthday` of the Natural user object or `LegalRepresentative` of the Legal user object. * `BUSINESS_NAME_MATCH` - Checks whether the name on the identity document is present in the name of the registered sole proprietor in the relevant national registry. * `BUSINESS_INSIGHTS_MATCH` - Checks whether the name on the identity document matches one of the directors listed in the national registry, and whether the PSC data declared in the session is coherent with the PSC data in the registry. * `PSC_ROLE_CHECK` - For Business, Organization, and Partnership Users, ensures the PSC form declares at least one UBO and at least one legal representative (a single PSC can hold both roles). Performed on every session, regardless of the business registry lookup outcome. * `PSC_CONSISTENCY_CHECK` - For Business, Organization, and Partnership Users, compares the PSC form against the business registry data and checks that any business-type PSC's ownership structure is adequately documented. Only performed if the business registry lookup found a match. For information on which checks are performed for which user type and in which cases, see the dedicated guides: [Natural](/guides/users/verification/hosted/natural), [Soletrader](/guides/users/verification/hosted/soletrader), [Business and Organization](/guides/users/verification/hosted/business).
    - `CheckStatus` string — **Returned values:** `VALIDATED`, `REFUSED` The status of the verification check.
    - `Reasons` ViewAnIdvSessionResponseChecksItemsReasonsItems[] — The reasons that the check was refused, which may be returned if `CheckStatus` was `REFUSED` (depending on the check type).
      - `Type` string — The type of the reason. For more details, see [refusals](/guides/users/verification/hosted/refusals).
      - `Value` string — The explanation of the reason. If the refusal was automatic, this is a preset string. For Legal users, if the refusal follows a manual review, this is a custom explanation from the person who conducted the review.
    - `CreationDate` integer — Unix timestamp (UTC) of the date and time the check was created.
    - `LastUpdate` integer — Unix timestamp (UTC) of the date and time the check was last updated.
    - `Data` ViewAnIdvSessionResponseChecksItemsDataItems[] — The data extracted and verified during the check. This array may be empty if no data was extracted or is not applicable for the check.
      - `Type` string — The type of the data. For a Natural user: * `FIRST_NAME` * `LAST_NAME` * `BIRTHDATE` For a Legal user: * `COMPANY_NAME` * `COMPANY_NUMBER` * `LEGAL_REPRESENTATIVE_FIRST_NAME` * `LEGAL_REPRESENTATIVE_LAST_NAME` * `LEGAL_REPRESENTATIVE_BIRTHDATE`
      - `Value` string, nullable — The value of the data. The value may be `null` or an empty string if data extraction was not possible but the check was still carried out.
  - `PSCs` ViewAnIdvSessionResponsePsCsItems[], nullable — The list of persons of significant control (PSCs) declared during the session. Only returned if the multi-session PSC flow is activated for `BUSINESS` and `ORGANIZATION` Legal Users. This array is empty or `null` when not applicable.
    - `Id` string — The unique identifier of the PSC.
    - `Status` string — The status of the PSC verification: - `PENDING_VALIDATION` – The PSC verification is ongoing. - `VALIDATED` – The PSC 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 the PSC's `CreationDate`, 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 verification was abandoned by Mangopay, for example if it was a duplicate of another declared PSC.
    - `HostedUrl` string — The URL to redirect the PSC to for the hosted verification session.
    - `CreationDate` integer — Unix timestamp (UTC) of the date and time the PSC was created.
    - `LastUpdate` integer — Unix timestamp (UTC) of the date and time the PSC was last updated.
    - `Data` ViewAnIdvSessionResponsePsCsItemsDataItems[] — The data associated with the PSC.
      - `Type` string — The type of the data, depending on the `PSC_TYPE` declared in the session. Individual: - `FIRST_NAME` - `LAST_NAME` - `PSC_TYPE` Business: - `PSC_LEGAL_REPRESENTATIVE_FIRST_NAME` - `PSC_LEGAL_REPRESENTATIVE_LAST_NAME` - `BUSINESS_PSC_NAME` - `PSC_TYPE`
      - `Value` string, nullable — The value of the data.

---

[API](https://skmtc.dev/mangopay/apis/api-reference.md) · [All operations](https://skmtc.dev/mangopay/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mangopay/api-reference/revisions/fafbd0c69654/schema)