About Didit
Didit is the integrated proofing provider: TruU provisions the account, so the Proofing factor works the moment you make it Active. It performs document authenticity checks, selfie-to-document match, and liveness detection across a broad set of countries and document types. Didit acts as TruU’s subprocessor for this check. Use it to pilot proofing or to run production where a TruU-held vendor relationship is acceptable to your privacy program. Where you need the vendor to be your own processor, use Entrust, Persona, or PingOne Verify.What the connection enables
Nothing else about the user is sent. See Proofing for the full list of what crosses and what comes back.
Prerequisites
- An IDV Console account with the Owner or Admin role.
- End users on a phone with a camera (QR handoff from desktop is offered by default).
Get your credentials
None. The integrated provider is provisioned by TruU for your workspace. There is no key to generate and nothing to paste. If your organization already has its own Didit account and wants proofing to run under it, contact TruU; that is not configurable in the console today.Connect in TruU
Open Factors → Proofing and select Didit as the provider.
Validated at save: the configuration is well formed. Not validated at save: that the country list covers the documents your users hold.
Verifying the connection
Status appears on the factor configuration and in Credential health. Because the credentials are TruU’s, you cannot break this check; a failure means a provider issue on TruU’s side; contact support if it persists. Run one test verification on your own phone to confirm the end-to-end path.
How it works
Session. TruU creates a Didit session with the expected name and your accepted countries and shows Didit’s capture UI inside the verification page. The user photographs the document and records a short selfie. Didit returns the outcome, per-check results, extracted fields, and the selfie to TruU. Decision record and face extraction. As on every provider: the decision record is written to your write store or TruU managed storage; the verified selfie is deposited as a face reference when Proofing photo is on. See Proofing. Deletion on completion. TruU sends a delete request for the session as soon as the decision record is written, so Didit holds the document images and selfie only for the duration of the check plus the vendor’s deletion processing time. Retention. The durable artifacts are the ones TruU writes under your storage settings. Didit’s handling after a delete request is governed by TruU’s agreement with Didit; details are available on request. Hosts. TruU calls Didit’s API hosts only. The user’s browser loads the capture UI from Didit’s hosts; if your proxy blocks unknown domains for managed devices, see Network requirements.Gotchas and troubleshooting
- Desktop capture fails or loops. The most common proofing failure. Use the QR handoff to the phone.
- Users with uncommon documents fail at document selection. The issuing country is not in Document countries. Widen it, or add a fallback column that does not need proofing.
- Name match failures on passed documents. See the name matching notes on Proofing; lower Name match score or correct the directory.
- You need the vendor to be your own processor. Didit is TruU’s subprocessor in this model. Switch the factor to a bring-your-own provider; existing decision records are unaffected.
- Not validated at save. Country coverage.
Related pages
Proofing
Account models, what crosses to the vendor, the decision record.
Data handling
Retention and what is never stored.
Compliance
How to request the subprocessor list.

