LexisNexis KYC

LexisNexis KYC searches for an individual and can retrieve a detailed person report. Use the search result to identify matching records and the report to review the best available identity, contact, affiliation, and public-record information returned by LexisNexis. The LexisNexis KYC block is available for individual entities in the KYC category of Workflow Builder.

LexisNexis Email Search is a separate KYC block and service. It is not part of the Search and Report services documented on this page.

Available services

Service	Provider operation	Required data	What it returns
KYC Search	BPS Search	No individual field is required by the current validator; available owner identity and address data improves matching.	A list of possible matching people and their available identifying information.
KYC Report	Comprehensive Person Report	No individual field is required by the current validator; available owner identity, address, and business-name data improves matching.	Detailed information for the best-matched individual.

KYC Search and KYC Report have separate service statuses and responses. A template can run either service or both.

Requirements

Lendflow builds the request from the primary business owner’s personal information and address.

KYC Search

Application field	Requirement	Notes
First and last name	Optional	Strongly recommended for identifying the subject.
Street address, city, state, and ZIP code	Optional	Strongly recommended for match quality.
SSN	Optional	Must be valid when present.
Date of birth	Optional	Must be a valid date when present.
Telephone	Optional	Must be a valid ten-digit telephone number when present.
Country	Optional	Used to validate state and ZIP values.

KYC Report

Application field	Requirement	Notes
First and last name	Optional	Strongly recommended for identifying the subject.
Street address, city, state, and ZIP code	Optional	Strongly recommended for match quality.
SSN	Optional	Must be valid when present.
Date of birth	Optional	Must be a valid date when present.
Telephone	Optional	Must be a valid ten-digit telephone number when present.
Business legal name	Optional	Uses the legal name on the application when available.
Country	Optional	Used to validate state and ZIP values.

The Lendflow request validator does not require an individual field for either service. However, incomplete identity information can reduce match quality or produce no results.

Configure LexisNexis KYC in Data Orchestration

In the Lendflow Dashboard, open Builders > Data Orchestration.
Create or edit a template.
Add the LexisNexis KYC service from the KYC category.
Select KYC Search, KYC Report, or both.
Select the attributes the template should evaluate or use to update the business owner.
Configure any synchronization or address-update behavior required by the selected attributes.
Connect each outcome to the next block.
Save and publish the template.

KYC Search and KYC Report expose different attributes. Run the service that supplies an attribute before evaluating that attribute. See Data Orchestration for the complete template-building workflow.

Run LexisNexis KYC through the API

Data services run through a published Data Orchestration template. Your integration needs:

An integration token with permission to access the application and run Data Orchestration.
The application ID.
A published template containing the applicable LexisNexis KYC service.
The template ID.
The applicable workflow stage_id when the template is assigned to a specific stage.

Call Execute Data Orchestration for the application.
Include template_id and application_id. Include stage_id when applicable.
Confirm that the response contains data.executed: true.
Monitor the asynchronous run with List Data Orchestration Logs and Get Data Orchestration Log.
Retrieve the application’s enrichment data after processing finishes.

An accepted execution response means the run was scheduled. It does not mean LexisNexis has finished processing.

What the services return

Response area	Meaning
`lexis_nexis.kyc.BpsSearchResponseEx`	KYC Search response containing possible matching records.
`lexis_nexis.kyc_report.CompReportResponseEx`	KYC Report response containing the selected individual’s available report sections.

KYC Search uses SubjectTotalCount to indicate how many subjects were returned. A count of zero produces a no-results status. The current KYC Report request primarily enables:

Best available identity information.
Email addresses.
Phone information and metadata.

Other LexisNexis report sections appear only when returned for the request. Do not assume that criminal records, bankruptcies, liens, judgments, relatives, neighbors, or other extended sections will always be present. A representative response shape is:

