Lola Bureau icon

Lola Bureau

Lola Bureau Node

Lola Bureau

AI-generated

Overview

The Lola Bureau node performs compliance and identity screening checks on individuals by querying various lists such as OFAC, Patriot Act, SDN, custom blacklists, and identity validation sources. It is useful in scenarios where organizations need to verify the background of a person for anti-money laundering (AML), know your customer (KYC), or general risk assessment purposes.

Practical examples:

  • Onboarding a new customer and checking if they appear on any government watchlists.
  • Validating the identity of a user before allowing access to sensitive services.
  • Screening employees or partners against internal or external blacklists.

Properties

Name Meaning
Screening Lists Select which lists to screen against. Options: All Lists (*), Black Lists Screening (OFAC, Patriot Act, SDN, etc.), Validate Identity, Custom Blacklist. Multiple can be selected.
Fail Early If enabled, stops further checks after the first failure.
First Name First name of the person to search. Required.
Last Name Family name of the person to search. Required.
Date of Birth Date of birth in YYYY-MM-DD format. Optional.
Nationality Country 3-letter country code (e.g., USA, MEX). Optional, defaults to "USA".
Address Address of the person to search. Optional.
City City of the person to search. Optional.
State 2-letter state code of the person to search. Optional.
Zip Code Zip code of the person to search. Optional.

Output

The node adds a field called lola_bureau to the output item's json property. The structure of this field depends on the selected screening lists:

{
  "lola_bureau": {
    "blacklists": { /* Result from blacklistScreening, includes status, trackId, etc. */ },
    "identity_validation": { /* Result from validateIdentity, includes status, trackId, etc. */ },
    "custom_lists": { /* Placeholder for custom blacklist results */ }
  }
}
  • Each key (blacklists, identity_validation, custom_lists) appears only if the corresponding list was selected.
  • If a check fails and "Fail Early" is enabled, the node outputs the item to the "rejected" output; otherwise, it continues processing and outputs to "success".

Dependencies

  • May require credentials named lolaKeyApi if configured.
  • Relies on internal helper functions for blacklist and identity validation checks.
  • No explicit environment variables are required unless specified by the credential setup.

Troubleshooting

Common issues:

  • Missing required fields: If "First Name" or "Last Name" are not provided, the node will fail.
  • Invalid date format: "Date of Birth" must be in YYYY-MM-DD format.
  • API errors: If the underlying screening service returns an error or non-success status, and "Fail Early" is enabled, processing will stop at that point.

Error messages:

  • "Blacklist Screening failed: <trackId>, since failEarly is true, it will not continue to the next list"
    Resolution: Check the input data and ensure the person is not on a blacklist, or disable "Fail Early" to continue with other checks.
  • "Validate Identity failed: <trackId>, since failEarly is true, it will not continue to the next checkpoint"
    Resolution: Verify the identity information provided is correct, or disable "Fail Early".

Links and References

Discussion