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 67
Responses to Credit Card Transaction Requests
PNREF Value
8
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.
z The PNREF value is used as the ORIGID value (original transaction ID) in delayed capture
transactions (TRXTYPE=D), credits (TRXTYPE=C), inquiries (TRXTYPE=I), and voids
(TRXTYPE=V).
z The PNREF value is used as the ORIGID value (original transaction ID) value in reference
transactions for authorization (TRXTYPE=A) and Sale (TRXTYPE=S).
NOTE: The PNREF is also referred to as the Transaction ID in Payflow Link documentation.
PNREF Format
The PNREF is a 12-character string of printable characters, for example:
z EFHP0D426838
z ACRAF23DB3C4
NOTE: Printable characters also include symbols other than letters and numbers such as the
question mark (?). A PNREF typically contains letters and numbers only.
The PNREF in a transaction response tells you that your transaction is connecting to the
server.
Historically, the contents of a PNREF indicated a test or a live transaction. However, this is not
always the case, and as a rule, you should not place any meaning on the contents of a PNREF.
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