Skip to main content
Version: 🚧 Next

LexisNexis

:::info V2 → V3 migration note The Data Plus V3 provider is functionally equivalent to Data Plus V2. No configuration/mapping behavior was changed. The only change is technical: V3 uses OAuth2 instead of basic authorization. As part of this migration, your authentication.clientSecret must be the OAuth2 client secret generated in your LexisNexis account (it is no longer the old password-style secret). :::

🎯 Functional documentation​

This provider uses basic party data (name, birthdate, etc.) and country code data fields (nationality, address, etc.) from the party to construct a request to the Lexis Nexis service. The response of the service is then mapped to one or more Due Diligence (DD) parameters, which will be set to YES or NO (depending on the presence of the corresponding segments in the response).

Input data points​

  • Individual
    • First name
    • Last name
    • Date of birth
    • Place of birth
    • Gender
    • Address
  • Company
    • Name

DD parameters mapping​

This V3 provider supports dynamic mapping of LexisNexis segments to CDD parameters. You can map any LexisNexis segment (from the list below) one-to-one to any CDD parameter defined in your RBA JSON configuration.

Currently Supported LexisNexis Segments for Direct Matching:

  • PEPs
  • Enforcements
  • AdverseMedias
  • Sanctions
  • SOEs

Currently Supported LexisNexis Segments for Relationship Matching:

  • Any segment present in the LexisNexis response under the WatchLists -> Matches -> Match -> Relationships -> Segment CSV string is supported.

Example of key–value mapping:

  • "PEPs": "PEP"
  • "Enforcements": "ADVERSE_MEDIA"
  • "AdverseMedias": "SANCTION_LIST"
  • "Sanctions": "CRIMINAL_ACTIVITIES"

⚙️ Configuration​

Required authorization settings​

  • clientId
  • clientSecret

Implementation class​

  • Implementation class: LexisNexisDataPlusV3DueDiligenceProvider
  • Resource uri: https://staging.bridger.lexisnexis.eu/LN.WebServices/api

Settings​

  • authentication (required)
    • clientId (required)
    • clientSecret (required)
    • userId (required)
  • searchName (required): The name of the search to be used. Gets sent in the PredefinedSearchName field to the API.
  • API_KEY (required): The API key used for authentication with the Lexis Nexis API. Gets sent as an X-API-Key header to the API.
  • DUE_DILIGENCE_DOCUMENT_FETCH (optional): Generates a report. See DD document creation.
  • companyParameterMapping (required): Defines how LexisNexis DataPlus segments map to CDD parameters for companies.
    • Must include both directMatches and relationshipMatches objects. They can be empty but cannot be omitted or null.
  • individualParameterMapping (required): Defines how LexisNexis DataPlus segments map to CDD parameters for individuals.
    • Must include both directMatches and relationshipMatches objects. They can be empty but cannot be omitted or null.

Example Settings​

Settings Configuration

Examples

note
  • In the example above, each key-value pairs in directMatches and relationshipMatches (eg - "AdverseMedias": "ADVERSE_MEDIA"),
    • The key 'AdverseMedias' represents the segment name from the LexisNexis provider response
    • The value 'ADVERSE_MEDIA' represents the corresponding CDD parameter defined in the RBA JSON configuration.
  • Segment names (keys) are case-sensitive. refer above given list of supported Direct & Relationship Mapping segments.
  • CDD parameter (values) are case-sensitive and must exactly match the case defined in the RBA JSON (generally ALL UPPER CASE).