User's Guide
Table Of Contents
- Payflow Pro 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
- Freight Forwarder 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
Activating and Configuring the Buyer Authentication Service
Configuring Buyer Authentication
5
26 Fraud Protection Services User’s Guide
IMPORTANT:Full API documentation is included with each SDK.
Configuring Buyer Authentication
To enable Buyer Authentication processing on your site, you will need to construct two
transaction requests (messages) and construct a frameset. You can accomplish the tasks in a
few hours.
In the standard Payflow Pro implementation, when the customer submits a purchase request,
your website sends a single Sale transaction request with all purchase details (message with
transaction type S) to the server. With Buyer Authentication, you must submit two additional
transaction requests (types E— Verify Enrollment and Z—validate PARES response) before
the Sale.
Follow these steps:
1. Log in to PayPal Manager at
https://manager.paypal.com/
2. Click Service Settings > Fraud Protection > Buyer Authentication. The Buyer
Authentication Setup page appears.
3. Enter Registration information (complete all fields for both MasterCard and Visa).
– Select your Acquirer (Acquirer Support) for MasterCard and Visa and click Activate to
activate the Acquirer you selected.
– Enter your Business Name.
– Enter the fully qualified URL (be sure to include http:// or https://) of your business.
– Select your Country Code from the drop-down menu.
4. Click Submit. A gray notification box appears towards the top of the page confirming the
changes. If there are any errors, a yellow box appears towards the top of the page stating
the problem.
5. On the main PayPal Manager page click the Download link.
6. Read chapters 5 through 7 and Appendix D of this document
7. Download the Payflow SDK (Software Developer’s Kit) appropriate for your software
environment.
8. Download Payflow Pro Developer’s Guide (PDF format document). Read as much of
Payflow Pro Developer’s Guide as you need.
9. Configure the Payflow SDK as described in the developer’s guide.