> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# PingOne Verify

> Run TruU IDV document and selfie proofing through your own PingOne Verify environment: environment ID, worker app client credentials, region, the health checks, and how results are polled.

This page is for the admin whose organization runs PingOne and wants proofing under that contract. When you finish, the Proofing factor creates PingOne Verify transactions in your environment and PingOne is your processor. For resetting PingOne MFA devices after a verification, see [PingOne MFA reset](https://docs.truu.ai/idv/connect/pingone-mfa.md); the two connections are independent.

## About PingOne Verify

PingOne Verify is Ping Identity's document and selfie verification service, configured through verify policies in your PingOne environment. Connecting it lets TruU IDV start a verify transaction for each proofing attempt, pass the expected name as a requirement so PingOne's own comparison works, and collect the result.

## What the connection enables

| Capability | What TruU reads | What TruU writes |
| - | - | - |
| Document and selfie proofing | Transaction status, verification results, extracted document fields, selfie | A verify transaction with the expected name as a requirement |
| User mapping | An existing PingOne user when directory lookup mapping is selected | A throwaway PingOne user per session when ephemeral mapping is selected |

## Prerequisites

* A PingOne environment with PingOne Verify licensed and a verify policy configured (document and selfie, liveness as you require).
* A PingOne worker application with the **Identity Data Admin** role on the environment.
* An IDV Console account with the Owner or Admin role.
* Outbound HTTPS from TruU to PingOne's API host for your region (TruU's side).

## Get your credentials

**1. Note the environment ID and region**

In the PingOne admin console, open **Environment → Properties**. Copy the environment ID and note the region the environment lives in.

**2. Create a worker application**

Under **Applications**, add a **Worker** application dedicated to TruU. On its **Roles** tab, grant the **Identity Data Admin** role scoped to this environment. That role lets TruU read your verify policies, create verify transactions and, with ephemeral users, create and delete users in the population. Copy the client ID and client secret from the **Configuration** tab; the secret is shown once.

**3. Pick the verify policy**

Under **Experiences → Verify policies**, make sure the verify policy you want exists. You pick it in TruU after connecting.

## Connect in TruU

Open **Factors → Proofing** and select **PingOne Verify** as the vendor. To connect, enter:

| Field | Format | Notes |
| - | - | - |
| **Environment ID** | UUID | |
| **Worker Client ID** | UUID | The worker application |
| **Worker Secret** | String | Shown once by PingOne. Stored in a managed secrets service, never returned |

After connecting, set:

| Field | Options | Notes |
| - | - | - |
| **PingOne region** | com (North America, the default), eu, asia, ca | Set this first if your environment isn't in North America; it selects the API host |
| **Verify policy** | One of your PingOne verify policies | Loaded live from your environment. This is the first real call to PingOne, so a list that loads proves the credentials, region and role work |
| **User resolution** | **Ephemeral (create & delete per verification)** (default) or **Existing PingOne directory user** | Ephemeral creates a throwaway PingOne user per verification and removes it afterwards. The other option matches the verified person to an existing PingOne identity |
| **Directory lookup attribute** | **External ID** (default) or **Username** | For existing users only; the PingOne attribute the match uses |
| **Population ID** | PingOne population UUID | Optional, ephemeral users only. Leave it empty to use the environment's default population |

Of the common [Proofing](https://docs.truu.ai/idv/factors/proofing/overview.md) settings, **Phone camera only** and the storage options apply to PingOne Verify; document and matching rules come from your verify policy.

**Not validated at connect:** that the credentials work (the Verify policy list is the first check) or that the verify policy's document and country rules cover what your people hold.

## Test it

1. Confirm the **Verify policy** list loads and pick your verify policy.
2. Run one verification on your phone with the Proofing factor and confirm the transaction appears under the environment's Verify activity in PingOne.

## How it works

**Session.** TruU resolves or creates the PingOne user, creates a verify transaction with the expected name as a requirement, and presents PingOne's capture experience in the verification page or hands it to the phone by QR.

**Polling, not webhooks.** TruU polls the transaction status until it reaches a terminal state. You do not configure a webhook or callback in PingOne, and TruU does not need an inbound path from PingOne. Results appear on the verification request within a few seconds of the transaction completing.

**What PingOne holds.** The transaction, documents, selfie, and verification results, in your environment under your contract. With ephemeral mapping the throwaway user is deleted after the session; with directory lookup the transaction is attached to the existing user.

**What TruU holds.** The decision record in your write store or TruU managed storage, and the selfie as a face reference when **Proofing photo** is on. See [Data handling](https://docs.truu.ai/idv/security/data-handling.md).

**Hosts.** TruU only ever calls PingOne's API and auth hosts for your region. The user's browser loads the capture experience from PingOne's hosts.

**Secrets.** The client secret is held in a managed secrets service. Rotate it by pasting a new secret; the superseded value is deleted. Changes are audited.

## Gotchas and troubleshooting

* **The Verify policy list doesn't load.** The region doesn't match the environment, the secret is wrong, or the worker app has no role in this environment.
* **The Verify policy list is empty.** The worker app is missing the **Identity Data Admin** role, or the environment has no verify policy yet.
* **Ephemeral verifications fail to start.** The worker role can't create users, or the population ID is wrong.
* **Directory lookup cannot find the user.** No PingOne user matches the verified user's attribute. Switch to ephemeral mapping, or align the attribute.
* **Transaction completes in PingOne but the request stays on the proofing step for a while.** Polling interval. Wait a few seconds; if it never completes, the transaction ended in a state TruU does not treat as terminal and the request detail shows the raw status.
* **Desktop capture fails.** Use the phone handoff; see [Proofing](https://docs.truu.ai/idv/factors/proofing/overview.md).
* **Secret rotated in PingOne, not in TruU.** Proofing fails at session creation until the new secret is pasted in.
* **Not validated at save.** Verify policy rules and PingOne licensing or volume.

## Related pages

> [card] [Proofing](https://docs.truu.ai/idv/factors/proofing/overview.md)
>
> Common settings, name matching, and the decision record.

> [card] [PingOne MFA reset](https://docs.truu.ai/idv/connect/pingone-mfa.md)
>
> The separate connector for resetting MFA devices after success.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.