Signals & Checks

Every session is assessed across these families at once and ends in one result. Each family below names the checks that back it. What each check decides, and when it appears in a result, is defined once in Session Results.

Device

The browser and connection the capture came from, assessed before the first capture. The device signals detect automated sessions, tampered browser environments and identifications replayed from another session. Which of them count against a session is set for your tenant — ask your Inyo contact. Widget flow only: a server-to-server verification has no browser, so neither row appears there.

Checks: device_identification_valid · device_risk_clear

Geography

Where the connection comes from — whether it is routed through a VPN, a proxy, an anonymising network or a hosting provider — is read as part of the device assessment, through device_risk_clear. There is no separate location check. The document's issuing country is checked against the jurisdictions you accept, when you restrict them.

Checks: jurisdiction_accepted · device_risk_clear

Identity data

The identity fields read off the document — name, date of birth, document number — and, when you send prefill, how they compare with the data you hold. The fields arrive in the result's person and document blocks.

Checks: document_readable · document_data_match

Documents and DMV records

Whether the document is a genuine physical document of the type declared, in date, with a number that fits its issuer — and, for a US driver's license, whether the issuing DMV's record agrees with it.

Checks: document_authentic · document_scene_clear · document_portrait_present · document_type_match · document_not_expired · document_number_valid · dmv_record_match

Phone and carrier

The phone number you send: the kind of line it is on, and whether it is registered to the person the document identifies. Neither check runs without a phone number in the request.

Checks: phone_line_type · phone_identity_match

MRZ and barcode

The machine-readable data a document carries — a passport's zone, a US license's barcode — checked on its own terms and against what the document's face prints.

Checks: document_mrz_valid · document_barcode_valid · document_sources_agree

Designated lists

The name read from the document, screened against the OFAC Specially Designated Nationals list. A name match counts only when the listing's date of birth also agrees.

Checks: sanctions_clear

Biometrics and liveness

The selfie: one usable face, a live person rather than a reproduction, and the same person as the document portrait. Optionally, an age consistent with the document's date of birth.

Checks: face_detected · liveness · face_match · age_match

Decisioning

Every check's outcome feeds one trustIndex from 0 to 100. Under managed decisioning Inyo360 also reaches a decision: approved, declined, inconclusive, or in_review while a person looks at it — see Manual Review. Under non-managed decisioning, the default, decision is absent and you decide from the checks and the trust index.

Checks: capture_attempts