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 49
Performing Buyer Authentication Transactions Using the SDK
Logging Transaction Information
6
Logging Transaction Information
A record is maintained of all transactions executed on your account. Use PayPal Manager to
view the record and use the information to help reconcile your accounting records.
NOTE: This record is not the official bank statement. The activity on your account is the
official record.
In addition, it is strongly recommended that you log all transaction results (except for check
information) on your own system. At a minimum, log the following data:
PNREF (called the Transaction ID in PayPal Manager reports)
Transaction Date
Transaction Amount
If you have any questions regarding a transaction, use the PNREF to identify the transaction.
Audit Trail and Transaction Logging
The Buyer Authentication server logs Verify-Enrollment transactions, PAREQ values, and
PARES values.
Verify Enrollment Transactions
Verify Enrollment transactions are logged when all of the following items occur:
The merchant passes data needed to perform buyer authentications.
The server connects to Visa or MasterCard and gets a meaningful response (card
enrollment AUTHENTICATION_STATUS=E, U, or X). If status is Y, then the PAREQ
value is logged along with the Verify Enrollment transaction data.
Otherwise, the transaction is not logged.
Validate Authentication Transactions
The Buyer Authentication server will log the PARES value only when all of the following
items occur:
There is a matching PAREQ (by Message ID, not by content) in the database.
There is no other PARES with the same Message ID in the database. This means that if a
duplicate PARES is submitted, it is logged only once.