User Guide

Customizing Websites to use Fraud Management Filters
Fraud Management Filters API Prerequisites
34 June 23, 2009 Fraud Management Filters
txn_type = virtual_terminal
payment_date = 17:09:40 Jul 15, 2008 PDT
last_name =
receipt_id = 0739-3836-3393-2098
residence_country = US
item_name =
payment_gross = 2.11
mc_currency = USD
business = [e-mail]
payment_type = instant
verify_sign = AFcWxV21C7fd0v3bYYYRCpSSRl31ASrKFBPwac7aQm47p8CMLrdParSt
payer_status = unverified
test_ipn = 1
fraud_management_pending_filters_1 = Maximum Transaction Amount
tax = 0.00
txn_id = 53R82724RM1848354
fraud_management_pending_filters_2 = Unconfirmed Address
quantity = 1
first_name =
receiver_email = [e-mail]
payer_id = PUWAJRBB8NM74
receiver_id = 2RXLTRMGT3M2G
item_number =
payment_status = Denied
shipping = 0.00
mc_gross = 2.11
custom =
charset = windows-1252
notify_version = 2.4
Fraud Management Filters API Prerequisites
If your website uses PayPal APIs and you want to use FMF, you must detect transactions that
have been pended by Fraud Management Filters.
IMPORTANT: To use Fraud Management Filters with the PayPal API, you must use version
52.0 or higher of the PayPal API.
To detect transactions that have been pended by Fraud Management Filters, you must ensure
that your website meets the following criteria:
z You must handle Pending in the pending status of a response as representing a successful
payment.
z You must handle the SuccessWithWarning acknowledgement status in the response to
any of the following API operations that you use: BillUser
DoDirectPayment DoExpressCheckoutPayment DoReferenceTransaction