Developer's Guide

Payflow Pro Developer’s Guide 51
Credit Card Testing
RESULT Values Returned Based on Transaction Amount
Alternative Methods for Generating Specific RESULT Values
The table below shows another method for obtaining RESULT values. Non-zero RESULT
values from processors are not returned by the servers, and therefore cannot be simulated
using the amount. In some cases, you may get certain results using the RESULT value plus
1000 even though this table suggests another means of obtaining the RESULT value.
Elavon (Formerly Nova) 0, 12, 13, 104
First Data Merchant Services Nashville 0, 12, 13, 104
First Data Merchant Services North 0, 4, 5, 12, 13, 23, 24,114, 1000
First Data Merchant Services South 0, 12, 13, 104
Global Payments Central 0, 4, 5, 8, 12, 13, 23, 24, 104, 111, 114, 1000
Global Payments East 0, 4, 5, 12, 13, 23, 24, 30, 100, 104, 114, 1000
Paymentech Salem (New Hampshire) 0, 12, 13, 104
Paymentech Tampa 0, 3, 4, 5, 12, 13, 23, 24, 1000
TSYS Acquiring Solutions (Formerly Vital Processing
Services)
0, 4, 12, 13, 23, 104, 114, 1000
T
ABLE 5.4 Obtaining RESULT value
RESULT Definition How to test using Payflow Pro
0 Approved Use an AMOUNT of $1000 or less
For all Processors except Global Payments Central (MAPP) and FDI
Credit (C) and Force (F) transactions will always be approved
regardless of dollar amount or card number
1 User authentication failed Use an invalid PWD
2 Invalid tender Use an invalid TENDER, such as G
3 Invalid transaction type Use an invalid TRXTYPE, such as G
4 Invalid amount Use an invalid AMOUNT, such as –1
5 Invalid merchant
information
Use the AMOUNT 1005 - Applies only to the following processors:
Global Payments East and Central, and American Express
7 Field format error Submit a Delayed Capture transaction with no ORIGID
12 Declined Use the AMOUNT 1012 or an AMOUNT of 2001 or more
13 Referral Use the AMOUNT 1013
T
ABLE 5.3 Result values supporting the amount control
Processing Platform RESULT Values Available for Testing