Skip to main content
This page is for the admin who already runs Persona and wants TruU IDV proofing to use the tuned configuration there. When you finish, the Proofing factor creates inquiries on your Persona template and Persona is your processor.

About Persona

Persona runs identity verification as inquiries against templates you configure in the Persona dashboard: which documents to accept, which checks to run, and what thresholds to apply. Connecting your account lets TruU IDV open an inquiry per proofing attempt and read the result, while the inquiry, its documents, and the selfie stay in your Persona account.

What the connection enables

TruU never lists or reads other inquiries in your account and never edits templates.

Prerequisites

  • A Persona account with API access and an inquiry template that includes a government ID verification and a selfie verification.
  • Someone who can create an API key in the Persona dashboard.
  • An IDV Console account with the Owner or Admin role.
  • Outbound HTTPS from TruU to Persona’s API host (TruU’s side).

Get your credentials

1

Create an API key

In the Persona dashboard, go to API → API keys and create a key for the production environment. Copy it; it is shown once. Use a dedicated key for TruU.
2

Copy the inquiry template ID

Open Inquiries → Templates, choose the template TruU should use, and copy its ID (it starts with itmpl_). The template must be active.
The template should accept name fields as prefilled inputs; TruU prefills first and last name and nothing else.

Connect in TruU

Open Factors → Proofing, select Persona as the provider, and enter: These are the only two values the console asks for. After connecting, Match sensitivity sets how precisely the name on the document must match the directory name, and Match date of birth and Match address can require those document fields to match a directory attribute you name. Then set the common proofing settings described on Proofing. Validated at save: the key authenticates and the template ID resolves. Not validated at save: that the template’s verifications match what your flow expects, or that your Persona plan has volume.

Verifying the connection

A wrong template ID shows up only when a verification starts, so run one test verification on your phone and confirm the inquiry appears in your Persona dashboard with your name.

How it works

Session. TruU creates an inquiry on your template with the expected name prefilled and opens Persona’s embedded flow in the verification page or hands it to the phone by QR. When the inquiry completes, TruU reads its status and the verification results. What Persona holds. The inquiry, documents, selfie, and verification reports, in your account under your retention settings. TruU does not delete inquiries; use Persona’s redaction and retention controls. 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. Hosts. TruU only ever calls Persona’s API host. The user’s browser loads the embedded flow from Persona’s hosts. Secrets. The API key is held in a managed secrets service. Rotate it by pasting a new key; the superseded value is deleted. Changes are audited.

Gotchas and troubleshooting

  • Credential check passes, template check fails. The template belongs to a different Persona environment than the key, or it is inactive.
  • Inquiry completes in Persona but the TruU request does not pass. The template’s decision was “needs review” or the name match failed in TruU. The request detail shows which.
  • Template asks the user for fields TruU already knows. Mark name fields as prefilled in the template so users are not asked to type them again.
  • Desktop capture fails. Use the phone handoff; see Proofing.
  • Key rotated in Persona, not in TruU. Proofing fails at inquiry creation until the new key is pasted in. Credential health shows the failing check.
  • Not validated at save. Template contents, plan volume, and your Persona retention settings.

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.