Who LexisNexis Risk Solutions is
LexisNexis Risk Solutions is part of RELX and headquartered in metro Atlanta, Georgia. It provides data and analytics for identity verification, fraud prevention, financial crime compliance and credit risk, to financial services, insurance, government and other sectors.
Two of its product families matter here. WorldCompliance data profiles sanctioned entities, politically exposed persons, state-owned enterprises, enforcement subjects and adverse media, screened through Bridger Insight XG, while ThreatMetrix assesses devices, locations and behaviour in real time, drawing on the LexisNexis Digital Identity Network. Together they make LexisNexis a connector in our KYC / AML and fraud & risk modules.
What it does in your platform
KYC / AML
Screens customers at sign-up against WorldCompliance data through Bridger Insight XG: sanctions, politically exposed persons, state-owned enterprises, enforcement and adverse media. Possible matches go to the module's review queue.
Fraud & risk
Adds ThreatMetrix's view of the device and the session to every sign-up, login and payment the module scores. Its signals join your own rules in one decision: allow, ask for a second factor, hold for review or block.
How the connection works
Each module talks to its own LexisNexis service from your platform: Bridger Insight XG for screening, ThreatMetrix for device and session risk. In your apps, ThreatMetrix's SDK only collects signals; the credentials stay in your platform's secrets.
The device is profiled
While a customer signs up, ThreatMetrix collects device and connection signals in the background, with no extra step for the customer.
The session is assessed
The fraud & risk module asks ThreatMetrix about the session and gets a risk assessment back in real time, drawn from the Digital Identity Network.
The name is screened
The KYC / AML module screens the customer's name and details through Bridger Insight XG against WorldCompliance data.
One decision
The fraud signal and the screening result meet your rules: a clean sign-up goes through, a risky device triggers a second factor, and a possible match waits in the review queue.
Every login after
ThreatMetrix keeps assessing later logins and payments, and if an answer is slow, the module decides on your own rules.
Sanctions stay current
LexisNexis updates WorldCompliance sanctions data up to four times a day, and the module rescreens customers so new designations reach your team.
Next to other providers
In fraud & risk, ThreatMetrix runs next to Sardine, SEON, Sift, Feedzai and Fingerprint: the module calls them in parallel, merges their signals into one decision, and keeps deciding on your rules if one is slow. In KYC / AML, WorldCompliance sits next to ComplyAdvantage, LSEG World-Check and Dow Jones.
The two connections are independent, so you can use ThreatMetrix without LexisNexis screening, or the other way round. Adding LexisNexis, or moving away from it later, leaves your apps and your queues as they are.
When LexisNexis Risk Solutions fits best
A strong fit when
- You want one provider for sanctions screening and for device-level fraud signals.
- You want fraud decisions informed by a network that shares digital identity intelligence across many businesses.
- Your policy needs sanctions data that is refreshed several times a day.
Also worth a look
- A device intelligence specialist such as Fingerprint, if device identification is all you need.
- A screening platform with transaction monitoring built in, such as ComplyAdvantage, if you want both in one place.
How we get you live
The contract
We help you get your LexisNexis Risk Solutions account and contracts in place, for screening, for ThreatMetrix, or both.
The settings
We set the screening settings with your compliance team, and with your risk team what ThreatMetrix's assessments should trigger.
The keys
The API credentials for Bridger Insight XG and ThreatMetrix go into your platform's secrets; your apps only carry the SDK that collects signals.
A full test run
Before go-live we run test sign-ups, logins and known names through both modules, and check that every outcome reaches the right queue.
