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
Screening Transactions Using the Payflow SDK
Response Strings for Transactions that Trigger Filters
7
60 Fraud Protection Services User’s Guide
Changing the Verbosity Setting
Setting the default verbosity level for all transactions
Contact Customer Service to set your account’s verbosity setting to LOW or MEDIUM for all
transaction requests.
Setting the verbosity level on a per-transaction basis
To specify a setting for verbosity that differs from your account’s current setting, include the
VERBOSITY=<value> name-value pair in the transaction request, where <value> is LOW or
MEDIUM.
NOTE: In the examples below, the <action> tag value is the state to which the transaction has
been set. Values are: R = Review, J = Reject, A = Accept.
Example Response for an Authentication Transaction With Verbosity=Low
RESULT=126&PNREF=VFHA28926593&RESPMSG=Under review by Fraud
Service&AUTHCODE=041PNI&AVSADDR=Y&AVSZIP=N&CVV2MATCH=X&HOSTCODE=A&PROCAVS=A
&PROCCVV2=X&IAVS=N&PREFPSMSG=Review: More than one rule was triggered for
Review&POSTFPSMSG=Review: More than one rule was triggered for Review
Example Response for an Authentication Transaction With
Verbosity=Medium
RESULT=126(0)&PNREF=VFHA28926593&RESPMSG=Under review by Fraud
Service(Approved)&AUTHCODE=041PNI&AVSADDR=Y&AVSZIP=N&CVV2MATCH=X&HOSTCODE=A
&PROCAVS=A&PROCCVV2=X&IAVS=N&PREFPSMSG=Review: More than one rule was
triggered for Review&FPS_PREXMLDATA[2898]=<triggeredRules><rule
num="1"><ruleId>2</ruleId><ruleAlias>CeilingAmount</ruleAlias><ruleDescript
128 Fraud Protection Services Filter — Declined by merchant after being flagged for review
by filters
131 Version 1 Payflow client no longer supported. Upgrade to the most recent version of the
Payflow client.
T
ABLE 7.6 Transaction RESULTs/RESPMSGs(Continued)
RESULT RESPMSG and Explanation