Developer's Guide
Table Of Contents
- Payflow Pro Developer’s Guide
- Contents
- Preface
- Introduction
- Installing and Configuring the Payflow APIs
- Performing Credit Card Transactions
- About Credit Card Processing
- Contents of a Transaction Request
- How To Format a Transaction
- Parameters Used in Credit Card Transactions
- Values Required by All Transaction Types
- Submitting Sale Transactions
- Submitting Authorisation/Delayed Capture Transactions
- When To Use Authorisation/Delayed Capture Transactions
- Required Authorisation Transaction Parameters
- Typical Authorisation Transaction Parameter String
- Required Delayed Capture Transaction Parameters
- Delayed Capture Transaction: Capturing Transactions for Lower Amounts
- Delayed Capture Transaction: Capturing Transactions for Higher Amounts
- Delayed Capture Transaction: Error Handling and Retransmittal
- Submitting Voice Authorisation Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Card Security Code Validation
- Responses to Credit Card Transaction Requests
- Testing Payflow Pro Credit Card Transactions
- Activating Your Payflow Pro Account
- Processor Details
- Verbosity: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- XMLPay
- Index
Payflow Pro Developer’s Guide 53
Testing Payflow Pro Credit Card Transactions
Result Code Responses
5
Alternative Methods for Generating Specific Result Codes
Table 5.4 shows another method for obtaining result codes. 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 code plus 1000 even
though this table suggests another means of obtaining the result code.
TABLE 5.3 Result codes supporting the amount control
Processing Platform Result Codes Available for Testing
American Express APAC 0, 12, 13, 104, 1000
Citibank Singapore 0, 4, 5,12,13,23,24,104, 2000
First Data International 0, 3, 4, 5, 12, 13, 23, 24, 26, 30, 50, 99, 100, 102, 104,
1000
T
ABLE 5.4 Obtaining result code
Result Definition How to test using Payflow Pro
0 Approved Use an AMOUNT of $1000 or less
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
19 Original transaction ID
not found
Submit a Delayed Capture transaction with an invalid ORIGID
23 Invalid account number Submit an invalid account number, for example, 000000000000000
24 Invalid expiration date Submit an invalid expiration date, for example, 0298
25 Transaction type not
mapped to this host
(Processor)
Submit a transaction for a card or tender you are not currently set up to
accept, for example, a Diners card if you aren’t set up to accept Diners
29 Invalid XML document Pass a bad XML document (XMLPay users only)
101 Time-out value too small Set timeout value to 1