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
- Testing Buyer Authentication Transactions Using the Payflow SDK
- Deactivating Fraud Protection Services
- Index
Fraud Protection Services User’s Guide 113
Testing Buyer Authentication Transactions Using the Payflow SDK
Buyer Authentication Testing Procedures
C
Step 2 Validate Authentication Transaction
Validate Authentication Transaction Test Cases
Procedure
Direct the Validate Authentication transaction (TRXTYPE=Z) to the test buyer
authentication server: pilot-buyerauth.verisign.com. Use the PARES value from the ACS
return POST or use the example value that appears on page 114.
IMPORTANT:To avoid format errors, the submitted PARES value should be a single line
with no carriage returns (check especially at the end of the message).
For this call, you must use the pfpro_file.exe script—do not use the pfpro.exe client. Save the
Validate Authentication transaction in a file and then use the pfpro_file script to send the
request to the test Buyer Authentication server:
Example Validate Authentication transaction
"TRXTYPE=Z&PARTNER=PAYPAL&PWD=p12345&VENDOR=SuperMerchant&USER=SuperMerchan
t&PARES[3648]=eJzdWFmTokoW/isdPW9T0c3iUnLDNiKTXQUrWYU3NllEUUBAfv0kWl1l91TPX
ebhTowRBpmHkyfPfr5gbiRlFHF6FFzKaDFXoqry4uhTGn77PAvH4SQKp1MvmEbTnYcf4efF/AVo
UXVj2HD7XjWCzskU0slkGr9sorJKi+OC+kp+pebE9y2RF3F6xNLLIPGO9WLuBWcoqwtq+M2J193
8EJUydyfe6Pf9nHg/93IZVhXWtEvDxe1iY9+qorB3DXniHNyDa/OUe3C+zYmBYx56dbSgSXJE
...
kKpX27a3+0P6ATMpQGWInl2WoZbuHePyp/FUqxyFTXlgV5I/+jMqjde/12HNLjbqW/Qqgfe7Qw9
GjcKgt2OdvtTspJPI2eyuRw0nbr9JKdp6eVP1u3xUyaKN1qYzVksB9vKCe6kqRlV4qfUJP1jvSW
l9OKuSbn5zpK0ouzXl9mNfoARhDv30qIt+8n719Wbh9fb5+Eh++Fj5+K/wWCuWQX"
T
ABLE C.4 Validate Authentication test cases
AUTHENTICATION_STATUS of Validate Authentication Transaction Test Case
Y 1
N 2
A (Visa only) 3
U 7
F 8