### Managing Fraud Screening Filters

The Parallels Business Automation - Standard anti-fraud system provides the set of pre-defined filters:

- New Order Creation. The filter is activated when a customer places a new order in Store or from Control Panel Upgrade Center.
- Recurring Order Creation. The filter is activated when a renewal order or resource overusage order is generated.
- Authorization with Unchecked Payment Method. An order passes this filter if a new credit card (not saved on Parallels Business Automation - Standard database and by default assigned the Unchecked status) is used for payment and the Preauth-Capture transaction type is used. This filter is used to check an order before funds preauthorization. Normally, this filter is not very strict. The main reason for such a filter introduction is allowing a user to reach a transaction verification step, for example, if 3D Secure Check is used, when a customer enters .
- Authorization with Approved Payment Method. An order passes this filter if a credit card saved in Parallels Business Automation - Standard and having the OK status is used for payment and the Preauth-Capture transaction type is used. The filter is used to check an order before funds preauthorization. This filter has been introduced for the same reason as the "Authorization with unchecked payment method" one.
- Capturing with Unchecked Payment Method. An order passes this filter if a new credit card (not saved on Parallels Business Automation - Standard database and by default assigned the "Unchecked" status) is used for payment. This filter should be much more strict than the one used for authorization since it is used for the final check before funds capture is allowed.

  Note: The one-step transactions of the Sale type are checked with strict filters ("Capture with..."). In this case, no preliminary check with the use of "Authorization.." filters is performed.

- Capturing with Approved Payment Method. An order passes this filter if a credit card saved in Parallels Business Automation - Standard and having the OK status is used for payment. The filter is similar to the "Capture with Unchecked Payment Method".
- Account Registration. Checks customer data when a customer comes to your store first time and creates an account.
- Trial Order Creation. The filter is activated when a customer places a trial order in Store or from Control Panel Upgrade Center.
- Login. Checks a customer data when he/she logs in to the Parallels Business Automation - Standard tools with his/or her existing account.

Each filter can include a number of rules. A rule in its turn, defines both a fraud plug-in used for checking and a check result and then both an action performed and fraud points to be scored to an order in case a fraud plug-in response corresponds to a check result defined.

The table below shows the anti-fraud plug-ins usage in the anti-fraud filters:

Filter Plug-In | New Order Creation | Recurring Order Creation | Authori-zation with Unchecked Payment Method | Capture with Unchecked Payment Method | Authori-zation with Approved Payment Method | Capture with Approved Payment Method | Account Regist-ration | Trial Order Creation | Login Filter
Country Black List | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
IP Black List | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Phone Black List | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Credit Card Black List | No | No | Yes | Yes | Yes | Yes | No | No | No
Credit Card Validation | No | No | Yes | Yes | Yes | Yes | No | No | No
Dummy | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Email Check | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Email Black List | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
IP Country | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Domain Name Black List | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Phone Country | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Proxy Check | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
Try Count | No | No | Yes | Yes | Yes | Yes | No | No | No
USA Phone | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
VariLogiX | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No
ZIP Check | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
FraudGuardian | No | No | Yes | Yes | Yes | Yes | No | No | No
Order Amount | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No
Trial Count | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No
IP City | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
VAT Number | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes

Note: A set of plug-ins offered for a rule in the frame of a particular filter differs from filter to filter. This is connected with a filter designation. For example, for a Login filter the ProxyCheck, Dummy and both domain name and IP black lists are offered, because the Login filter checks a customer host and some other data. The Account Registration filter checks the data required for an account registration, i.e., a customer e-mail, phone, and country, so for this filter you can create rules that use Black Email, Black Phone, and Phone/Country fraud plug-ins.

Thus, each rule in a filter contributes to a total fraud score assigned to an order being checked. An order score then is being compared with a filter threshold score, which can be set both as a default value for all filters or adjusted specially for each filter. If an order fraud score exceeds a filter threshold, such an order will be placed into the Documents for Approval queue in Commerce Director - Online Payments - Documents.

Depending on a check condition, fraud points can be either scored to an order or taken from an order. For example, if a check condition is "Customer E-mail is not found in Email Black List", then if this is actually so, an order will be taken fraud points off, which will decrease a total fraud score and may let an order pass a fraud filter.

Each rule in a filter can be enabled or disabled and each filter can be activated or de-activated separately.

To set up a fraud filter and start using it:

1. Check the anti-fraud plug-ins configuration and if needed, adjust it.
2. Recommended: set the default score for all anti-fraud filters and rules.
3. If needed, adjust a filter threshold score. This will help you to define the fraud score assigned per rule in a filter since a filter threshold score is shown on a rule configuration screen.
4. Compose a set of rules in a filter. Make sure that rules you want to use in a filter are activated.
5. Activate a fraud filter.
6. Make sure that fraud screening is activated generally.

In This Section Setting Default Threshold Score for a Filter and Default Score for Rules Setting Anti-Fraud Filter Threshold Score Composing Rules for Anti-Fraud Filter Activating Fraud Filter

Please send us your feedback on this help page