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
Testing Buyer Authentication Transactions Using the Payflow SDK
Test Case Descriptions and Account Numbers
C
108 Fraud Protection Services User’s Guide
Account numbers starting with 5 are MasterCard. Numbers starting with 4 are Visa. In the
table, VE stands for the Verify Enrollment transaction and VA stands for the Validate
Authentication transaction.
Test Cases
TABLE C.1 Generating buyer authentication result
Case Test Scenario Test Account Number
1 Card enrolled (VE AUTH_STATUS=E)
Successful authentication (AUTH_STATUS=Y for VA)
Successful signature verification
5100000000000008
5200000000000007
4000000000000002
4000000000000101
2 Card enrolled (VE AUTH_STATUS=E)
Failed authentication (AUTH_STATUS=N for VA)
Successful signature verification
5100000000000008
5200000000000007
4000000000000002
4000000000000101
3 Card enrolled (VE AUTH_STATUS=E)
Attempt authentication (VA AUTH_STATUS=A)
Successful signature verification
4111111111111111
4 Card not enrolled (VE AUTH_STATUS=O) 5105105105105100
4000000000000507
5 Can not verify card enrollment (VE AUTH_STATUS=X) 5555555555554444
4012888888881881
6 Card eligible for authentication (VE AUTH_STATUS=E)
User cancelled authentication by clicking the Cancel
button on the ACS page.
5100000000000008
5200000000000007
4000000000000002
4000000000000101
7 Card enrolled for authentication (VE AUTH_STATUS=E)
Unable to authenticate (VA AUTH_STATUS=U)
Successful signature verification
5300000000000006
4000000000000309
8 Card enrolled (VE AUTH_STATUS=E)
VA transaction error (VA AUTH_STATUS=F)
5500000000000004
12 Merchant not registered for this feature or is deactivated.
(merchant authentication failure)
Any valid MasterCard or
Visa account number