Skip to main content
This page is for the admin who already has an Entrust (Onfido) identity verification contract and wants proofing to run under it. When you finish, the Proofing factor runs on your Entrust workflow and Entrust is your processor, not TruU’s.

About Entrust (Onfido)

Entrust Identity Verification (the former Onfido platform) performs document authenticity, facial similarity, and liveness checks through configurable workflows in Onfido Studio. Connecting your account lets TruU IDV start a workflow run for each proofing attempt and collect the result, while document images, selfies, and the applicant record stay in your Entrust account.

What the connection enables

TruU never reads other applicants or reports in your account, and never changes your workflows.

Prerequisites

  • An Entrust (Onfido) account with API access in one region and a published workflow in Onfido Studio that includes document and facial similarity (and liveness if you require it).
  • Someone who can create an API token on the Entrust side.
  • An IDV Console account with the Owner or Admin role.
  • Outbound HTTPS from TruU to Entrust’s API host for your region (TruU’s side).

Get your credentials

1

Create an API token

In the Entrust (Onfido) dashboard, go to Settings → Developers → Tokens and create a live token. Copy it; it is shown once. Use a dedicated token for TruU so it can be revoked independently.
2

Note your region

The region your account was created in: US, EU, or CA. A token works only against its region’s API host.
3

Copy the workflow ID

In Onfido Studio, open the workflow you want TruU to run and copy its ID. The workflow must be published; drafts cannot be run.
Allow the workflow’s input to be an applicant with first and last name only; TruU does not supply other applicant fields. If the workflow has a document country or type restriction, keep it consistent with your allowlists in TruU.

Connect in TruU

Open Factors → Proofing, select Entrust as the provider, and enter: Then set the common proofing settings described on Proofing. Validated at save: the token authenticates in the selected region and the workflow ID exists. Not validated at save: that the workflow’s outputs include the checks you expect, or that your Entrust account has volume remaining.

Verifying the connection

Results show on the factor configuration and in Credential health, at save, on demand, and in a daily sweep. Then run one test verification on your phone and confirm the run appears in your Entrust dashboard under the applicant with your name.

How it works

Session. For each proofing attempt TruU creates an applicant (first and last name from your directory), starts a workflow run on your workflow ID, and embeds Entrust’s capture UI in the verification page or hands it to the phone by QR. On completion TruU reads the run’s outcome and the report outputs. What Entrust holds. The applicant, the workflow run, the document images, the selfie or video, and the reports, all in your account under your contract and retention settings. TruU does not delete them; use Entrust’s retention controls. What TruU holds. The decision record (outcome, check results, extracted fields, raw response) in your write store or TruU managed storage, and the selfie as a face reference when Proofing photo is on. See Data handling. Certifications. For Entrust’s own security and compliance attestations, see Entrust’s trust documentation. TruU does not restate them. Hosts. TruU only ever calls Entrust’s API host for your selected region. The user’s browser loads the capture UI from Entrust’s hosts. Secrets. The API token is held in a managed secrets service. Rotate it by pasting a new token on the factor configuration; the superseded value is deleted. Changes are audited.

Gotchas and troubleshooting

  • Credential check fails with an authentication error. The token belongs to a different region than the one selected, or it is a sandbox token. Match the region to where the account lives.
  • Verifications fail to start. The workflow is a draft, or the ID was copied from a different environment. Publish it in Studio and copy the ID from the published version.
  • Runs start but every one fails before capture. The workflow’s document restrictions exclude what users hold, or the workflow expects applicant fields TruU does not send (for example date of birth as a required input). Relax the workflow input requirements.
  • Desktop capture fails. Use the phone handoff; see Proofing.
  • Results are “needs review” more often than with the integrated provider. Your workflow’s thresholds decide this, not TruU. Tune them in Studio.
  • Token rotated in Entrust, not in TruU. Proofing fails at session creation until the new token is pasted in. Credential health shows the failing check.
  • Not validated at save. Workflow outputs, account volume, and retention settings in your Entrust account.

Proofing

Common settings, name matching, and the decision record.

Credential health

Where the checks above appear.

Data handling

What TruU stores versus what stays with your vendor.