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 Protection Services User’s Guide 79
Fraud Filter Reference
High-risk Payment Filters
A
is using a stolen identity to complete a purchase (and having the items sent to another address
from which they can retrieve the stolen items).
To help to distinguish between legitimate and fraudulent orders, review all mismatches by
cross-checking other purchase information such as AV S and card security code.
Product Watch List Filter
What does the filter do?
The Product Watch List filter compares the SKUs (or other product identifier) of the products
in a transaction against a Product Watch List that you create. Any transaction containing an
SKU in the list triggers the filter. If you enable this filter, then you must set up the list of
products that should be monitored.
NOTE: Items that you enter in the test Product Watch List are not carried over to the
configuration for the live servers, so do not spend time entering a complete list for the
test configuration.
How does the filter protect me?
Some products are attractive to fraudsters (especially popular products with high resale value
like computers or televisions). The Product Watch List filter gives you the opportunity to
review transactions involving such products to ensure that the order is legitimate.
High-risk Payment Filters
High-risk Payment Filters identify transactions that show billing/shipping discrepancies or an
indication that someone other than the legitimate account holder is initiating the transaction.
AVS Failure Filter
What does the filter do?
This filter compares the street number and the ZIP code submitted by the customer against the
data on file with the issuer.
The AVS response is composed of a Y, N, or X value for the customer’s street address and a Y,
N, or X value for the ZIP code. For example, the response for a correct street number and an
incorrect ZIP code is YN.