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
Content
4
Acting on Transactions that Triggered Filters . . . . . . . . . . . . . . . . . . . . . . 22
Rejecting Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Fine-tuning Filter Settings—Using the Filter Scorecard . . . . . . . . . . . . . . . . . . . 23
Ensuring Meaningful Data on the Filter Scorecard . . . . . . . . . . . . . . . . . . . 24
Re-running Transactions That Were Not Screened . . . . . . . . . . . . . . . . . . . . . 24
Chapter 5 Activating and Configuring the Buyer Authentication Service
25
Building Customer Confidence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Enrolling for the Buyer Authentication Service . . . . . . . . . . . . . . . . . . . . . . . . 25
Downloading the Payflow (Including APIs and API Documentation). . . . . . . . . . . . . 25
Configuring Buyer Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Generate Transaction Request Software . . . . . . . . . . . . . . . . . . . . . . . . 27
Testing and Activating the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 6 Performing Buyer Authentication Transactions Using the
SDK31
Testing the Buyer Authentication Service . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Buyer Authentication Transaction Overview . . . . . . . . . . . . . . . . . . . . . . . . . 31
Buyer Authentication Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Buyer Authentication Server URLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Detailed Buyer Authentication Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . 33
Call 1: Verify that the cardholder is enrolled in the 3-D Secure program . . . . . . . . 33
Call 2: POST the authentication request to and redirect the customer’s browser to the ACS
URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Call 3: Validate the PARES authentication data returned by the ACS server . . . . . . 36
Call 4: Submit the intended transaction request to the Payflow server . . . . . . . . . 36
Example Buyer Authentication Transactions. . . . . . . . . . . . . . . . . . . . . . . . . 37
Example Verify Enrollment Transaction . . . . . . . . . . . . . . . . . . . . . . . . . 38
Example Verify Enrollment Response . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Example Validate Authentication Transaction . . . . . . . . . . . . . . . . . . . . . . 38
Example Payflow Authorization or Sale Transaction . . . . . . . . . . . . . . . . . . 39
Buyer Authentication Transaction Parameters and Return Values . . . . . . . . . . . . . 40
Transaction Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Verify Enrollment Transaction Name-Value Pairs . . . . . . . . . . . . . . . . . . . . 40
Validate Authentication Transaction Name-Value Pairs . . . . . . . . . . . . . . . . . 42
Standard Payflow Sale or Authorization Transaction . . . . . . . . . . . . . . . . . . 43
ECI Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44