Outputs

Product Outputs

Composite Score

The strength of the match (no match, full match, partial match, etc.) for each element creates a score based on the weightings and type of match. Each of the element-level scores are aggregated into a composite score. The composite score scale is between 0 and 100 with the higher the number the greater the probability that the identity is a match.

Not all identity elements are equal in terms of verification. For example, there should be a one-to-one ratio between a person and their SSN. Only one person should have a particular SSN and that SSN should never change (with very few exceptions). Enformion’s default weighting is highest for SSN and DoB.

Default Weights

1st FieldRankPercentage
SSN1021.05%
DoB1021.05%
Email510.53%
FN +LN8.7518.52%
Address6.2513.16%
Phone7.510.53%

Identity Element Match Codes

In the API Response Enformion provides score descriptions. Anytime there is a partial match the reason will be contained in the score description

Element-Level Match Codes: Enformion indicates the type of match for each identity element that was submitted.

  • “Match” - This indicates that the submitted identity element is an exact match to the corresponding element in the Enformion database
  • “Partial Match” - This indicates that the submitted identity element is a a partial match to the corresponding element in the Enformion database. There are different types of partial matches (based on the type of identity element) and the “Score Descriptions” are useful to understand the type of partial match
  • “No Match” - This indicates that the submitted identity element is NOT a match to the corresponding element in the Enformion database. Enformion uses strict data matching standards.
  • “Not Applicable” - This response is returned whenever a field does not include a submission (e.g., empty)
FieldField Score LogicLogicScore Description
AddressFull AddressFull Address Match"Address Match"
Previous AddressFull address match on a previous/historical address"Prev_Address_Match"
Address Missing Unit Number (#)Full address match excluding the unit"ADDRESS_MATCH_MINUS_UNIT"
Previous Address Minus Unit Number (#)Full address match on previous/historical address excluding the unit"PREV_ADDRESS_MATCH_MINUS_UNIT"
Partial Address MatchMatch on house number and first 4 chars of street name"HOUSE_NUMBER_1ST_FOUR_OF_STREET_NAME_MATCH"
Partial Address Match on a Previous AddressMatch on previous/historical house number and first 4 chars of street name"PREV_HOUSE_NUMBER_1ST_FOUR_OF_STREET_NAME_MATCH"
House Number MatchHouse number match"HOUSE_NUMBER_MATCH"
House Number Match on a Previous AddressHouse number match on previous/historical address"PREV_HOUSE_NUMBER_MATCH"
Street Name MatchStreet name match"STREET_NAME_MATCH"
Street Name Match on a Previous AddressStreet name match on previous/historical address"PREV_STREET_NAME_MATCH
No MatchNo Match On Address"ADDRESS_NO_MATCH"
Name
Full NameFull name match including middle if included in request"FULL_NAME_MATCH"
Full Name on Also-Known-as (AKA)Full name match (on AKA) including middle if included in request"PREV_FULL_NAME_MATCH"
First Name (FN)First and last names match, but not middle name.FIRST_NAME_LAST_NAME_MATCH
FN on AKAFirst and last names match on AKA, but not middle name."PREV_FULL_NAME_MATCH"
Partial FN and Last Name (LN)Last name and 1st 4 chars of first name match."LAST_NAME_AND_1ST_FOUR_OF_FIRST_NAME_MATCH"
Partial FN and LN on AKALast name and 1st 4 chars of first name of AKA.PREV_LAST_NAME_ONLY_MATCH
Partial FN and LNLast name and 1st letter of first name match."LAST_NAME_AND_1ST_LETTER_OF_FIRST_NAME_MATCH
Partial FN and Last Name (LN) on AKALast name and 1st letter of first name match of AKA.PREV_LAST_NAME_ONLY_MATCH
Last NameLast name only match.LAST_NAME_ONLY_MATCH
Last Name on AKALast name only matches on AKA."PREV_LAST_NAME_ONLY_MATCH"
First NameFirst name only matches."FIRST_NAME_ONLY_MATCH"
First Name on AKAFirst name only matches on AKA."PREV_FIRST_NAME_ONLY_MATCH"
No MatchNo Name Match"NAME_NO_MATCH"
Date Of Birth
Full Date of Birth (DoB)Full DOB match"FULL_DOB_MATCH"
MonthMonth and Year match, not day"MONTH_YEAR_MATCH"
YearYear of DOB only match"YEAR_MATCH"
No MatchNo DOB Match"DOB_NO_MATCH"
Phone
Full PhoneFull phone match"FULL_PHONE_MATCH"
Full Phone on Previous PhoneFull phone match on previous/historical phone"PREV_FULL_PHONE_MATCH"
Partial PhoneLast 7 digits of phone match"PHONE_LAST_7_MATCH"
Partial on Previous PhoneLast 7 digits of phone match or previous/historical phone"PREV_PHONE_LAST_7_MATCH"
No MatchNo Phone Match"PHONE_NO_MATCH"
Email
Full EmailFull email match"FULL_EMAIL_MATCH"
User NameUser name only match"USERNAME_MATCH"
NO MATCHNo Email Match"EMAIL_NO_MATCH"
SSN
Social Security Number (SSN)SSN exact match"SSN_EXACT_MATCH"
Partial SSNLast 4 digits of SSN match"LAST_4_MATCH"
Last 4 of SSN when RestrictedLast 4 digits of SSN when full SSN's are not permitted by access profile"LAST_4_MATCH_REDACTED"
NO MATCHNO SSN MATCH"SSN_NO_MATCH"
City
Full CityCity Exact Match"FULL_CITY_MATCH"
NO MATCHNo City Match"CITY_NO_MATCH"
Zip
Full ZipZip Exact Match"ZIP_EXACT_MATCH"
Partial ZipPartial Zip Match"FIRST_3_DIGITS_MATCH"
NO MATCHNO ZIP MATCH"ZIP_NO_MATCH"
STATE
Full StateFull State Match"STATE_EXACT_MATCH"
NO MATCHNo State Match"STATE_NO_MATCH"

Deceased Status

Enformion will return a deceased status of "True” when there is a positive match, otherwise a “False” is returned. A positive match only occurs when the Full Name, Date-of-Birth and SSN matc

Additional Outputs

Person ID - Enformion returns a unique identifier for each of the candidate identities located in the Enformion database.

Request ID – Enformion produces a unique, transaction-based identifier for every score request and response. Client’s should use the Request ID when asking Enformion to research a particular score request. Here is a sample: "c57d4bb3-73e9-484a-8e57-5fdb1b889a61"