Skip to content
Console(opens in a new tab)

Name and address checks

How the four name and address tasks compare the names and addresses you send with the matched records, and the results each one returns.

The name and address checks compare the business names and addresses you send with the records of the business Enigma matched. All four tasks run on both the identify and verify packages, and each reports its outcome in risk_summary.tasks. The two name tasks share one comparison, as do the two address tasks: name_verification and address_verification compare against every matched record, including the brand, while sos_name_verification and sos_address_verification compare against Secretary of State (SoS) registrations only.

These two tasks come from the example response on How checks work, shown here with their sources.

Example name and address tasks
{
"risk_summary": {
"tasks": [
{
"task_name": "address_verification",
"status": "success",
"result": "address_match",
"reason": "An input address matches an address in any of Enigma's records",
"sources": [
{
"address": {
"street_address1": "245 5TH AVE",
"street_address2": "FL 17",
"city": "NEW YORK",
"state": "NY",
"postal_code": "10016",
"type": "headquarters",
"deliverable": "deliverable",
"virtual": "not_virtual",
"delivery_type": "multi-tenant building",
"rdi": "commercial"
},
"match_entity_type": "registered_entity",
"match_relationship_type": "registration_address",
"urls": ["https://example.com/records/ny-5012345"]
}
]
},
{
"task_name": "name_verification",
"status": "success",
"result": "name_match",
"reason": "An input business name matches a business name in any of Enigma's records",
"sources": [
{
"name": "ENIGMA TECHNOLOGIES, INC.",
"match_entity_type": "registered_entity",
"urls": [
"https://example.com/records/de-4973743",
"https://example.com/records/ny-5012345"
]
},
{
"name": "ENIGMA TECHNOLOGIES",
"match_entity_type": "brand",
"urls": []
}
]
}
]
}
}
  • address_verification: the request omitted the suite, and the record carries FL 17, so the result is address_match.
  • name_verification: the submitted name “Enigma” (the trade name from the Several names example) is contained in both the registered name and the brand name but matches neither exactly, so the result is name_match and both records are listed. The brand source’s urls is [].

Compares each business name you send (up to two) with the registered names on the matched registered entity’s registrations and with the matched brand’s names.

  • Required input: a business name in name, names or primary_name.
  • Exact match: the names are identical after normalization. Normalization ignores case, periods, commas and extra spaces, and treats common forms as equal: “Incorporated” and “Inc”, “Limited Liability Company” and “LLC”, “Company” and “Co”, “&” and “and”.
  • Match: the names are substantially similar but not identical. Legal suffixes are not removed, so “Enigma Technologies” against “Enigma Technologies, Inc.” is name_match, not an exact match. A name contained in a longer one also matches, in either direction: a submitted name within a name on record, or a name on record within the submitted name.
ResultStatusMeaning
name_exact_matchsuccessA submitted name exactly matches a name on the matched records.
name_matchsuccessA submitted name matches a name on the matched records, but not exactly.
name_not_verifiedfailureNo submitted name matches, or no business matched.

The same comparison, with the same required input, as name_verification, restricted to the registered_name of each SoS registration on the matched registered entity. Brand names do not count. It returns the same results as name_verification, where a match must be the registered_name of an SoS registration.

A success on name_verification with name_not_verified here means the name matches a brand name but not a registered name.

Compares each address you send (up to two) with the addresses on the matched records: registration addresses, the registered entity’s mailing addresses, the brand’s operating locations and, when you request the person_addresses add-on, the addresses of the people on its registrations.

  • Required input: an address with street_address1. An address without a street line is skipped, so a city, state or ZIP code alone always returns address_not_verified.
  • Standardization: both addresses are standardized first, with USPS-style abbreviations and the ZIP code cut to five digits. If either address has no ZIP code, the ZIP code is ignored.
  • Street number: the street numbers must agree, allowing for a likely typo: one digit slightly off, two adjacent digits swapped, a digit added or dropped at either end, or a small difference in a number of four or more digits. Any other difference, or a number on only one side, is not a match.
  • Exact match: the addresses are identical after standardization. When either address has a street_address2 (a suite, floor or unit), both must have the same one. Send street_address2 when the business has one.
  • Match: the address as a whole is substantially similar. A city also matches through an alternative city name for the record’s ZIP code, such as Hollywood for a Los Angeles ZIP code. A match found this way is never exact.
ResultStatusMeaning
address_exact_matchsuccessA submitted address exactly matches an address on the matched records.
address_matchsuccessA submitted address matches an address on the matched records, but not exactly.
address_not_verifiedfailureNo submitted address matches, no submitted address has a street line, or no business matched.

The same comparison, with the same required input, as address_verification, restricted to the addresses on the matched registered entity’s SoS registrations. It returns the same results as address_verification, where a match must be an address on an SoS registration.

Each of the four tasks lists the records behind a match in sources: the name or address on record, where it came from and, for an address, how it relates to its record. For the fields, and which records are listed when a task finds an exact match, see Sources on How checks work.