Rule match explanation

Audience tip

This article is relevant for Fraud Management SaaS users.

As an Admin, Senior Analyst, or Analyst, you can test if the existing rule logic would hit a past transaction you're examining. This is another way for you to understand your rule logic better.

To try it out, open a rule and go to Test rule match. Enter a Fraugster ID for a transaction (frg_id) in the dedicated field and select the version of the rule you'd like to test on. Run the test to see the result.

If the rule logic matches a past transaction, it means that similar transactions may be caught in the future – if the rule is active. If you don't see a match, review the rule logic and update it accordingly.

This feature not only helps you test a rule on a past transaction, but also helps you understand why a transaction was hit by a specific rule. To find the answer to this question, go to the Decision box, hover over a rule that hit a transaction and select Explain match.

Please consider how the testing of transactions happens. Two conditions are tested first, then the test result is tested on the next condition – and so on. All the conditions are not being tested simultaneously at the same time, as one may capture from the design of the rule logic. This design helps you view the logic and understand it better – the conditions, however, fire one at a time.