> ## Content Index
> Fetch the complete content index at: https://blog.digifi.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# LexisNexis Risk Solutions and DigiFi: Layered Identity and Fraud Checks in One Workflow
- URL: https://blog.digifi.io/lexisnexis-risk-solutions-and-digifi-layered-identity-and-fraud-checks-in-one-workflow/
- Published: 2026-11-18T09:40:18.000Z
- Updated: 2026-11-18T09:52:05.000Z
- Description: How lenders use LexisNexis Risk Solutions in DigiFi to layer device intelligence, identity verification, fraud scores, and sanctions screening, whether they use one product or all of them.
- Author: Bradley Vanderstarren
- Tags: Partner Spotlight

An application arrives at 2:14 a.m. The name, date of birth, and Social Security number are valid. The address exists. The credit file is thin but clean. Nothing on the form looks wrong.

What that data doesn't show is the rest of the picture. The device submitting it has been used for applications under several different names this week. The connection runs through a proxy. The phone number was activated last month. None of these facts proves fraud on its own. Together, they describe an application that deserves a closer look before anyone funds it.

This is the core difficulty of fraud prevention during loan origination: each check answers a different question, and no single check answers all of them. A device signal can’t tell you whether a person is real. An identity check can’t tell you whether the person typing is the person named on the application. A fraud score can’t tell you whether an applicant is on a sanctions list. Lenders have to decide which questions to ask, in what order, and what to do when the answers disagree, while keeping the process fast for the large majority of applicants who are exactly who they say they are.

