LexisNexis Contact Card

LexisNexis Contact Card retrieves identity, address, telephone, email, and association information for the application’s primary business owner. Although the Workflow Builder block is grouped under KYB, the report subject is the individual owner. The block exposes lexis_nexis_contact_card_report.

Requirements

Application field	Requirement	Notes
Business legal name	Required	Identifies the end-user company.
Primary owner name	Optional	Strongly recommended to identify the report subject.
Primary owner address	Optional	Helps locate the subject and disambiguate results.
Primary owner SSN	Optional	Must be valid when provided; identifies the report subject.
Primary owner date of birth	Optional	Identifies the report subject.
Primary owner telephone	Optional	Identifies the report subject.
Business address and telephone	Optional	Provides end-user context.

Run LexisNexis Contact Card

Call Enrich Business Credit Application with:

{
  "provider": "lexis_nexis_contact_card_report",
  "options": {
    "include_phones_plus": 1,
    "include_email_addresses": 1
  }
}

Poll Get Commercial Data with services[]=lexis_nexis_contact_card_report. The result appears at commercial_data.lexis_nexis.contact_card_report, the lifecycle message appears at statuses.lexis_nexis.contact_card_report, and the stored request appears at request_data.lexis_nexis.contact_card_report.

The stored request and provider response can contain SSN, date-of-birth, address, telephone, email, and other sensitive identity data. Restrict access and avoid logging these objects.

Data Orchestration availability

The current Data Orchestration definition exposes Contact Card-derived owner-name, owner-address, telephone, and address checks within the LexisNexis KYB Report group. It does not present Contact Card as a separate top-level provider group.

What the service returns

Response area	Meaning
`Header`	Provider request status and transaction identifier.
`Individual.SubjectInformation`	Primary identity, SSN indicators, date of birth, age, and deceased status.
`Individual.Imposters` and `Individual.AKAs`	Potential imposters and alternate identities.
`Individual.ReportAddresses`	Address history, dates, verification flags, and associated residents.
`Individual.ContactCard`	Grouped contact and relationship information.

Representative response

{
  "ContactCardReportResponseEx": {
    "response": {
      "Header": {
        "Status": 0,
        "TransactionId": "example-transaction"
      },
      "Individual": {
        "HasBankruptcy": "0",
        "HasProperty": "0",
        "HasCorporateAffiliation": "0",
        "SubjectInformation": {
          "Name": {
            "First": "JANE",
            "Last": "DOE"
          },
          "SSNInfo": {
            "SSN": "*****1234",
            "Valid": "1",
            "HighRiskIndicators": {
              "HighRiskIndicator": []
            }
          },
          "Deceased": "N",
          "Age": 45
        },
        "ReportAddresses": {
          "ReportAddress": []
        },
        "ContactCard": {
          "CardGroup": []
        }
      }
    }
  }
}

Response attributes

Attribute	Type	Meaning	Possible values or units	When returned
`Header.Status`	Number	LexisNexis request status code.	Provider code; `0` appears in the success fixture.	For a provider response.
`Header.TransactionId`	String	Provider transaction identifier.	Provider-generated text.	For a provider response.
`Individual.HasBankruptcy`	String	Provider indicator for bankruptcy data.	LexisNexis indicator such as `0` or `1`.	When supplied.
`Individual.HasProperty`	String	Provider indicator for property data.	LexisNexis indicator.	When supplied.
`Individual.HasCorporateAffiliation`	String	Provider indicator for corporate affiliations.	LexisNexis indicator.	When supplied.
`Individual.SubjectInformation.Name`	Object	Name associated with the subject.	First, middle, last, and prefix fields can appear.	When a subject is found.
`Individual.SubjectInformation.SSNInfo.SSN`	String	Masked or provider-formatted SSN.	Sensitive identifier text.	When available.
`Individual.SubjectInformation.SSNInfo.Valid`	String	Provider SSN validity indicator.	LexisNexis code such as `0` or `1`.	When evaluated.
`Individual.SubjectInformation.SSNInfo.HighRiskIndicators`	Object	Provider risk codes and descriptions associated with the SSN.	Zero or more indicators.	When evaluated.
`Individual.SubjectInformation.Deceased`	String	Provider deceased indicator.	Provider code such as `Y` or `N`.	When available.
`Individual.SubjectInformation.Age`	Number	Provider-calculated age.	Years.	When available.
`Individual.ReportAddresses.ReportAddress`	Array	Address history records.	Zero or more address objects.	When address data exists.
`Individual.ContactCard.CardGroup`	Array	Grouped contacts, relationships, addresses, and telephones.	Zero or more card groups.	When contact-card data exists.

Errors and statuses

Lendflow records No contact card results found. when the response lacks Individual. Authorization failures, service timeouts, and other provider errors use separate terminal messages. Success means a report was stored; it is not an identity-verification conclusion.

FAQ

Why is an individual report in the KYB category?

The block supports business underwriting by retrieving contact information for the application’s primary business owner, but the report subject is an individual.

Are phone and email results included by default?

Yes. include_phones_plus and include_email_addresses both default to 1.

What happens when no individual is returned?

Lendflow records No contact card results found. and marks the service as failed.