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
- Deactivating Fraud Protection Services
- Index
Fraud Protection Services User’s Guide 31
6
Performing Buyer Authentication
Transactions Using the SDK
This chapter describes the process of performing Buyer Authentication transactions using the
Payflow SDK. For information on using the SDK and on transaction syntax see Payflow Pro
Developer’s Guide.
The content and format of responses to transaction requests are described in “Buyer
Authentication Transaction Parameters and Return Values” on page 40. Standard Payflow Pro
response values are described in Payflow Pro Developer’s Guide.
XMLPay client support for Buyer Authentication is described in Payflow Pro XMLPay
Developer’s Guide.
For information on how to view Buyer Authentication reports in PayPal Manager, see PayPal
Manager online help.
Testing the Buyer Authentication Service
Testing the Buyer Authentication feature is not available at this time.
In This Chapter
“Buyer Authentication Transaction Overview” on page 31
“Buyer Authentication Terminology” on page 32
“Buyer Authentication Server URLs” on page 33
“Detailed Buyer Authentication Transaction Flow” on page 33
“Example Buyer Authentication Transactions” on page 37
“Buyer Authentication Transaction Parameters and Return Values” on page 40
“ECI Values” on page 44
“Logging Transaction Information” on page 46
Buyer Authentication Transaction Overview
To implement Buyer Authentication, you use the Payflow SDK to write software that:
1. Receives the customer’s account number and determines whether it is enrolled in the
Verified by Visa or MasterCard SecureCode buyer authentication program.