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 59
Screening Transactions Using the Payflow SDK
Response Strings for Transactions that Trigger Filters
7
NOTE: If you use Nashville, TeleCheck, or Paymentech, then you must use a client version
newer than 2.09 to take advantage of the MEDIUM verbosity setting. For information
on interpreting the responses returned by the processor for the MEDIUM Verbosity
setting, contact your processor directly.
The table below shows the increments that are possible on basic TRANSSTATE values.
RESULT Values Specific to Fraud Protection Services
A RESULT value greater than zero indicates a decline or error. For this type of error, a
RESPMSG name-value pair is included. The exact wording of the RESPMSG may vary.
Sometimes a colon appears after the initial RESPMSG followed by more detailed information.
BATCHID Integer 10 Value available only after settlement
has assigned a Batch ID.
SETTLE_DATE Date format
YYYY-MM-
DD
HH:MM:SS
19 Value available only after settlement
has completed.
T
ABLE 7.5 TRANSSTATE value increments
Increment Meaning
+100 No client acknowledgment (ACK) is received (=status 0 in V2), for example, 106 is
TRANSSTATE 6.
+200 The host process never receives ACK from the transaction broker (or backend
payment server). A transaction with a TRANSSTATE of +200 is basically in limbo
and will not be settled.
+1000 Voided transactions. Any TRANSSTATE of +1000 (for example, 1006) means the
transaction was settle pending. However, it was voided either through the API
PayPal Manager, or Customer Service.
T
ABLE 7.6 Transaction RESULTs/RESPMSGs
RESULT RESPMSG and Explanation
125 Fraud Protection Services Filter — Declined by filters
126 Fraud Protection Services Filter — Flagged for review by filters
127 Fraud Protection Services Filter — Not screened by filters
T
ABLE 7.4 Medium VERBOSITY parameters
Parameter Type Length Description