User's Guide
Table Of Contents
- Payflow 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
- 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
Fraud Protection Services User’s Guide 65
8
Responses to Credit Card
Transaction Requests
This chapter describes the contents of a response to a credit card transaction request.
In This Chapter
“An Example Response String” on page 65
“Contents of a Response to a Credit Card Transaction Request” on page 65
“PNREF Value” on page 66
“RESULT Codes and RESPMSG Values” on page 67
An Example Response String
When a transaction finishes, the server returns a response string made up of name-value pairs.
For example, this is a response to a credit card Sale transaction request:
RESULT=0&PNREF=VXYZ01234567&RESPMSG=APPROVED&AUTHCODE=123456&AVSADDR=Y&AVSZ
IP=N&IAVS=Y&CVV2MATCH=Y
Contents of a Response to a Credit Card Transaction Request
All transaction responses include values for RESULT, PNREF, and RESPMSG. A value for
AUTHCODE is included for Voice Authorization transactions. Values for AVSADDR and
AVSZIP are included if you use address verification system (AVS). Table 8.1 describes the
values returned in a response string.
TABLE 8.1 Transaction response values
Field Description Type Length
PNREF Reference ID, a unique number that identifies the
transaction. PNREF is described in
“PNREF
Format” on page 67
.
Alpha-
numeric
12
RESULT The outcome of the attempted transaction. A result
of 0 (zero) indicates the transaction was approved.
Any other number indicates a decline or error.
RESULT codes are described in
“RESULT Codes
and RESPMSG Values” on page 67
.
Numeric Variable