Developer's Guide
Table Of Contents
- Payflow Pro Developer’s Guide
- Contents
- Introduction
- Downloading, Installing, and Activating
- Simple Payflow Transaction
- Credit Card Transactions
- Credit Card Features
- About Credit Card Processing
- Parameters Used in Credit Card Transactions
- Submitting Sale Transactions
- Submitting Authorization/Delayed Capture Transactions
- When To Use Authorization/Delayed Capture Transactions
- Required Authorization Transaction Parameters
- Typical Authorization 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 Authorization Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Submitting Purchasing Card Transactions
- Using Address Verification Service
- Processing Platforms Supporting Address Verification Service
- Example Address Verification Service Request Parameter List
- Example Address Verification Service Response
- Card Security Code Validation
- Credit Card Testing
- Responses to Transaction Requests
- Processors Requiring Additional Transaction Parameters
- American Express
- First Data Merchant Services (FDMS) Nashville
- First Data Merchant Services (FDMS) South
- First Data Merchant Services (FDMS) North
- Merchant e-Solutions
- Elavon (Formerly Nova)
- Paymentech
- TSYS Acquiring Solutions
- Performing TeleCheck Electronic Check Transactions
- Submitting Purchasing Card Level 2 and Level 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions - Phoenix Processor
- American Express Phoenix Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing
- First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
- Global Payments - Central Purchasing Card Transaction Processing
- Global Payments - East Purchasing Card Transaction Processing
- Merchant e-Solutions Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- VERBOSITY: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- ISO Country Codes
- Codes Used by FDMS South Only
- XMLPay
- Index
Payflow Pro Developer’s Guide 57
Responses to Transaction Requests
RESULT Values and RESPMSG Text
6
TABLE 6.2 Payflow transaction RESULT values and RESPMSG text
RESULT RESPMSG and Explanation
0 Approved.
1 User authentication failed. Error is caused by one or more of the following:
z Login information is incorrect. Verify that USER, VENDOR, PARTNER, and
PASSWORD have been entered correctly. VENDOR is your merchant ID and
USER is the same as VENDOR unless you created a Payflow Pro user. All fields
are case sensitive.
z Invalid Processor information entered. Contact merchant bank to verify.
z "Allowed IP Address" security feature implemented. The transaction is coming
from an unknown IP address. See PayPal Manager online help for details on how to
use Manager to update the allowed IP addresses.
z You are using a test (not active) account to submit a transaction to the live PayPal
servers. Change the host address from the test server URL to the live server URL.
2 Invalid tender type. Your merchant bank account does not support the following
credit card type that was submitted.
3 Invalid transaction type. Transaction type is not appropriate for this transaction. For
example, you cannot credit an authorization-only transaction.
4 Invalid amount format. Use the format: “#####.##” Do not include currency
symbols or commas.
5 Invalid merchant information. Processor does not recognize your merchant account
information. Contact your bank account acquirer to resolve this problem.
6 Invalid or unsupported currency code
7 Field format error. Invalid information entered. See RESPMSG.
8 Not a transaction server
9 Too many parameters or invalid stream
10 Too many line items
11 Client time-out waiting for response
12 Declined. Check the credit card number, expiration date, and transaction information to
make sure they were entered correctly. If this does not resolve the problem, have the
customer call their card issuing bank to resolve.
13 Referral. Transaction cannot be approved electronically but can be approved with a
verbal authorization. Contact your merchant bank to obtain an authorization and submit
a manual Voice Authorization transaction.
19 Original transaction ID not found. The transaction ID you entered for this
transaction is not valid. See RESPMSG.
20 Cannot find the customer reference number










