User's Guide
Table Of Contents
- Payflow Pro 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
- Freight Forwarder 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
- Testing Buyer Authentication Transactions Using the Payflow SDK
- Deactivating Fraud Protection Services
- Index
Payflow Link Fraud Protection Services User’s Guide 23
Assessing Transactions that Triggered Filters
Fine-tuning Filter Settings—Using the Filter Scorecard
4
This information is especially helpful in fine-tuning your risk assessment workflow. For
example, if you find that you are reviewing too many transactions, then use the Filter
Scorecard to determine which filters are most active. You can reduce your review burden by
relaxing the settings on those filters (for example, by setting a higher amount for the Purchase
Price Ceiling filter).
1. Click Reports > Filter Scorecard. The Filter Scorecard Report page appears.
FIGURE 4.2 Filter Scorecard Report page
2. Specify the date range of the transactions to review.
3. In the Transaction Mode field, specify transactions screened by the live or the test servers.
4. Click Run Report.
The Filter Scorecard Report page displays the number of times that each filter was
triggered and the percentage of all transactions that triggered each filter during the time
span that you specified.
Ensuring Meaningful Data on the Filter Scorecard
The Scorecard shows the total number of triggered transactions for the time period that you
specify, so if you had changed a filter setting during that period, the Scorecard result for the
filter might reflect transactions that triggered the filter at several different settings.
Say, for example, you changed the Total Purchase Price Ceiling on August 1 and again on
August 7. You then run a Filter Scorecard for July 1 to August 31. Between July 1 to August