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 13
1
Overview
This chapter discusses how fraud can affect you the merchant and provides an overview of
Fraud Protection Services.
In This Chapter
“Growing Problem of Fraud” on page 13
“Reducing the Cost of Fraud” on page 13
Growing Problem of Fraud
Online fraud is a serious and growing problem. While liability for fraudulent card-present or
in-store transactions lies with the credit card issuer, liability for card-not-present transactions,
including transactions conducted online, falls to the merchant. As you probably know, this
means that a merchant that accepts a fraudulent online transaction (even if the transaction is
approved by the issuer) does not receive payment for the transaction and additionally must
often pay penalty fees and higher transaction rates. (One notable exception, Buyer
Authentication, is described in this document.)
Reducing the Cost of Fraud
Fraud Protection Services, in conjunction with your Payflow service’s standard security tools,
can help you to significantly reduce these costs and the resulting damage to your business.
NOTE: Merchants must meet the following eligibility requirements to enroll in and use the
Fraud Protection Services products:
– Merchant must have a current, paid-in-full Payflow service account.
– Merchant Payflow service account must be activated (in Live mode).
– Merchant must have its business operations physically based in the United States of
America.
– Merchant must use one of the following terminal-based processors: American
Express Phoenix, FDMS Nashville, FDMS North, FDMS South, Global Payments
East, Nova, Paymentech New Hampshire, or Vital.