User Guide

Fraud Management Filters June 23, 2009 11
Introducing Fraud Management Filters
Fraud Management Filters Examples
Filtering stops if the payment is denied. If the transaction originates from a country not on the
list, filtering continues.
Flagging Transactions With Invalid Card Security Codes
In this example, consider a scenario in which your experience indicates that customers
routinely mistype their credit card security code; however, in some cases, it is not an honest
mistake and can indicate fraud. Before you decide to review or deny this kind of payment, you
may decide to flag them first. After reviewing the flagged transactions, you can decide if
further action is necessary.
In this case, you could set the Card Security Code Mismatch filter to Flag, which would flag
the transaction:
Regardless of whether the transaction has been flagged, the next enabled filter is applied.
Flagging a transaction does not approve or deny a payment or pend the transaction for review.
Accepting Transactions Using the Total Price Minimum Filter
For the purpose of thinking about the operation of filters, the Total Price Minimum filter
determines the universe of payments on which the other filters operate. If the Total Price
Minimum filter is not enabled, the Fraud Management Filters universe includes all payments;
otherwise, the Fraud Management Filters universe includes all payments above the amount
specified by this filter.
NOTE: This filter is also the only filter that uses Accept to indicate that the filter does not
deny payments less than the specified amount.
Consider the following example in which the Total Price Minimum filter is set to Accept for
$10, In this case a $10 payment will be accepted and other filters will not be executed. If the
payment was for $11, other filters execute.