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 109
Testing Buyer Authentication Transactions Using the Payflow SDK
Expected Result Codes for Buyer Authentication
C
Expected Result Codes for Buyer Authentication
IMPORTANT:All returned name-value pairs for transactions with the Buyer Authentication
Server include length tags. Length tags specify the exact number of characters
and spaces that appear in the value. For example, RESPMSG[2]=OK.
The following Result Codes (RESULT return values) are associated with the Buyer
Authentication Service. The full list of Result Codes appears in “RESULT Codes and
RESPMSG Values” on page 68.
TABLE C.2 Buyer Authentication Service Result codes
Result
Code Description
0 Successful
3 Invalid transaction type
4 Invalid amount
7 Field format error
23 Invalid or missing account number
24 Invalid or missing expiration date
1001 Service unavailable
1002 Transaction timeout
1003 Invalid client version
1004 Invalid timeout value
101 Service unavailable
1012 Service unavailable
1013 Service unavailable
1014 Merchant has not activated buyer authentication for this card type
1021 Invalid card type
1022 Invalid or missing currency code
1023 Merchant has not activated buyer authentication for this card type
1041 Validate Authentication failed: missing or invalid PARES
1042 Validate Authentication failed: PARES format is invalid
1043 Validate Authentication failed: Cannot find successful Verify Enrollment
1044 Validate Authentication failed: Signature validation failed for PARES