Error Code Reference

More documents

Recommendations

Info

Error Code Reference -1310 Socket has not been setup correctly or there are not enough resources available -1311 Internal error indicating an invalid socket request has been made -1312 Error occurred during socket read request -1313 Internal error (not returned to applications) -1314 Operation attempted on a socket no longer open -1315 Internal error indicating that a socket operation cannot be completed immediately -1316 Request made on a connection where other side has closed the connection -1317 Request was not completed before the maximum time allowed -1318 A socket setup as a server did not receive a valid connection -1319 Occurs when waiting for a read or write to occur on a socket and the other side of the connection is closed -1351 Internal error caused by fatal ssl error -1352 Internal error caused by fatal ssl error, or ssl allocation error -1353 Internal error caused by a random number seeding failure -1354 Internal error caused by illegal cipher combination requested -1355 Invalid public key certificate was specified -1356 Invalid private key was specified -1357 Unable to connect to remote listener. Can be caused by attempting to connect to a non-ssl listener. -1358 Unable to accept connection from the client. Can be caused by the client attempting a non-ssl connection or by the client rejecting the supplied certificate -1359 Unable to send data -1360 Unable to read data -1361 Unable to read data -1362 Unable to verify supplied certificate -1363 Initialization failed for ssl request -1364 CN certificate value in the server certificate is not the expected value -1365 OU certificate value in the server certificate is not the expected value -1366 O certificate value in the server certificate is not the expected value -1367 L certificate value in the server certificate is not the expected value -1368 ST certificate value in the server certificate is not the expected value -1369 C certificate value in the server certificate is not the expected value -1400 Series Errors Error codes related to pipe and transaction communications. -1400 Generic pipe related error -1401 Attempt to read or write with an improperly initialized pipe object -1402 Failure during an attempt to read -1403 Failure during an attempt to write -1404 The read request aborted when sending output to a file -1405 An unknown response code sent back from file transfer -1406 Operation did not complete before the timeout expired -1407 Transaction returned with a NO_ERROR response but there was a header mismatch TouchNet Confidential
Error Code Reference -1408 Pipe closed before the operation completed -1409 Request made to a pipe that does not have a peer connected to it -1410 Connection request made to a pipe that already has a peer connected to it -1411 Request made for a pipe where no more instances are available -1412 The pipe handle is not valid -1413 Named pipe creation failed -1600 Series Errors Codes beginning with –1600 in the authorization or batch settlement reports indicate that problems occurred at your credit card processor. The information here is based on specifications provided by the credit card processor, and is subject to change by the processor. -16xx Credit Card processor specific -1700 Series Errors Codes beginning with -1700 indicate that Payment Gateway has signaled an error. -1701 Occurs when a required value was not found in the configuration file. This error commonly occurs if your current license does not allow an attempted operation, or if you have added more merchant accounts than your license allows. It may also occur if your Payment Gateway configuration is incorrect or incomplete. -1702 Required card data was not present or failed verification check. This error may indicate an invalid card number or type submitted by the payer. This error code indicates that the request could not be filled as submitted.* -1703 Generic bad authorization error and may occur in any case that might cause a card issuer to deny a payment, such as insufficient funds.* -1704 Occurs on a batch settlement in response to modem or other connection problems; if merchant or modem configuration is incorrect; or if incorrect characters appear in return data from the credit card processor. This error code indicates that the specific batch settlement request could not be filled as submitted. -1705 Occurs when a “start” signal was not sent by credit card processor. This error can indicate a modem or other connection error. -1706 Configuration file is not found -1707 A response is not received before the timeout -1708 Occurs when the maximum number of retries was exceeded. This error may have occurred after part or all of the batch was settled by the credit card processor, but before Payment Gateway received a response from the settlement. -1709 Occurs when a response character was not received before the timeout. This error may have occurred after part or all of the batch was settled by the credit card processor, but before Payment Gateway received a response from the settlement. -1710 Occurs when the request made for the transaction is not a valid request; the operation you have attempted on the transaction is not allowed. If using the Payment Gateway API, verify that the data passed to Payment Gateway is valid. TouchNet Confidential
Page 1: TM Error Code Reference Error Codes
Page 5 and 6: Error Code Reference -1730 Occurs w
Page 7: Error Code Reference -2302 There wa

Error Code Reference

Create successful ePaper yourself

Delete template?

Save as template?