PEP Status for Legal Entity Relationships
You can now add PEP status for legal entities that are shareholders, associated parties, or business partners of a business user.
This feature is particularly useful when the ultimate beneficial owners (UBOs) of a shareholder company are PEPs, allowing you to flag the entity relationship for enhanced due diligence and risk scoring.
PEP status can be updated via API with fields for PEP country, rank, category, and a boolean to mark as yes or no. See our API documentation for implementation details.
String Concatenation in Rule Configuration
You can now concatenate up to 3 strings in rule configuration, enabling more flexible rule logic.
This is particularly useful when you need to compare a full name composed of three variables, such as first name + middle name + last name, against screening results or other data fields.
To use string concatenation, use the "Concat String" function in rule logic and configure your rule conditions to combine the desired fields in the rule builder.
Multiple Users per Device Detection
You can now create alerts when a certain number of users share the same device ID, helping identify potential account takeover or fraud patterns.
This can be set up using the library template R-52, which monitors device ID usage across user accounts and triggers alerts based on your specified threshold.
To configure this rule, navigate to your rules library and customize template R-52 with your desired user count threshold.
Expected Transaction Countries
You can now add expected transaction countries for both business and consumer users to enhance geographic risk monitoring.
This information can be used in rules to trigger alerts when transactions are made from unexpected countries, helping you identify unusual activity patterns and potential fraud.
To add expected transaction countries, update the user profile via API. See our API documentation for implementation details.
Enhanced Screening Hit Details via API
You can now retrieve more comprehensive screening hit details using the GET Retrieve Alert Hits API endpoint.
Additional details now include aliases, associates, profile notes, images, PEP sources, sanctions sources, and REL sources. This expanded information helps you conduct more thorough investigations and make better-informed decisions on screening matches.
See our API documentation for details on retrieving these enhanced screening hit fields.
New Crypto Networks Added
BASE and HYPERLIQUID have been added to the list of supported crypto networks.
You can now track and monitor transactions on these networks for comprehensive cryptocurrency compliance coverage.
Assigned To Filter in User Profile Alerts
The "Assigned to" filter has been added to the alerts table within users' profiles.
This allows you to quickly filter alerts based on who they're assigned to, making it easier to track team member workloads and find specific alerts during investigations.
Zendesk Ticket Alerts
You can now create alerts based on Zendesk ticket custom field values.
This allows you to automatically flag compliance-related support tickets for investigation, helping you identify potential risks reported through customer service channels.
To configure Zendesk-based alerts, set up the entity variable "Zendesk ticket field" and configure rules that monitor the custom field values you want to track.