Authoritative Database
Checker Category: Identity — PII
Used In Steps: PII Validation
Used In Workflows: Identity Verification, NIST IAL2, and all MobileMatch-based workflows
Overview
Authoritative Database checkers validate user-provided PII against third-party identity databases — credit bureau records, public records, phone registration data, and proprietary intelligence. A match confirms that the provided identity data is internally consistent and exists in authoritative records. It does not confirm that the person submitting the data is the actual identity owner — pair with possession and risk checkers for full layered verification.
Four vendor variants are available. The variant configured for your workflow is determined at deployment time — contact your ID Dataweb team to confirm which is active. All four share the same inputs and the same role in the PII Validation step; they differ in database coverage, assertion depth, and geographic scope.
End User Requirements
Name, address, phone number. SSN (full 9-digit or last 4) is optional for US variants but significantly improves match rate and assertion depth.
Role in Layered Verification
Authoritative Database runs as part of the PII Validation step alongside the Phone Registration + Risk checker. Both run simultaneously. A confirmed match from either source contributes to the step result. The Authoritative Database checker handles the identity record side; Phone Registration handles the carrier-side corroboration.
Variants
Supported Countries: United States
What It Provides: Deep PII-to-database matching across LexisNexis' comprehensive identity graph — credit bureau, public records, and proprietary intelligence. Covers name-to-address matching, phone verification, SSN validation, deceased status, watchlist screening, and address characterization. Satisfies CIP requirements.
Acquired Attributes
| Attribute | Code | Description |
|---|---|---|
| Persistent ID | LexID | Stable cross-session identifier for this identity |
| SSN Validity Indicator | SSNValidityIndicator | SSN validity signal |
| Persistent ID Emerging | LexIDEmerging | Emerging identity signal |
| Record Lookup Type | RecordLookupType | Type of record matched |
| Phone Type | PhoneType | Mobile, landline, VOIP, etc. |
| Phone Status | PhoneStatus | Active, inactive, ported |
| Phone First Seen | PhoneFirstSeen | Date phone number first appeared in records |
| Phone Last Seen | PhoneLastSeen | Date phone number last appeared in records |
| Flagged Watchlists | FlaggedWatchlists | Whether identity appears on any watchlist |
| Flagged Watchlists Details | FlaggedWatchlistsDetails | Watchlist detail breakdown |
| Business Type | BusinessType | Business classification if address is commercial |
| Risk Indicator | RiskIndicator | Overall risk signal |
| Most Recent Street Address | MostRecentAddress | Most recent address on file for this identity |
Assertions
| Assertion | Key | Description |
|---|---|---|
| Provided SSN9 Linked to Provided Street Address in Identity Record | link.address_SSN9 | Confirms that the provided SSN9 corresponds to the provided street address in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided SSN4 Linked to Provided Street Address in Identity Record | link.address_ssn4 | Confirms that the provided SSN4 corresponds to the provided street address in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided DOB Linked to Provided SSN4 in Identity Record | link.dob_SSN4 | Confirms that the provided date of birth corresponds to the provided SSN4 in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided Last Name Linked to Provided SSN9 in Identity Record | link.lastName_SSN9 | Confirms that the provided last name corresponds to the provided SSN9 in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided Last Name Linked to Provided SSN4 in Identity Record | link.lastname_ssn4 | Confirms that the provided last name corresponds to the provided SSN4 in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided Name or Provided Street Address Linked to Provided SSN4 in Identity Record | link.name_or_address_to_ssn4 | Confirms that the provided name or provided street address corresponds to the provided SSN4 in identity records. Passes if a correspondence is found for at least one; fails if neither corresponds.. |
| Provided Name or Provided Street Address Linked to Provided SSN9 in Identity Record | link.name_or_address_to_ssn9 | Confirms that the provided name or provided street address corresponds to the provided SSN9 in identity records. Passes if a correspondence is found for at least one; fails if neither corresponds. |
| Street Address Not Business Check | test.addressIsNotBusiness | Confirms that the provided street address is not registered as a business address. Passes if it is not a business address; fails if it is. |
| Street Address Not PO Box Check | test.addressIsNotPOBox | Confirms that the provided street address is not a PO Box. Passes if it is not a PO Box; fails if it is. |
| Street Address Vacant Check | test.addressIsVacant | Indicates whether the provided street address is flagged as vacant. Passes if it is not vacant; fails if it is flagged as vacant. |
| Person Not Deceased Check | test.candidateNotDeceased | Confirms that the person associated with the provided identity data is not flagged as deceased. Passes if the person is not deceased; fails if a deceased flag is present. |
| Driver's License Number Record Check | test.driversLicenseNumberVerified | Confirms that the provided driver's license number matches official records. Passes if confirmed; fails if it cannot be. |
| Phone Number Type Check | test.phone_landline_mobile_personal | Confirms that the provided phone number is a verified landline, mobile, or personal line. Passes if the line type is confirmed; fails if it cannot be. |
| SSN4 Validity Check | test.ssn4IsValid | Confirms that the provided SSN4 is a valid format and recognized identifier. Passes if valid; fails if not. |
| SSN Validity Check | test.ssn9IsValid | Confirms that the provided SSN is a valid format and recognized identifier. Passes if valid; fails if not. |
| SSN Uniqueness Check | test.ssn9MatchesNoOthers | Confirms that the provided SSN and associated data points are collectively unlikely to correspond to any other SSN. Passes if the combination is sufficiently unique; fails if ambiguity exists. |
| SSN Deceased Person Check | test.ssn9NotDeceased | Confirms that the person associated with the provided SSN is not flagged as deceased. Passes if the person is not deceased; fails if a deceased flag is present. |
| SSN Validity Check | test.ssnIsValid | Confirms that the provided SSN is a valid format and recognized identifier. Passes if valid; fails if not. |
| Identity Global Watchlist Check | test.watchlistCheck | Assesses the provided identity data against global watchlist databases. Passes if no matches are found; fails if a watchlist match is detected. |
Notes: US only — for international coverage use LSEG. SSN optional but significantly improves assertion depth. LexID is useful for cross-session deduplication. Deprecated assertions: link.dob_SSN and link.lastName_DOB — do not use.
Testing & Expected Results
Testing follows PII Validation step procedures for all variants. See PII Validation for test credentials and step-by-step instructions.
- Approve: Andrew Roshell test data on any US variant
- International (LSEG): Contact your ID Dataweb team for LSEG-specific test data
Related Resources
→ PII Validation | → Phone Registration + Risk | → Dynamic KBA - LexisNexis | → Identity Verification
Updated 2 days ago