Rule manager overview

Audience tip

The articles in this section are relevant for Fraud Management SaaS users.

Rule manager is a risk management suite that allows you to combine your expertise with the Fraugster artificial intelligence. With Fraud Management SaaS, you are in charge of your organization’s risk management. You create rules to catch a specific behavior or pattern within a transaction.

In Fraud Management SaaS, the data that you send via the Fraugster API defines the set of datapoints and attributes available to you during the rule creation. You create fraud prevention rules as granular as the data allows and the business requires.

Rules allow you to take action whenever a payment matches a criteria that you define. For each transaction, Fraugster evaluates risk, so you can use this information also to create unique business logic.

Did you know?

Fraugster Engine gives each transaction a numerical risk score between 1 and 100, where 1 is the least risky and 100 is the riskiest. You decide what your blocking threshold should be according to your business needs. For example, your business may have low fraud rates. In this case, you may want to set a high default score at which Rule manager blocks a transaction. This allows more payments to go through. Alternatively, you may want to customize the score in order to decrease fraud even further. In this case, you might want to pick a rather low default score in your rules. This allows Rule manager to block potentially fraudulent transactions more aggressively.

How it works

Use rules to catch a specific behavior or pattern within a transaction. A rule applies a certain decision:

• Approves a transaction
• Declines a transaction
• Watches a transaction
• Sends a transaction for manual review
• Applies a PSD2 exemption

Go to Fraud management → Rules in the side navigation to get started with rules. Depending on its status, a rule can be located under Published, Changes, or Drafts.

Unpublished rules don’t have any impact on live transactions. A new rule or draft starts affecting live transactions when you publish it.