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
Responses to Credit Card Transaction Requests
PNREF Value
8
66 Fraud Protection Services User’s Guide
PNREF Value
The PNREF is a unique transaction identification number issued by the server that identifies
the transaction for billing, reporting, and transaction data purposes. The PNREF value appears
in the Transaction ID column in PayPal Manager reports.
CVV2MATCH Result of the card security code (CVV2) check. The
issuing bank may decline the transaction if there is a
mismatch. In other cases, the transaction may be
approved despite a mismatch.
Alpha
Y, N, X, or
no response
1
RESPMSG The response message returned with the transaction
result. Exact wording varies. Sometimes a colon
appears after the initial RESPMSG followed by
more detailed information. Response messages are
described in
“RESULT Codes and RESPMSG
Values” on page 67
.
Alpha-
numeric
Va ri ab le
PPREF Unique transaction ID of the payment.
If the TRXTYPE of the request is A, then you will
need the value of PPREF for use with Authorization
and Delayed Capture transactions.
string 17
AUTHCODE Returned for Sale, Authorization, and Voice
Authorization transactions. AUTHCODE is the
approval code obtained over the phone from the
processing network.
AUTHCODE is required when submitting a Force
(F) transaction.
Alpha-
numeric
6
AVSADDR AVS address responses are for advice only. This
process does not affect the outcome of the
authorization.
Alpha
Y, N, X, or
no response
1
AV S Z I P AVS ZIP code responses are for advice only. This
process does not affect the outcome of the
authorization.
Alpha
Y, N, X, or
no response
1
IAVS International AVS address responses are for advice
only. This value does not affect the outcome of the
transaction.
Indicates whether AVS response is international (Y),
US (N), or cannot be determined (X). Client version
3.06 or later is required.
Alpha
Y, N, X, or
no response
1
T
ABLE 8.1 Transaction response values (Continued)
Field Description Type Length