The engine has numerous rules available for configuration. There are several classes of rules that are assessed at the time of a transaction.
|Rule Class||Description||Example Rule|
|ShopperDNA Rules||These rules are calculated over the ShopperDNA network associated with a transaction. ShopperDNA allows merchants to track fraudsters across devices and networks and created rules on that entire network of transactions.||Shopper Has a Previous Chargeback|
|Referral Lists||These are lists of known good and bad shopper attributes (e.g. card numbers). Merchants can use these lists to ensure that loyal customers are unaffected and that known fraudsters are no longer able to attempt transactions.||Shopper Email Referral List|
|Consistency Rules||These are rules that look for known fraudulent trends in the customer behavior or data.||Shopper Using Anonymous Proxy|
|Velocity Rules||Velocity rules allow merchants to set specific thresholds on how often a shopper can attempt transactions in a given time period.||Shopper Email Usage Frequency|
|External risk checks||Plugins to various third-party risk mitigation systems that allow them to be used in coordination with RevenueProtect.||Perseuss Airline Check|
The engine rules are configured at the merchant account level. Depending on a merchant's fraud exposure, they may configure significantly different risk mitigation rules for each account. Generally speaking, merchants tend to isolate low-risk transactions from high-risk, enabling differentiated risk configurations for each profile.
Remember that transactions are blocked when their score reaches 100.
Note the following about the risk configuration setup:
Each rule has a score threshold associated with it. This is the score that adds to the aggregate transaction score if the rule triggers.
- Many rules need additional configuration. Click the pencil icon to configure the rule-specific settings for that rule.
- Inactive checks are not displayed by default. Click Show inactive checks to see rules that have been de-activated.