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
Fraud Protection Services User’s Guide 49
7
Screening Transactions Using
the Payflow SDK
This chapter describes the process of using the Payflow SDK to perform transactions that will
be screened by the Fraud Protection Services filters. For information on using the SDK, and on
transaction syntax, see Payflow Pro Developer’s Guide.
IMPORTANT:Recurring Billing transactions are not screened by Fraud Protection Services
filters.
Response Values. Payflow response values are described in “RESULT Codes and
RESPMSG Values” on page 45
.
Testing Filters. Information on testing filters appears in Appendix C, “Testing the
Transaction Security Filters.”
In This Chapter
z “Downloading the Payflow SDK (Including APIs and API Documentation)” on page 29
z “Transaction Parameters Unique to the Filters” on page 32
z “Existing Payflow parameters Used by the Filters” on page 32
z “Response Strings for Transactions that Trigger Filters” on page 34
z “Accepting or Rejecting Transactions That Trigger Filters” on page 40
z “Logging Transaction Information” on page 41
Downloading the Payflow SDK (Including APIs and API
Documentation)
The Payflow SDK is available either as a standalone client that can you can integrate with
your Web store using CGI scripts or as a set of APIs for direct integration with your
application. Payflow Pro Developer’s Guide The Payflow Pro Developer’s Guide provides
instructions for downloading the SDK appropriate to your platform.
IMPORTANT:Full API documentation is included with each SDK.
Transaction Data Required by Filters
This table lists each filter and the Payflow parameter values that are required by the filters.