Guide

How to review verifications, run compliance checks & generate applicant links

01 — Getting in

Signing in

The console is at https://admin.idntory.com. Sign in with your firm slug and your firm password.

/admin/login
The sign-in screen: a Firm field, a Password field, and a Sign in button.
Put your firm slug (e.g. northwind) in Firm and your password below it.

A session lasts 7 days. Sign out is in the top-right of every page.

Three tries

After 3 failed sign-ins from one network address, that address is blocked from signing in — with no on-screen notice; the form keeps saying “Incorrect password”. If you fat-finger your password a few times and then can't get in even when it's right, you've been blocked — contact your idntory administrator to clear it.

02 — The verifications list

The verifications list

This is the landing page. Every completed verification appears here, newest first, with the person's name, country, document type, the system's verdict, and a confidence score.

/admin/list
The verifications list: a filter row above a table of verification rows with coloured verdict badges.
Click any row to open the full record.

Filtering & search

status
Verified / not verified.
document
Passport, national ID, driver's licence, residence permit.
country
Start typing and pick from the list — a partial code is ignored.
date range
Submitted between two dates.
search
Matches the person's name, the document number, or your user_ref. Typing here also shows a quick jump-to-record dropdown.

Press Filter to apply. Paging controls are at the bottom.

What the verdict badge means

Green is a pass, red is a fail, amber is a pass with a caveat. The exact words come from the pipeline's combined verdict:

BadgeVerdictMeaning
passpassDocument, face and (where present) MRZ all matched cleanly.
mrz face passmrz_face_passNo reference image on file for this document, but the MRZ and the face both checked out.
face only passface_only_passFace matched; no document or MRZ check was possible.
pass mrz warnpass_mrz_warnPassed, but the MRZ had a non-fatal warning. Worth a look.
both weakboth_weakDocument and face both matched weakly — needs a human decision.
face ai mismatchface_ai_mismatchThe two face models disagreed — a strong fraud signal.
mrz unreadablemrz_unreadableAn MRZ zone was found but couldn't be parsed or checksummed.
mrz tamperedmrz_tamperedMRZ check digits didn't validate.
liveness failliveness_failThe selfie frames failed the anti-spoof check.
failfailNothing matched.

Only pass, mrz_face_pass, face_only_pass and pass_mrz_warn count as verified. Anything else that reaches a person also gets a second-opinion review by Claude before it lands here.

03 — Reading a verification

Reading a verification

A record has six tabs. Overview is the summary; the rest are the evidence behind the verdict.

/admin/detail — Overview
The Overview tab: summary cards for verdict, score, country, document type and submission time, then the extracted identity fields.
Summary up top, then Extracted identity — the name, date of birth, document number, issue and expiry dates the system read off the document.
/admin/detail — Overview (captured images)
The Captured images section showing the ID document and two selfie frames as thumbnails, with a Compare frames button.
Further down: the captured images — the document and the selfie / liveness frames. Compare frames puts the document photo and a selfie side by side. (Images shown here are demo placeholders.)

Model Scores

Each leg of the check, with the model that produced it. A score tagged heuristic fallback came from a simpler method, not the full model — weight it accordingly.

/admin/detail — Model Scores
The Model Scores tab: face match, liveness, document match and MRZ validation each as a card with a percentage and a match label.
Face match (ArcFace), liveness, document match (reference-image comparison) and MRZ checksum validation, side by side.

MRZ Checksums & Printed vs MRZ Cross-Check

For documents with a machine-readable zone: the MRZ Checksums tab shows each ICAO check digit passing or failing. Printed vs MRZ Cross-Check puts the text the OCR read off the front of the document next to the text encoded in the MRZ, so a mismatch (a sign of tampering) is obvious.

Forensics & EXIF Check

Tamper heuristics on the document image — camera metadata, Error Level Analysis, and named risk flags like missing_exif or an editing-tool signature. A review verdict here means “look closer”, not “reject”.

/admin/detail — Forensics & EXIF Check
The Forensics tab: a REVIEW verdict, EXIF metadata fields, Error Level Analysis scores, and a list of risk flags.
Here the image has no EXIF metadata and a raised ELA score — both flagged under Risk flags.

PEP & Sanctions Checklist

The screening run on the extracted name against global politically-exposed-person, sanctions and adverse-media lists.

/admin/detail — PEP & Sanctions Checklist
The PEP tab: subject name, a POTENTIAL_MATCH risk badge, a match profile card, and the list of databases checked.
A POTENTIAL_MATCH shows the matched profile, the confidence, and which lists it came from. Databases checked confirms every source was queried even when nothing matched.

04 — Making a decision

Approve, reject, correct

The action buttons sit in the top-right of a record: Your name, Edit values, Reject, Approve.

  1. Put your name in the Your name box — it's stamped onto the record as the reviewer. (Named team members are filled in automatically.)
  2. Read the evidence tabs. Pay attention to any amber or red leg.
  3. If the system misread a field, click Edit values, fix it, and save. Your correction is stored as an overlay — the original machine reading is kept untouched for audit.
  4. Click Approve or Reject. The record is marked reviewed and shows a Reviewed by … badge from then on.
Overrides

Approving a record the system failed (or rejecting one it passed) is allowed and expected — that's the point of human review. Both the system's verdict and your decision are kept on the record.

05 — Removing records

Deleting & restoring

Delete is a soft delete: the record greys out and can be Restored for 24 hours, after which it is permanently purged automatically. Deleting a record removes its images from storage too. Generated links follow the same 24-hour soft-delete rule.

07 — Checks without a verification

Ad-hoc checks

Three tools for checking someone or something that isn't going through the full capture flow. Each keeps its own audit log and never touches the verifications list.

PEP & Sanctions Check person

Screen a name against the same PEP / sanctions / adverse-media lists the pipeline uses. No document needed.

/admin/screen
The PEP and Sanctions Check form: first name, surname, optional date of birth and nationality, and a Run screen button.
Add a date of birth or nationality to sharpen the match.

KYB company

The same idea for a business — screen a company name against sanctions and adverse-media lists, with optional jurisdiction and registration number.

/admin/kyb
The KYB form: company name, optional jurisdiction and registration number, and a Run screen button.
Results use the same match-profile cards as the person screen.

Document Authenticity Check document

Upload a document on file and run the forensics, reference-match / MRZ, and a PEP screen on the name — without a selfie or liveness step. For checking a document you already hold, not onboarding a live person.

/admin/document-check
The Document Authenticity Check form: document type, issuing country, front and back file uploads, and a Run check button.
Passports run MRZ validation; cards run reference-image matching plus OCR. Both run the tamper forensics.