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 107
C
Testing Buyer Authentication
Transactions Using the Payflow SDK
This chapter describes the process of testing Buyer Authentication transactions using the
Payflow SDK. For complete information on using the SDK, 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.
In This Appendix
z “Testing Buyer Authentication Transactions” on page 107
z “Test Case Descriptions and Account Numbers” on page 107
z “Expected Result Codes for Buyer Authentication” on page 109
z “Buyer Authentication Testing Procedures” on page 110
Testing Buyer Authentication Transactions
Test cases are described in “Test Case Descriptions and Account Numbers” on page 107. Use
the card number associated with a test case and the appropriate password to generate the
results appropriate to the case.
Buyer Authentication Test Server
Direct Verify Enrollment transactions (TRXTYPE=E) and Validate Authentication
transactions (TRXTYPE=Z) to the test Buyer Authentication Server:
pilot-buyerauth.verisign.com
Payflow Test Server
Direct the standard Payflow sale or authentication test transaction to:
pilot-payflowpro.paypal.com
Test Case Descriptions and Account Numbers
To generate particular results, use the test account numbers listed in Table C.1.