User Guide

Introducing Fraud Management Filters
Fraud Management Filters Examples
8 June 23, 2009 Fraud Management Filters
1. Configure your Fraud Management Filters to flag, hold for review, or deny riskier
payments.
2. Based on your settings, your filters review incoming payments.
3. Your filters automatically, flag, deny, or hold payments for review; typically, most
payments are accepted because they do not show characteristics indicating fraud
A flexible fraud management configuration enables you to select the filters to use and to test
your strategy before denying payments or pending transactions for review. Advantages of
using Fraud Management Filters include
z time savings from having the computer do more to review transactions, and review them
consistently, which allows you to focus on transactions that are truly risky
z cost savings from identifying potentially risky transactions, which reduces chargebacks and
lowers your cost of doing business
z more accepted payments because you apply rules evenly with greater accuracy
Fraud Management Filters Examples
These examples show ways to configure Fraud Management Filters to flag or review
transactions and accept or deny payments. You must configure your filters before they take
effect.
Consider an example using four of the many kinds of filters provided by PayPal:
z Maximum Transaction Amount filter, which identifies transactions whose value exceeds a
specified amount
z Country Monitor filter, which identifies transactions based on the country of origin
z Card Security Code Mismatch filter, which identifies transactions with differences in the
credit card security code
z Total Purchase Price Minimum filter, which identifies transactions that are less than a
specified amount