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
Assessing Transactions that Triggered Filters
Reviewing Suspicious Transactions
4
24 Fraud Protection Services User’s Guide
Acting on Transactions that Triggered Filters
The Fraud Details page displays the data submitted for a single transaction. The data is
organized to help you to assess the risk types and to take action (accept, reject, or continue in
the review state).
The following notes describe data in the Fraud Details page shown in the figure.
1. This transaction was set aside because it triggered the AVS Failure filter.
2. The transaction was not screened by any of the filters in the Skipped Filters section because
the data required by these filters did not appear in the transaction data or was badly
formatted. In special cases, all filters appear here. See “Re-running Transactions That Were
Not Screened” on page 26
3. Specify the action to take on the transaction:
– Review: Take no action. You can return to this page at any time or reject or accept the
transaction. The transaction remains unsettleable.
– Reject: Do not submit the transaction for processing. See “Rejecting Transactions” on
page 24.
– Accept: Submit the transaction for normal processing.
4. You can enter notes regarding the disposition of the transaction or the reasons for taking a
particular action. Do not use the & < > or = characters.
5. Click Submit to save the notes, apply the action, and move to the next transaction.
NOTE: You can also view the Fraud Details page for transactions that were rejected or
accepted. While you cannot change the status of such transactions, the page provides
insight into filter performance.
Rejecting Transactions
If you decide to reject a transaction, you should notify the customer that you could not fulfill
the order. Do not be explicit in describing the difficulty with the transaction because this
provides clues for performing successful fraudulent transactions in the future. Rejected
transactions are never settled.