Glossary
The words the console uses, in the sense the console means them
Most of these have an everyday meaning as well. This is what they mean here.
People and attempts
Applicant is the person being verified. They never see the console.
Verification, also called a session, is one attempt: created, run, finished with a verdict.
Attempt is the same thing, used when counting. "Attempt 2 of 3" means this person has tried three times and you are looking at the second.
Person is our best assembly of the attempts that belong to the same human, built from the identity on their documents, the face in their captures, and the identifiers your integration sent.
Outcomes
Status is where a session stands: pending, processing, approved, rejected, manual review, or expired.
Verdict is what the checks concluded: approve, reject, or review. A session whose verdict is review keeps that verdict after a person decides it, while its status becomes approved or rejected.
Score is the overall figure for the session, shown as a percentage.
Finding, sometimes shown as a reason code, is a specific thing a check noticed, such as a photograph of a screen or a name in a script the machine-readable zone does not share. Findings are always recorded, so an approved verification still tells you what was noticed about it.
Decided by says what settled the case: our engine, your automatic policy, a reviewer, or something outside this console.
Configuration
Flow is the ordered set of checks an applicant goes through, plus its branding and what it accepts.
Check is one step inside a flow: document, liveness, face match, age estimation, screening, proof of address, phone, email verification.
Required and optional describe a step. A required step that fails fails the verification; an optional one is recorded without failing anything by itself.
Sensitivity is how readily borderline results are held back for a person instead of being decided automatically. It moves the uncertain middle and never declines anybody on its own.
Default flow is the one that runs when a verification is created without naming a flow.
Engine tier is which of our verification engines your account runs on.
Review
Case is a verification waiting for a human decision.
Claim is taking a case from the queue so it is yours to decide. It lasts for a set period, the lease, and returns to the queue if you never finish.
Assignment is a case being given to somebody, by a person or automatically.
Escalation is a reviewer saying they cannot honestly decide, and passing the decision to an owner or a review manager.
Automatic decisions settle cases from the score, at thresholds you set, without a person.
Internal note stays in the console for your team. Message to the applicant is what they read.
Edit (applicant data) changes the identity fields the engine extracted, by hand, without re-running a check or changing any decision. Every edit is kept as a new version, and an edited record is marked Modified.
Reprocess re-reads the document images we already hold and replaces the stored fields. It does not change the status, the verdict or the score.
Access
Role is the preset that decides what somebody reaches. Permission, or capability, is one individual switch inside it.
Environments on a seat are whether that person can open sandbox, live, or both. It is the only thing gating real applicant data.
Flow access narrows a seat to specific flows, hiding every verification, person and review case outside them.
Step-up is the request for a code from your authenticator app before a sensitive action goes through.
Reveal is decrypting an applicant's identity to look at it. Every reveal is recorded against your name.
Integration
Sandbox is the test environment, driven by magic values that produce whatever outcome you ask for. Live is real applicants.
API key is the secret your servers use. Test keys work in sandbox, live keys in live.
Webhook endpoint is a URL of yours that we post events to. Delivery is one such post, event is what it carries, and the signing secret is what lets you prove it came from us.
Idempotency key lets a receiver recognise a repeated delivery and drop it rather than acting twice.
White-label means the verification flow runs on your own domain, under your own branding, with nothing of ours on it.
Fraud network is the cross-account signal that the same face or identity has been seen elsewhere. Details belonging to other organizations are never shown to you, and yours are never shown to them.