Overview
Identity matching compares the candidate (the person being screened) against the subject found in a criminal record. Each identity field is independently evaluated and assigned a match status, then weighted to produce an overall score that determines the identity level used for routing.Match Statuses
Every field comparison produces one of the following statuses:Field-Level Matching Rules
Name
Name matching comparesfirst_name, last_name, and optionally middle_name between the candidate and the record subject. Aliases are also considered.
Date of Birth (DOB)
DOB is compared component by component: year (YYYY), month (MM), and day (DD).SSN (Social Security Number)
SSN matching is strict with no fuzzy logic. Partial SSNs from the court are not treated as a match.Address
Address matching uses standardized address comparison. There is no partial match for addresses.Scoring Weights
Each field’s match score is multiplied by its weight, and the results are summed to produce the overall identity score.Current Weight Configuration
Score Calculation
Common Score Scenarios
Identity Level Thresholds
The overall score maps to an identity level:The qualifying threshold for
is_match is 0.85 (is_match: true when match_score >= 0.85). A Name + DOB match with no SSN or address yields exactly 0.85 and qualifies as a positive match. This is separate from the identity_level label, which only reaches High at 0.9 and above.Routing
Identity match results feed directly into charge-level routing. See Routing & Queues for the full routing matrix and queue rollup logic.Examples
High Match — Name + DOB + Address
Medium Match — Name + DOB (no SSN, no address)
Weak Match — Different Person
Related
- Identity Match Endpoint — API endpoint for standalone identity comparison
- Routing & Queues — How identity level feeds into charge routing
- Evaluate — Full evaluation endpoint that includes identity matching
