For Fraud.net clients that use E-commerce and Marketplace APIs, we have refactored how the product filters work within rules. 

Previously
Product rule filters evaluated the entire product object across all items in a transaction, leading to potential false positives. For example:

Rule: Product Price > $125 AND Product Brand is Nike THEN send to queue
Products Purchased: $135 Converse shoes + $75 Nike shoes
Result: Transaction sent to queue, as one product met the price, and another met the brand condition, even though no single product matched both.

Currently
Filters evaluate each product individually, reducing false positives and aligning rule results with the intent.

Rule: Product Price > $125 AND Product Brand is Nike THEN send to queue (same as above)
Products Purchased: $135 Converse shoes + $75 Nike shoes (same as above)
Result: Rule does not trigger.

This update ensures rules now focus on relevant products, helping investigators target the intended transactions. Active rules with multiple product filters will now behave in the way described in the Currently example.

improvement Investigators now have access to additional alert details on the Alert Detail Page and when expanding an alert from the Alert Discover Page, providing information the investigator wouldn’t get prior. This enhancement helps in assessing the severity of the alert by displaying the following fields:

• Threshold: The set threshold for the alert.
• Value: The actual value that triggered the alert.
• Difference: The difference between the threshold and the value

Alert Discover Page View

Alert Detail Page View

Update SSO Auth Link

We have improved the SSO (Single Sign-On) authentication process. Now, after logging in through SSO, users will be smoothly redirected to the correct page.

fix Bug Fixes

• IPv4 Address Error Fix
  An issue where an IPv4 address provided in its standard format caused errors has been resolved. The system now correctly converts IPv4 addresses, preventing this error from occurring.
• Customer History View: Users were unable to view specific customer transactions in the customer history, resulting in over 4000 unrelated records being displayed. The customer history card now correctly displays transactions associated with the relevant customer.
• Default Team Membership: Users in the default team had unrestricted access to all transactions. Additionally, when trying to edit a team member’s access under ‘Admin’ → ‘Management,’ it displayed an invitation modal rather than an edit modal to remove or restrict access. 

Driven by valuable user feedback, we are excited to announce significant improvements to our platform. These updates are designed to enhance your user experience, making it more efficient and intuitive. Here's what's new:

Improved Header Design

We've redesigned the header to be more compact, freeing up space for more detailed views. With this change, more data is visible at any given time allowing for quicker and more efficient investigation.

Header Before:

Header After:

Network History Added Functionality

• Sorting Functionality: Entries can be sorted by different metrics such as date or amount.
• Default View: By default, you can now view network history spanning the last 90 days, providing a more comprehensive overview.
• Paging Functionality: Access up to 100 entries at a time, making investigating more efficient.
• Dedicated Network History Tab: Users can opt in to have network history on it's own tab. This will allow investigators more space to investigate related transactions instead of within a card on the overview tab.

Thank you for your continuous feedback and support. We remain committed to enhancing your experience with our platform. 

We're excited to announce improvements to Entity Monitoring designed to provide you with greater insights into case closures and enhance the identification of potentially risky contacts.

Improved Case Closure with Labels

Investigators using Entity Monitoring for banking marketplaces can now select a relevant label when closing a case. This provides valuable context into the reason for closure and facilitates reporting through Kibana.

New App: EnBanca’s Contactability Score

The new EnBanca's Contactability Score compares the relationship and contactability of contact information (email address, phone number, and name) against identification details provided during an application or transaction. This score, based on Colombian data and ranging from 1 to 100, helps you assess the potential risk associated with a particular contact.

announcement 

This week we are excited to announce new enhancements to our Entity Monitoring Rules Management system. These updates introduce more flexibility and precision in creating and managing rules. Key features include:

1. Entity Monitoring Rules Management:

   • Rules can now be defined based on the entity, not just the event.

2. Rule Categories:

   • Policy Enforcement: Standard rules for enforcing policies.
   • Policy Forecasting: Includes logic for comparing different time periods using multipliers.
   • Custom (Event-Based): Allows for event-specific rule creation.
     

3. Advanced Rule Settings:

   • Combine "and" and "or" conditions within the same rule for greater complexity.
     

4. Alert Management:

   • Set alert priorities and automatically create cases when alerts are triggered.
     

5. Target Assignment:

   • All rules must be assigned a specific target.
   • Note: Calculations based on a target are pending implementation.

Additional Enhancements:

• Filters for Policy Targets and Segmentation: New filters have been added, allowing for more precise definitions and usage.

fix 

• Resolved an issue with the velocity rule involving actual currency.
• Fixed a Single Sign-On (SSO) problem.
• Addressed issues related to rules not properly displaying in Events 2.0.

announcement 

In this release we've implemented several updates to the Entity Monitoring case management portal designed to enhance navigation and usability across entities, alerts, and cases pages. Key improvements include:

1. Enhanced Alert Discover and Management Pages:
   • Linked transactions are no longer displayed on these pages, allowing up to 25 alerts to be shown at once.
   • Previously, linked transactions occupied 50% of the page space, limiting the view to only 2-3 alerts at a time.

1. New Alert Detail Page:
   • Users can now open a new tab from the Alert Discover or Management page to view all linked transactions and details related to a specific alert.
   • This page also includes links to all entity events and the entity overview page.

Looking forward we will be adding the entity name to the Alert Discover page and the priority of alerts will be added to the Entity Discover page.

fix 

• Improved Single Sign-On (SSO) functionality.
• Resolved duplicate filter issue in the User Persona Age filter.
• Limited network history display to the 100 most recent events.

announcement Following our past release, we're thrilled to introduce Segmentation features to Entity Monitoring! This feature empowers users to create and manage Segmentation Groups, enabling more tailored and efficient management of information. Here's what you can expect:

1. Create and manage Segmentation Groups: Users can now easily create and manage Segmentation Groups, such as MCCs or Countries, to categorize and organize their data effectively.
2. Create and manage Segmentations within the group: Within Segmentation Groups, users have the flexibility to create and manage specific Segmentations, such as Lodging, Retail, and Airlines, or Germany, Canada, and Mexico, depending on their business needs.
3. Policy Threshold Exceptions: When setting policy thresholds, segmentation becomes a powerful tool for creating exceptions to default thresholds. This allows for more granular control and customization based on different segments within your data.

Segmentation Creation and Management

The most recent release included updates to Entity Monitoring. This is in addtion to the prior updates clients received of being able to view events, cases, and alerts by entity, updated fields, and design updates. Now clients have the ability to view transactions linked to an alert in Entity Monitoring. 

Another exciting update to Entity Monitoring are status configurations. Admin users are now able to add a status to entities, alerts, and cases. Stay tuned for more Entity Monitoring updates to follow!

fix 

Improved Team SLA and Watchlist Rule functionality and fixed the Transaction Discovery page to ensure an accurate status is shown. 

The release for this week includes additions to the Alert Module dropdown, additional functionality to Events 2.0, expanded availability for Sayari Apps, and bug fixes.

announcement 

Now with the Alert Module dropdown clients are able to view metrics of the alert such as the source, sub-type, difference, rule threshold, and velocity. 

Events 2.0 now has enhanced event management with the added functionality of the 'Go to Next Transaction' Module, simplifying navigating your transactions. Additionally, endless scroll in network history has been enabled creating a seamless user experience. 

Lastly, enhanced the reliability of velocity rules, addressing the issues reported by users.