User's Guide
Table Of Contents
- Payflow Fraud Protection Services User’s Guide
- Preface
- Overview
- How Fraud Protection Services Protect You
- Configuring the Fraud Protection Services Filters
- Assessing Transactions that Triggered Filters
- Activating and Configuring the Buyer Authentication Service
- Performing Buyer Authentication Transactions Using the SDK
- Testing the Buyer Authentication Service
- Buyer Authentication Transaction Overview
- Buyer Authentication Terminology
- Buyer Authentication Server URLs
- Detailed Buyer Authentication Transaction Flow
- Call 1: Verify that the cardholder is enrolled in the 3-D Secure program
- Call 2: POST the authentication request to and redirect the customer’s browser to the ACS URL
- Call 3: Validate the PARES authentication data returned by the ACS server
- Call 4: Submit the intended transaction request to the Payflow server
- Example Buyer Authentication Transactions
- Buyer Authentication Transaction Parameters and Return Values
- ECI Values
- Logging Transaction Information
- Screening Transactions Using the Payflow SDK
- Downloading the Payflow SDK (Including APIs and API Documentation)
- Transaction Data Required by Filters
- Transaction Parameters Unique to the Filters
- Existing Payflow Parameters Used by the Filters
- Response Strings for Transactions that Trigger Filters
- Accepting or Rejecting Transactions That Trigger Filters
- Logging Transaction Information
- Responses to Credit Card Transaction Requests
- Fraud Filter Reference
- Testing the Transaction Security Filters
- Good and Bad Lists
- AVS Failure Filter
- BIN Risk List Match Filter
- Country Risk List Match Filter
- Email Service Provider Risk List Match Filter
- Geo-location Failure Filter
- International IP Address Filter
- International Shipping/Billing Address Filter
- IP Address Match Filter
- Shipping/Billing Mismatch Filter
- Total Item Ceiling Filter
- Total Purchase Price Ceiling Filter
- Total Purchase Price Floor Filter
- USPS Address Validation Failure Filter
- ZIP Risk List Match Filter
- Deactivating Fraud Protection Services
- Index
Fraud Filter Reference
High-risk Customer Filters
A
88 Fraud Protection Services User’s Guide
fraudster making repeated attacks on a system. Legitimate customers do not typically perform
multiple transactions in quick succession.
How does the filter protect me?
Fraudsters often submit multiple purchases using an automated script that tests unknown card
numbers. Alternatively, the fraudster may attempt to bypass other filters by making multiple
small purchases with multiple stolen account numbers.
High-risk Customer Filters
Bad Lists
What does the filter do?
This filter compares the customer’s e-mail address and credit card number against lists (that
you create) of addresses and numbers for known bad customers.
NOTE: Unlike the Risk lists managed by PayPal, you, solely, manage and update the Bad
Lists.
Any transaction that is an exact match with an entry in one of your bad lists triggers the filter.
If you enable this filter, then your next step will be to set up lists of bad email addresses and
bad card numbers. Be sure to type the e-mail addresses and credit card numbers accurately.
Enter only numerals in the credit card number list—no spaces or dashes.
NOTE: Items that you enter in the test Bad lists are not carried over to your configuration for
the live servers, so do not spend time entering a complete list for the test configuration.
How does the filter protect me?
This filter enables you to block repeat fraud.
In the e-commerce world, once someone successfully performs a fraudulent transaction, they
are very likely to try again. For this reason, you should set up lists of cards and email addresses
and configure this filter to take action on transactions with data elements appearing in the bad
lists.
International Order Filters
International Order Filters identify transactions associated with risky international locations.