Developer's Guide

Website Payments Pro Developer’s Guide 75
Responses to Transaction Requests
RESULT Codes and RESPMSG Values
8
4 Invalid amount format. Use the format: “#####.##” Do not include currency symbols
or commas.
5 Invalid merchant information. Processor does not recognise 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, expiry 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 authorisation. Contact your merchant bank to obtain an authorisation and submit
a manual Voice Authorisation transaction.
14 Invalid Client Certification ID. Check the HTTP header. If the tag, X-VPS-VIT-
CLIENT-CERTIFICATION-ID, is missing, RESULT code 14 is returned.
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
22 Invalid ABA number
23 Invalid account number. Check credit card number and re-submit.
24 Invalid expiry date. Check and re-submit.
25 Invalid Host Mapping. You are trying to process a tender type such as Discover Card,
but you are not set up with your merchant bank to accept this card type.
26 Invalid vendor account
27 Insufficient partner permissions
28 Insufficient user permissions
29 Invalid XML document. This could be caused by an unrecognised XML tag or a bad
XML format that cannot be parsed by the system.
30 Duplicate transaction
T
ABLE 8.5 Payflow transaction RESULT values and RESPMSG text (Continued)
RESULT RESPMSG and Explanation