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. 

Howdy, everyone, we hope you are all having a great week!

We fixed an issue that would kick users out of the portal after clicking on transactions. It's magic!

Your feedback helps to keep us going, please let us know about any problems or issues you may have by submitting them here to our support site.

This week we've made some fixes to the manual check in the portal, rule descriptions when your mouse hovers over it, and possibly to the space-time continuum.  

All in a day's work to ensure a seamless experience for all of our clients. 

Your feedback helps to keep us going, please let us know about any problems or issues you may have by submitting them here to our support site.

We’ve tinkered with the internal workings and polished some rough edges (like bug fixes).

This includes some tweaks to the advanced settings in rules and optimizing the case management portal for a better experience. 

We are regularly making updates to our service to make it even better.

As always if you have any feedback from please submit them here to our support site.