Rule properties overview

Audience tip

This article is relevant for Fraud Management SaaS users.

Each rule has specific properties, let's look at them in detail.

Rule ID

A rule ID is an automatically generated human-readable number that identifies the rule. It allows you to see order and recency. It’s located in front of the rule name. To find a specific rule, you can search by rule name or ID.

Example: #45

Rule name

A form of identification that should be straightforward and self-explanatory. You add the name manually when you create a new rule. Providing an accurate and clear name helps other users understand what the rule does. Fraugster highly recommends that you develop naming conventions within your organization.

As an Admin, Senior Analyst, or Analyst, you can edit a rule's name anytime in Rules.

Rule name example:

General: Velocity CC over email – 1 day

• General – applies to all merchants.
• Velocity – stands for the frequency of transactions incoming from one individual.
• CC over email – points out that different credit cards are being used with the same email address.
• 1 day – specifies the time range.

Rule description

A rule description clarifies what the rule does. You add a description manually when creating a new rule. As an Admin, Senior Analyst, or Analyst, you can edit a rule's description anytime in Rules.

Tips on writing a good rule description:

• Explain what the rule does.
• Possibly include background information. Why was this rule written? Does it apply to a general fraud pattern or a current trend?
• Include measurements for the rule's performance.
• Include notes if necessary, anything important that you want other colleagues to know.

Example:

General: Velocity CC over email – 1 day

Description: We decline transactions when the same email address is used with three or more credit cards within one day. In September 2018 this rule hit 100 bad transactions and 100 false positives. The ratio is 1:1.

Action

A rule action defines what the rule does. The following actions are available:

• Approve allows a transaction that otherwise would have been rejected to go through.
• Decline blocks an incoming transaction.
• Watch doesn't perform any specific action, but marks a transaction for later analysis.
• Manual review doesn't perform any specific action, but marks a transaction for manual review. The transaction is added to the section Manual review in the side navigation. As no further action is triggered, it depends on the gateway or merchant implementation if the transaction is forwarded to authorization.
• PSD2 exemption approves a transaction if it qualifies for a specific exemption type.
• Custom triggers an action on your side as defined by you. Read more in Custom actions.

Labels

Labels are words or combinations of words you add to rules to improve your search experience. You can add labels related to the datapoints or attributes you are using, or any other information that would be helpful to filter rules and run reports.

Labels appear on each rule on the Rules page. Hover over the number of hidden labels to have them displayed. Label examples include:

Labels also appear below the rule name.

Label	Description
Action	The first label displays the action the rule applies – approve, decline, watch, manual review, or PSD2 exemption. For example,
Priority	Defines rule's importance in relation to other rules. Rule manager offers three levels of priority – low, medium, and high. Examples:

Priority

A rule's priority defines its importance in relation to other rules. Fraud Management SaaS provide three levels of priority:

• High
• Medium
• Low

When multiple rules within the same ruleset hit a transaction, Fraugster applies the following prioritization flow to determine which rule should take priority. The order of events is relevant here:

1. Check rule vs. list priority. Lists have priority over rules. Approve lists take priority over decline lists.
2. Check he priority of each rule – high, medium, low.
3. Check the action priority (high to low) – approve → decline → manual review → psd2 → custom.
4. Check the custom priority – within the custom group only.
5. Check the ID of the rule – the rule with the lower ID (i.e. the rule created earlier in time) takes priority over its younger counterpart.

Search

To find a specific rule, you can search by the rule ID or name.

Additionally, you can filter your rules by:

• Rule name or ID
• Rule action
• Datapoints/attributes used in rules
• Labels
• User that created the rule

Use in the top-right corner of the page to customize the view of the Rules page.