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 Filter Reference
High-risk Address Filters
A
84 Fraud Protection Services User’s Guide
BIN Risk List Match Filter
What does the filter do?
The Bank Identification Number (BIN) makes up the first six digits of a credit card number.
The BIN identifies the bank that issued the card. This filter screens every credit card number
for BINs on the high-risk list.
The specified action is taken whenever a BIN matches one on the list.
How does the filter protect me?
Certain BINs might be associated with a greater degree of fraud because the issuer uses less
stringent authentication policies when issuing cards. In other cases, because some issuers have
a large number of cards in circulation, the cards are more likely to fall into the hands of
fraudsters.
Account Number Velocity Filter
What does the filter do?
The Account Number Velocity filter triggers when any credit card account number is used five
times within a three-day (72-hour) period.
IMPORTANT:The specified action is performed on only the transaction that triggered the
filter and not on the previous four transactions. You must manually review and
act upon those transactions. Generate a Transaction Details report and click
the Account Velocity link to view the transactions.
What is Velocity?
In the risk management industry, an event’s velocity is a measure of its frequency of
occurrence during a defined time period. Unusually high velocity is can be associated with a
fraudster making repeated attacks on a system. Legitimate customers do not typically perform
multiple transactions in quick succession.
How does the filter protect me?
Fraudsters often submit multiple purchases with a single account number to try to discover the
card’s valid billing address or card security code. Alternatively, the fraudster may attempt to
bypass ceiling filters by making multiple small purchases with a know good account number.
High-risk Address Filters
High Risk Address Filters identify transactions associated with high-risk geographical
locations or poorly-matched transaction data.