> ## 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.

# Proofing

> How document and selfie proofing runs in TruU IDV: the integrated provider, bring-your-own Entrust, Persona, or PingOne Verify for production, what TruU sends the vendor, what comes back, the decision record, name and DOB matching, document allowlists, and face extraction.

This page is for the admin choosing a proofing provider and the privacy reviewer asking what leaves TruU during a document check. When you finish, you will know which account model fits, exactly what crosses to the vendor, and what is written where.

## About proofing

Document and selfie proofing captures a government-issued ID, matches it against a live selfie, and checks liveness. In TruU IDV it is one factor, Proofing, used in [flows](https://docs.truu.ai/idv/build/flows.md) like any other. The user completes capture on their own phone through the verification page; no app install.

The check itself runs on a vendor. TruU supports two account models:

| Model | Provider | Who holds the vendor contract | Typical use |
| - | - | - | - |
| Integrated provider | [Didit](https://docs.truu.ai/idv/factors/proofing/didit.md) | TruU provisions it; no credentials to enter | Getting started, and production where a TruU-held vendor relationship works for you |
| Bring your own account | [Entrust (Onfido)](https://docs.truu.ai/idv/factors/proofing/entrust.md), [Persona](https://docs.truu.ai/idv/factors/proofing/persona.md), [PingOne Verify](https://docs.truu.ai/idv/factors/proofing/pingone-verify.md) | You; the vendor is your processor | Production, where your privacy program needs a direct vendor relationship |

You choose the provider per Proofing factor configuration in **Factors**, so an onboarding flow and a help desk flow can use different providers or settings.

## What the connection enables

| Capability | What TruU reads from the vendor | What TruU writes to the vendor |
| - | - | - |
| Start a proofing session | A session reference and a capture URL or token | The expected name from your directory (given and family name), the allowed document types and countries, and a session reference. Nothing else about the user |
| Collect the result | Outcome, per-check results, fields extracted from the document, and the selfie | Nothing |
| Delete the session (integrated provider) | Confirmation | A delete request on completion |

TruU does not send the user's email, phone, employee ID, address, directory photo, or any other attribute to the vendor. The expected name is the only identity input, and it is used for the name match.

## Prerequisites

* An IDV Console account with the Owner or Admin role.
* For bring-your-own: an account with the vendor, a configured workflow or template on their side, and API credentials. See the vendor page for the exact values.
* End users need a phone with a camera. Desktop webcams can complete capture but fail often; the verification page offers a QR handoff to the phone by default.

## Get your credentials

Depends on the provider.

| Provider | Credentials | Where to get them |
| - | - | - |
| Didit | None | TruU provisions the account |
| Entrust (Onfido) | API token, region, workflow ID | [Entrust page](https://docs.truu.ai/idv/factors/proofing/entrust.md) |
| Persona | API key, template ID | [Persona page](https://docs.truu.ai/idv/factors/proofing/persona.md) |
| PingOne Verify | Environment ID, worker client ID and secret, region | [PingOne Verify page](https://docs.truu.ai/idv/factors/proofing/pingone-verify.md) |

All vendor credentials are shown once, stored in a managed secrets service, and never returned by any API.

## Settings

Open **Factors → Proofing**. Choose the **Proofing vendor** first; vendor-specific fields are on each vendor page.

![Proofing settings panel with Didit selected as the vendor, Phone camera only, score sliders, Document countries and What is stored](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/factor-proofing-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=aaa162e6e90d0b374480bf4ae968edca)

| Setting | What it does | Default |
| - | - | - |
| **Proofing vendor** | **Didit** (recommended, no keys), **PingOne Verify**, **Persona** or **Entrust (Onfido)** | Didit |
| **Phone camera only** | Desktop users scan a QR code and finish on their phone; the computer's camera isn't offered. Didit and PingOne Verify. | Off |
| **Name match score** (Didit) | How closely the name on the document must match your directory | 75% |
| **Liveness score** (Didit) | How confident the liveness check must be that a real person is present | 60% |
| **Face comparison score** (Didit) | How closely the selfie must match the document photo | 55% |
| **Document countries** (Didit) | **All countries** or **Specific countries**. Photo IDs only; non-photo IDs are never accepted. | All countries |
| **Attempts per run** (Didit) | Failed checks allowed before the factor fails | 3 tries |

**Reset to recommended** restores the three scores. For PingOne Verify, Persona and Entrust, document and matching rules are set in your vendor account; see each vendor page.

### What is stored

| Option | What it keeps | Default |
| - | - | - |
| **Proofing photo** | The selfie from a passed check, used later as the employee's [Face](https://docs.truu.ai/idv/factors/face.md) reference. **Edit path** sets where it is written. | On in new workspaces |
| **Decision record** | One JSON file per decision: scores, identity fields, warnings | On |
| **Store capture videos** | ID front and back clips and active-liveness video | Off |
| **Store capture images** | ID document stills, the liveness reference frame and face-match images | Off |

**Store** picks where these files go: the TruU managed store or one of your own (**Add store**). **Store this photo separately** sends the Proofing photo to a different store from the decision records. ID images and liveness video otherwise stay with the vendor.

> [!WARNING]
>
> Capture images and video are biometric data. What you store has to match what your consent notice tells employees is kept. See [Data handling](https://docs.truu.ai/idv/security/data-handling.md).

### Directory matching and decline rules

* **Date of birth and address matching:** **Match date of birth** and **Match address** compare the document with the value in your directory or, with an [HR system](https://docs.truu.ai/idv/connect/hr/overview.md) connected, in HR. Choose the source for each. Address matching isn't offered for Entrust, whose document check returns no address.
* **Require active employment:** with an HR system connected, fails verification when HR shows the person as inactive or has no record of them.
* **When HR can't answer:** checks that read HR fail open. If HR is down or disconnected, they're skipped and the verification continues; TruU doesn't fall back to your directory. See [When HR is unavailable](https://docs.truu.ai/idv/connect/hr/overview.md#when-hr-is-unavailable).
* **Decline rules:** how Didit treats specific findings, such as expected-details mismatch, invalid MRZ, inconsistent data, multiple faces or a duplicated face. These are set in Didit and shown here for reference.

## Verifying the connection

[Credential health](https://docs.truu.ai/idv/admin/credential-health.md) checks the vendor credentials daily and on demand:

| Vendor | What's checked |
| - | - |
| Didit | The workspace's credentials and its verification workflow |
| Persona | The API key authenticates |
| Entrust | The API token authenticates |
| PingOne Verify | Not checked; the **Verify policy** list loading is the live check |

A test verification on a phone is the real check: confirm the request shows **Verified** with Proofing in the column it used, and that a decision record appears in your store.

## How it works

**Session.** TruU creates a session with the vendor and hands the user to the vendor's capture UI inside the verification page (or by QR to the phone). The vendor performs document authenticity, selfie match, and liveness. When the session completes, TruU collects the result.

**What comes back.** Outcome (pass, fail, or needs review), the result of each check, the fields extracted from the document (name, date of birth, document number, expiry, issuing country, document type), and the selfie image. TruU does not receive biometric templates.

**Name matching.** TruU compares the extracted name against the expected name from your directory with a fuzzy comparison that tolerates accents, hyphenation, middle names, name order, and common transliterations. A failed name match fails the factor even when the vendor passed the document.

**Date of birth match (optional).** When on, the extracted DOB must equal the mapped directory attribute. Most directories do not hold DOB; leave it off unless coverage is high.

**Decision record.** With **Decision record** on, TruU writes a record of the outcome, each check's result, the name match result, and the fields read from the document when the check completes. It goes to your write store if you have one under [Your stores](https://docs.truu.ai/idv/connect/storage.md), otherwise to TruU managed storage partitioned for your organization. The verification request carries the outcome and the record's reference; consoles show confidence bands, not raw scores.

**Face extraction.** With **Proofing photo** on, the selfie from a passed check is stored as the user's face reference (in your write store or TruU managed storage). Later verifications can then use the Face factor without a directory photo. Proofing-derived references match better than most directory photos, which are often old or small.

**Vendor session deletion.** For the integrated provider, TruU deletes the session on the vendor side after the decision record is written. For bring-your-own providers the session stays in your vendor account under your contract.

**Hosts.** TruU calls only the vendor's API hosts for the provider you selected; see each vendor page. The user's browser loads the vendor's capture UI from the vendor's hosts.

## Gotchas and troubleshooting

* **Desktop capture loops on "move closer" or "move further", or the camera never starts.** Webcams and pages rendered in a mobile layout on desktop fail capture frequently. Use the QR handoff to the phone; it succeeds where the desktop did not. Tell agents to recommend the phone by default.
* **Camera is unavailable on the Windows lock screen.** Expected. The phone handoff is the path there.
* **Name match fails for a user the vendor passed.** The directory name is a preferred name, an initial, or includes a suffix the document does not. Loosen the name match setting for your provider, or fix the directory value. The request detail shows both names.
* **Every session fails before capture.** The accepted documents or countries do not cover what the user holds, or the vendor workflow has its own restrictions that conflict with yours. Loosen one side.
* **Needs review outcomes pile up.** The vendor returned an inconclusive result (glare, cropped document, expired ID). Ask the user to retry with a clear, uncropped photo of a valid document.
* **Face factor still unavailable after proofing.** **Proofing photo** is off, or the proofing check did not pass. Only passed checks deposit a reference.
* **Not validated at save.** TruU does not check that your vendor account has volume or that the workflow accepts the documents your users hold.

## Related pages

> [card] [Didit](https://docs.truu.ai/idv/factors/proofing/didit.md)
>
> The integrated provider.

> [card] [Entrust (Onfido)](https://docs.truu.ai/idv/factors/proofing/entrust.md)
>
> Bring your own Entrust account.

> [card] [Persona](https://docs.truu.ai/idv/factors/proofing/persona.md)
>
> Bring your own Persona account.

> [card] [PingOne Verify](https://docs.truu.ai/idv/factors/proofing/pingone-verify.md)
>
> Bring your own PingOne environment.

> [card] [Data handling](https://docs.truu.ai/idv/security/data-handling.md)
>
> What is stored from proofing and where.

> [card] [Storage](https://docs.truu.ai/idv/connect/storage.md)
>
> Where the decision record and face reference are written.


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