Error Code Reference
Error Code Reference
Error Code Reference
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Error</strong> <strong>Code</strong> <strong>Reference</strong><br />
-1711 Occurs when there is a bad batch write. The batch was processed, but the batch file<br />
could not be updated and may be corrupted.<br />
-1712 Occurs when there is a bad read from the settlement batch file. Typically, this indicates<br />
that the settlement data expected by the credit card processor does not match the<br />
data sent with the batch settlement<br />
-1713 Occurs when the ETX was not received<br />
-1714 Occurs when modem processing has failed. This error may have occurred after part or<br />
all of the batch was settled by the credit card processor, but before Payment Gateway<br />
received a response from the settlement.<br />
-1715 Occurs when the modem is unavailable<br />
-1716 Occurs when a bad LRC accuracy check was received. Each request and response<br />
includes a single character that verifies whether the response corresponds to the<br />
request. This error indicates that the request and response characters did not match.<br />
This error may have occurred after part or all of the batch was settled by the credit card<br />
processor, but before Payment Gateway received a response from the settlement.<br />
-1717 Occurs when the modem dial failed; either no dial tone was found, or another modem,<br />
phone line, or other connection error has prevented the connection to the credit card<br />
processor. The error may also indicate incorrect modem configuration.<br />
-1718 Occurs when a modem write failed.<br />
-1719 Occurs when a modem read failed.<br />
-1720 Occurs when an invalid response is received. This may be caused by a modem,<br />
phone line, or other connectivity problem occurring while receiving a response. Other<br />
conditions that cause this error are incorrect merchant or modem configuration or<br />
unexpected data received from the credit card processor.<br />
-1721 Occurs when the batch settlement failed because a record was flagged as invalid by<br />
the credit card processor.<br />
-1722 Occurs when a duplicate batch was received<br />
-1723 Occurs when an error occurred in receiving the batch. The error may indicate that the<br />
host was busy. It may also indicate incorrect merchant configuration or credit card<br />
processor phone number information.<br />
-1724 Occurs when address verification failed. No correction is required.*<br />
-1725 Occurs when the card is expired. No correction is required.*<br />
-1726 Occurs when the batch was out of balance. This means that the payment amounts<br />
expected by the credit card processor did not match the amount total of the batch.<br />
-1727 Occurs when an invalid amount was specified. This error may indicate that you<br />
attempted to reverse or credit an invalid amount, or attempted an authorization for<br />
zero or fewer dollars.*<br />
-1728 Occurs when reversals are not allowed for this transaction. The error occurs when you<br />
try to process a credit on a payment that has not yet been settled, with a credit card<br />
processor that does not allow reversals. If needed, you may remove the transaction<br />
from the pending batch, then process a single authorization for the correct amount.*<br />
-1729 Occurs when the operation has been attempted on a previously voided transaction.<br />
This error indicates that no further activity is permitted for the transaction you selected<br />
in the Operations Center.*<br />
TouchNet Confidential