DigiFi is proud to be partnered with [LexisNexis Risk Solutions](https://risk.lexisnexis.com/?ref=blog.digifi.io), whose identity, fraud, and compliance products are widely used in financial services. Eight LexisNexis integrations are available off-the-shelf in the [DigiFi loan origination system](https://www.digifi.io/?ref=blog.digifi.io), covering device and session intelligence, identity verification, fraud scoring, and sanctions screening. Lenders connect them with their own LexisNexis credentials. Many start with a single product and add others as their fraud patterns change.

The post provides an in-depth review of how lenders can use LexisNexis within their loan origination workflows to increase automation while reducing fraud.

## Four Questions at the Front Door

The LexisNexis integrations in DigiFi map to four layers of defense, and each answers one question.

| Layer                    | The question                                                 | LexisNexis products in DigiFi                                                    | Typical response to a flag              |
| ------------------------ | ------------------------------------------------------------ | -------------------------------------------------------------------------------- | --------------------------------------- |
| Device and session       | Is this a genuine user on a trustworthy device?              | ThreatMetrix Session ID and Session Verification                                 | Step up verification, or send to review |
| Identity                 | Is this a real person, and do these details belong together? | InstantID, FlexID, Attribute Verification                                        | Request documents, or refer             |
| Fraud risk               | How likely is this application to involve identity fraud?    | Fraud Intelligence 1.0 Score (formerly FraudPoint), Fraud Intelligence 2.0 Score | Route by score band and warning codes   |
| Sanctions and watchlists | Is this person or business on a sanctions or watch list?     | Bridger Insight XG                                                               | Hold for compliance review              |

**Device and session: ThreatMetrix.** ThreatMetrix builds a digital identity for each user from device information, anonymized identity data, behavioral patterns, and threat intelligence. Its signals draw on the LexisNexis Digital Identity Network, which analyzed more than 116 billion transactions in 2025\. In DigiFi, the ThreatMetrix Session ID integration captures a session ID on the Standard Borrower Portal, and the Session Verification integration uses that ID to bring device and risk data back into the application. The check runs in the background, so genuine applicants see nothing extra.

**Identity: InstantID, FlexID, and Attribute Verification.** These confirm that an applicant’s details are real and belong together, using public records, credit bureau identity data, and other sources linked through LexisNexis’s LexID technology. InstantID is designed to support Customer Identification Program and Know Your Customer requirements. FlexID offers configurable, multi-method verification with risk scoring. Attribute Verification validates individual details, such as name, email, phone, or ID, when a lender needs to check specific elements rather than a full identity.

**Fraud risk: Fraud Intelligence scores.** Fraud Intelligence 1.0 (formerly FraudPoint) returns a three-digit score with warning codes that point to the conditions driving the risk, such as a Social Security number linked to multiple identities. Fraud Intelligence 2.0 adds insight into identity events and application activity seen across LexisNexis’s networks.

**Sanctions and watchlists: Bridger Insight XG.** Bridger screens individuals and businesses against global regulatory, sanctions, and watch lists. Every U.S. lender must avoid doing business with sanctioned parties, and screening at application is the usual control.

## How the Integration Works

![](https://storage.ghost.io/c/a4/93/a4936be6-6f08-4913-9b80-e4b056976b09/content/images/2026/11/image-2.png)

1. **The lender connects its LexisNexis credentials.** Each LexisNexis product the lender licenses is added from the DigiFi Marketplace with the lender’s own credentials.
2. **ThreatMetrix profiles the session.** When the applicant opens a lender's digital lending portal, the ThreatMetrix Session ID integration generates and stores a session ID while the applicant completes the application.
3. **DigiFi runs the checks at the right step.** The lender decides which LexisNexis integrations run at which workflow step, and whether a later check runs only when an earlier one raises a flag.
4. **Results land as data.** Scores, verification results, warning codes, and watchlist matches are mapped to application variables.
5. **The lender’s rules decide.** Decision strategies combine LexisNexis results with credit bureau and application data to approve, request more information, refer, or decline.
6. **Exceptions go to the right team.** Referred applications reach fraud or compliance reviewers with the LexisNexis results attached.

## Start With One Layer, Add Others

![](https://storage.ghost.io/c/a4/93/a4936be6-6f08-4913-9b80-e4b056976b09/content/images/2026/11/image-3.png)

Few lenders implement every layer at once, and they don’t need to. Each integration works on its own, so a lender can start where its risk is concentrated:

- **Banks and credit unions** often start with InstantID or FlexID to support their Customer Identification Program, and add Bridger Insight XG if sanctions screening isn’t handled elsewhere.
- **Digital lenders with high application volume** often start with ThreatMetrix. Bots and repeat devices show up in session data before they show up anywhere else, and the check adds no friction for applicants.
- **Lenders seeing identity fraud losses** add a Fraud Intelligence score to separate likely fraud from honest data-entry mistakes.

Because DigiFi controls when each check runs, layers can also be ordered to manage cost. A lender might run the background session check on every application, run identity verification on every completed application, and call the fraud score only when the first two raise a flag or above a certain loan amount. Adding a layer later is a configuration change, not a new implementation.

## Designing Your Fraud Policy

The products supply the signals. The policy decides what happens next:

- **Score bands, not single cutoffs.** Define what happens in each band: proceed, step up, review, or decline. A middle band that triggers a document request or a reviewer task catches fraud without turning away good applicants who happen to score near a cutoff.
- **Warning codes as instructions.** Map LexisNexis warning codes and verification results to reviewer instructions, so the person working a referral knows what to check first.
- **Step up before declining.** For partial identity matches, ask for a document or additional verification before declining. Many mismatches are typos, recent moves, or name variations.
- **Separate fraud rules from credit rules.** Keep them distinct in the decision strategy, so each can be tuned, audited, and explained on its own.
- **Close the loop.** Record confirmed fraud outcomes in DigiFi and review thresholds against them regularly.

Each of these is a rule: written once, tested, and applied the same way every time in the [decision engine](https://www.digifi.io/decision-engine?ref=blog.digifi.io).

## Trade-offs to Plan For

Layered checks reduce fraud, but they bring trade-offs of their own.

**Friction for legitimate applicants.** Identity checks built on records can struggle with thin files, recent moves, and name variations. Set thresholds using your own data, and give applicants a clear way to resolve a mismatch.

**Fraud tools are not credit tools.** LexisNexis describes Fraud Intelligence as a non-FCRA solution. Work with your compliance team and LexisNexis on how each product’s results may be used in a decision, and how declines are handled and communicated.

**Cost per check.** Each product is priced under the lender’s own LexisNexis agreement. Running every check on every application maximizes coverage, but it also maximizes cost. Conditional ordering helps.

**Device data needs disclosure.** ThreatMetrix collects device and behavioral data during the session. Confirm that your privacy disclosures cover it.

**Fraud adapts.** LexisNexis detected 4.9 billion automated bot attacks across its network in 2025, up 59% from the year before. Rules that work today will need adjusting, and keeping them in a decision engine rather than in code makes that faster.

## Who Benefits Most

| Lender type                       | Starting point                                                                        | How they use LexisNexis in DigiFi                                                       |
| --------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Community banks and credit unions | CIP and sanctions obligations; manual identity reviews                                | InstantID or FlexID with Bridger Insight XG, with results recorded on every application |
| Digital consumer lenders          | High volume, bots, and synthetic identities                                           | ThreatMetrix on every session, plus a Fraud Intelligence score for flagged applications |
| Indirect lenders (auto, RV, etc.) | Applications arrive through dealers, so the lender never sees the applicant’s session | InstantID and a Fraud Intelligence score on every dealer-submitted application          |
| Small business lenders            | Verifying owners and screening both owners and the business                           | Identity verification on owners, and Bridger Insight XG on owners and the entity        |
| Lenders with rising fraud losses  | Losses are growing, but the source is unclear                                         | Start with one layer, measure where fraud appears, and add layers there                 |

## For Technology Teams

Each LexisNexis product is a Marketplace integration added to a loan product and configured with the lender’s credentials. Response fields map to application variables used in decision strategies, workflow automation, and reports. ThreatMetrix session capture is built into the Standard Borrower Portal. Teams with a custom portal load ThreatMetrix profiling in their own front end and send the session ID to DigiFi for the Session Verification call. LexisNexis products not yet in the Marketplace can be connected through DigiFi’s data integrations. Full details are in the [LexisNexis integration documentation](https://docs.digifi.io/docs/lexisnexis?ref=blog.digifi.io) and the [ThreatMetrix Session ID setup guide](https://docs.digifi.io/docs/lexisnexis-treatmetrix-session-id?ref=blog.digifi.io).

## Getting Started

1. **Confirm your LexisNexis products.** Identify the products you license or plan to license, and get your credentials from LexisNexis.
2. **Add the integrations.** Add each product from the DigiFi Marketplace and enter your credentials. For ThreatMetrix, enter your Organization ID under Lending Setup > Marketplace > LexisNexis ThreatMetrix Session ID, then add Session Verification.
3. **Decide the order.** Choose which checks run at which workflow step, and which run only when an earlier check raises a flag.
4. **Write your policy as rules.** Set score bands, step-up actions, and review routing, and decide how fraud rules and credit rules interact.
5. **Test, then launch.** Run test applications in DigiFi’s testing mode, including known-bad scenarios. After launch, track referral rates, confirmed fraud, and how many good applicants are stepped up or declined.

Existing DigiFi customers typically go live in one to two weeks, and new DigiFi customers in 60 to 90 days.

Return to the 2:14 a.m. application. With layered checks in DigiFi, the device history and proxy connection send it to a step-up identity check instead of an automatic approval. Meanwhile, the genuine applicants who apply that night move through without noticing anything at all.

## Frequently Asked Questions

### What is LexisNexis Risk Solutions?

LexisNexis Risk Solutions provides data and analytics for identity verification, fraud prevention, and compliance.

### Which LexisNexis products are available in DigiFi?

ThreatMetrix Session ID and Session Verification, InstantID, FlexID, Attribute Verification, Fraud Intelligence 1.0 Score (formerly FraudPoint), Fraud Intelligence 2.0 Score, and Bridger Insight XG. Other LexisNexis products can be connected through DigiFi’s data integrations.

### Do I need to use all of them?

No. Each integration works on its own. Many lenders start with one product and add others later.

### How does ThreatMetrix work in DigiFi?

The Standard Borrower Portal captures a ThreatMetrix session ID in the background while the applicant completes the application. The Session Verification integration then uses that ID to bring device and risk data into DigiFi for the lender’s rules.

### Can I use ThreatMetrix with a custom portal?

Yes. Lenders with a custom portal embed ThreatMetrix profiling in their own front end and pass the session ID to DigiFi.

### Do I need my own LexisNexis contract?

Yes. Lenders contract with LexisNexis Risk Solutions directly and connect each product to DigiFi with their own credentials.

### Can DigiFi screen applicants against sanctions lists?

Yes. With Bridger Insight XG, lenders can screen individuals and businesses against global regulatory, sanctions, and watch lists as part of the application workflow.

### How long does implementation take?

1-2 weeks for existing DigiFi customers. 60-90 days for new DigiFi customers.