{
  "lexis_nexis": {
    "kyc": {
      "BpsSearchResponseEx": {
        "response": {
          "SubjectTotalCount": 1,
          "Records": {
            "Record": [
              {
                "UniqueId": "example-person-id",
                "Name": {
                  "First": "Jane",
                  "Last": "Doe"
                },
                "Verified": true
              }
            ]
          }
        }
      }
    },
    "kyc_report": {
      "CompReportResponseEx": {
        "response": {
          "Individual": {
            "UniqueId": "example-person-id",
            "BestInfo": {
              "Name": {
                "First": "Jane",
                "Last": "Doe"
              }
            },
            "Emails": {
              "Email": []
            },
            "PhonesPluses": {
              "PhonesPlus": []
            }
          }
        }
      }
    }
  }
}

Response attributes

KYC Search

Attribute	Type	Meaning
`BpsSearchResponseEx`	Object	Wrapper for the KYC Search response.
`BpsSearchResponseEx.response`	Object	Contains the search header, records, and subject count.
`SubjectTotalCount`	Number	Number of people returned by the search. Zero means no matching subjects were found.
`Records.Record`	Array	Possible matching people.
`Record.UniqueId`	String	LexisNexis identifier for the person.
`Record.Name`	Object	Available first, middle, and last-name parts for the person.
`Record.DOB`	Object	Available year, month, and day of birth.
`Record.Address`	Object	Available street, city, state, ZIP code, county, and country information.
`Record.PhoneInfo`	Object	Available telephone and phone-indicator information.
`Record.SSNInfo`	Object	Masked SSN information and validity details.
`Record.Age`	Number	Age associated with the returned record.
`Record.Deceased`	String	Deceased indicator returned by LexisNexis, commonly `"Y"` or `"N"`.
`Record.Verified`	Boolean	Indicates whether LexisNexis marks the record as verified.
`Record.IsCurrent`	Boolean	Indicates whether LexisNexis considers the record current.
`Record.SubjectSSNIndicator`	String	Describes how the SSN relates to the subject, such as subject, close, relative, or no match.

KYC Report

Attribute	Type	Meaning
`CompReportResponseEx`	Object	Wrapper for the KYC Report response.
`CompReportResponseEx.response`	Object	Contains the response header and individual report.
`Individual`	Object	Detailed result for the selected person.
`Individual.UniqueId`	String	LexisNexis identifier for the reported person.
`Individual.BestInfo`	Object	LexisNexis’s best available name, address, DOB, gender, deceased indicator, and SSN information.
`Individual.Emails.Email`	Array	Email records associated with the person, including available names and addresses.
`Individual.PhonesPluses.PhonesPlus`	Array	Telephone records, including available carrier, phone type, listed name, address, and timezone.
`Individual.Sources.Source`	Array	Source records supporting the report when returned.
`Individual.CorporateAffiliations.Affiliation`	Array	Businesses associated with the person when the section is returned.
`Individual.CriminalRecords`	Object	Criminal-record details when requested and returned.
`Individual.LiensJudgments`	Object	Lien and judgment details when requested and returned.
`Individual.UCCFilings`	Object	UCC filing details when requested and returned.

Objects for optional report sections can be absent or empty. Their absence does not necessarily mean the overall KYC Report request failed.

FAQ

What is the difference between KYC Search and KYC Report?

KYC Search returns possible matching people. KYC Report retrieves detailed information for the best-matched individual. They are separate services with separate responses.

Why did LexisNexis return no search results?

Confirm that the primary owner has accurate name and address information. SSN, date of birth, and telephone can improve matching when available.

Why is a report attribute empty?

Some attributes depend on optional report sections. If LexisNexis did not return the underlying section, the attribute remains empty even when the report request completed.

Is LexisNexis Email Search part of this block?

No. LexisNexis Email Search is a separate KYC block and service.

Does data.executed true mean LexisNexis has finished?

No. It means Data Orchestration accepted and scheduled the run. Monitor the orchestration log for completion.

​LexisNexis KYC

​Available services

​Requirements

​KYC Search

​KYC Report

​Configure LexisNexis KYC in Data Orchestration

​Run LexisNexis KYC through the API

​What the services return

​Response attributes

​KYC Search

​KYC Report

​FAQ

LexisNexis KYC

Available services

Requirements

KYC Search

KYC Report

Configure LexisNexis KYC in Data Orchestration

Run LexisNexis KYC through the API

What the services return

Response attributes

KYC Search

KYC Report

FAQ