LexisNexis Personal Credit

LexisNexis Personal Credit runs RiskView Attributes for the application’s primary owner. It returns identity, address, inquiry, and property-related attributes rather than a traditional bureau score. The registered Workflow Builder block is Personal Credit > LexisNexis Personal Credit, its block ID is lexisnexis_personal_credit, and it supports the Individual entity type.

Service	Service ID	Numeric provider ID
Lexis Nexis Risk View	`lexis_nexis_risk_view`	`57`

LexisNexis RiskView is a bring-your-own-credentials service. Your organization must connect active LexisNexis RiskView credentials before the service can run.

Requirements

Application field	Requirement	Notes
Primary-owner first and last name	Required	Used to match the owner.
Business telephone	Required	Use a valid phone number.
Business legal name and address	Optional	Company name, street, city, state, and ZIP improve matching when available.
Owner SSN	Conditional	At least one matching route is required: SSN, full date of birth, or complete personal address.
Owner date of birth	Conditional	Required when neither SSN nor complete personal address is supplied; use a complete date.
Owner personal address	Conditional	Required when neither SSN nor full date of birth is supplied; include street, city, state, and ZIP.
Owner email	Optional	Use a valid email address.

Inquiry semantics

RiskView does not expose a hard/soft credit-inquiry option in Lendflow. It is an attribute service whose request includes an intended purpose. Do not describe it as a hard or soft bureau pull; use only a purpose authorized for the connected credentials.

API flow

Call Enrich Business Credit Application for the application.
Set provider to lexis_nexis_risk_view.
Omit options; this service has no run-time service context.
Confirm data.onqueue: true.
Poll GET /api/applications/{application_id}/commercial_data through Get Commercial Data with services[]=lexis_nexis_risk_view.

{
  "provider": "lexis_nexis_risk_view"
}

Commercial data uses data.commercial_data.lexis_nexis.risk_view for the provider response, data.statuses.lexis_nexis.risk_view for status, data.dates.lexis_nexis_risk_view for the latest date, and data.request_data.lexis_nexis.risk_view for the stored request.

Data Orchestration availability and flow

LexisNexis RiskView is available in Builders > Data Orchestration > Personal Credit as provider ID 57, under LexisNexis Risk View. Current conditions include whether the input address is likely an apartment, months since the address first appeared on a non-derogatory source, inquiries in the past three months, real properties purchased in the past five years, and the latest assessed value for the input address.

Add the required RiskView condition to a template.
Configure the comparison and connect outcomes, then save and publish.
Execute with Execute Data Orchestration.
Monitor the logs and retrieve the complete provider response through the paths above.

What the service returns

Response area	Meaning
`Header.Status`	Provider-level request status.
`Header.TransactionId`	LexisNexis transaction identifier.
`Header.Exceptions.Item`	Provider exception codes, including success code information.
`Result.InputEcho`	Identity values echoed by the provider. Treat these as sensitive.
`Result.AttributesGroup.Name`	Requested attribute set; current requests use `RISKVIEWATTRV6`.
`Result.AttributesGroup.Attributes.Attribute`	Name/value pairs returned by RiskView.

{
  "RiskViewKelResponseEx": {
    "response": {
      "Header": {
        "Status": 0,
        "TransactionId": "example-transaction",
        "Exceptions": {"Item": [{"Code": 0}]}
      },
      "Result": {
        "AttributesGroup": {
          "Name": "RISKVIEWATTRV6",
          "Attributes": {
            "Attribute": [
              {"Name": "pi_inpaddrtaxval", "Value": "250000"}
            ]
          }
        }
      }
    }
  }
}

Attribute values arrive as strings and provider sentinel values may have special meanings. Treat missing attributes as unknown, not zero or false.

Errors and statuses

Condition	Meaning
`Authorization failed.`	Connected RiskView credentials were rejected.
`No RiskView attributes were returned.`	The request completed without the required attributes collection.
Input validation message	Correct the missing or invalid name, phone, identity route, address, email, state, or ZIP.
`data.onqueue: true`	The asynchronous job was queued.
`Not yet started`, `Started`, `Success`, or an error	Lendflow lifecycle status, not a RiskView attribute.

FAQ

Does RiskView return a credit score?

The current integration requests RiskViewAttrV6 attributes. It does not configure a conventional FICO or VantageScore model.

Can I use Lendflow-managed credentials?

No. The current service definition is bring-your-own-credentials only.

Must the owner have an SSN?

Not always. The matching rules allow SSN, full DOB, or a complete personal address in supported combinations. First name, last name, and the required phone remain mandatory.