--- title: Reviewing and managing verification description: "View or manage a user's ID verification results." component: pingone page_id: pingone:identity_verification_using_pingone_verify:p1_verify_managing_verification canonical_url: https://docs.pingidentity.com/pingone/identity_verification_using_pingone_verify/p1_verify_managing_verification.html llms_txt: https://docs.pingidentity.com/pingone/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: April 7, 2026 page_aliases: ["p1_verify_view_status.adoc", "p1_verify_manually_approve_id.adoc"] section_ids: viewing-user-id-verification-results: Viewing user ID verification results steps: Steps steps-2: Steps choose-from: Choose from: manually-approving-a-users-id: Manually approving a user's ID steps-3: Steps steps-4: Steps result: Result --- # Reviewing and managing verification You can view a user's ID verification results and manually approve the most recent verification transaction for a user using the PingOne admin console or the PingOne Verify REST API. Reviewing user ID verification results allows you to audit compliance, troubleshoot failed verification attempts, and maintain security oversight. Although automated verification handles most checks, you can manually approve a user's most recent verification transaction if an automated check requires human intervention, such as resolving a borderline photo match or a minor data mismatch. You can perform these actions using either the PingOne admin console or the PingOne Verify REST API. ## Viewing user ID verification results You can view a user's ID verification results in the PingOne admin console or through the PingOne Verify REST API. > **Collapse: Admin console** > > ## Steps > > 1. In the PingOne admin console, go to **Directory > Users** and browse or search for the user you want to view. > > 2. Click the user entry to open the user details panel. > > 3. In the user details panel, go to **Services** > **ID Verification** to view the verification status and results for the user. > > For each **Transaction ID**, the status of the user ID verifications, including a timestamp and the result, is displayed. > > The **Status** can have one of the following values: > > | Status | Definition | > | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | > | **Requested** | The user is requested to send their ID information for verification. | > | **Initiated** | The user receives the link to the verify transaction, or scans a QR code, and clicks **Begin Verification** within their mobile web browser or mobile app using the PingOne Verify SDK. | > | **In progress** | The user successfully captures and submits a document image. The ID verification service receives the ID information and attempts to validate the data with the service provider (SP). | > | **Partial** | At least one step of the verification process is complete, but some steps are pending. For example, an end user has shared their government ID images but hasn't taken their selfie. | > | **Success** | The user ID information has been validated by the service provider and verified by the ID verification service. | > | **Approved manually** | The user ID information has bypassed the verification process and been approved manually with admin-assisted verification. This happens after the document collection process has begun. | > | **Approved no request** | The verification transaction is manually approved without the user starting the document collection process. | > | **Fail** | The user ID information went through validation, and a service provider failed it because of detected fraud, an unsupported document, or bad image quality.A **Fail** status can also occur when:- The user doesn't initiate or complete the document collection process. This causes the verification transaction to expire and change the status to **Fail**. > > - An internal error occurs during processing. | > > 4. Click **View** to view the metadata **Result** for a specific transaction ID. > **Collapse: API** > > ## Steps > > * Use the PingOne Verify REST API to make one of the following requests: > > ### Choose from: > > ``` > GET /environments/{envID}/users/{userID}/verifyTransactions > ``` > > Returns all changes (transactions) in verification status for the user. Learn more in [Read all ID verification transaction records for a user](https://developer.pingidentity.com/pingone-api/verify/verify-transactions/read-all-verify-transactions.html) in the API documentation. > > ``` > GET /environments/{envID}/users/{userID}/verifyTransactions/{transactionID} > ``` > > Returns a specific change (transaction) in verification status for the user. Learn more in [Read an ID verification transaction record for a user](https://developer.pingidentity.com/pingone-api/verify/verify-transactions/read-one-verify-transaction.html) in the PingOne API documentation. ## Manually approving a user's ID If automated user ID verification fails for any reason or you need a user to bypass the automated verification process, you can manually approve a user's ID. Manual approval allows the user to bypass the automated verification process and instead use admin-assisted verification. In this case, you can rely on a custom-defined identity verification process such as in-person or video-based conferencing to verify users. You can manually approve a user's ID in the PingOne admin console or through the PingOne Verify REST API. > **Collapse: Admin console** > > ## Steps > > 1. In the PingOne admin console, go to **Directory > Users** and browse or search for the user you need to approve. > > 2. Click the user entry to open the user details panel. > > 3. In the user details panel, go to **Services** > **ID Verification** to view the verification details for the user. > > 4. Click **View** on the appropriate verification transaction. > > This opens the transaction metadata. > > 5. Click **Manually Approve**. > > ![A screen capture of ID verification metadata](_images/verifymetadata.png) > > | | | > | - | -------------------------------------------------------------------------------------------------------------------------------------------------------- | > | | The **Manually Approve** option isn't available for the following transaction statuses:- **Approved manually** > > - **Success** > > - **Approved no request** | > **Collapse: API** > > ## Steps > > * Use the PingOne Verify REST API to make the following request: > > ``` > PUT /environments/{envID}/users/{userID}/verifyTransactions/{transactionID} > ``` > > Learn more in [UPDATE an ID verification transaction record for a user](https://developer.pingidentity.com/pingone-api/verify/verify-transactions/update-verify-transaction.html) in the PingOne API documentation. ## Result The user ID is verified, and the user can register or sign on from their device.