Handling errors

If an error has occurred during processing the response will be as follows:

{
"error": "<errortext>", "errorcode": <errorcode>
}

 

For example:

{"error":"Transaction Error:Terminal is offline.","errorcode":2000}

 

The following lists the error texts and associated codes:

  • {“Invalid siteid”, “1001”}
  • {“Invalid token”, “1002”}
  • {“Invalid txndate”, “1003”}
  • {“Invalid terminalserialnumber”, “1004”}
  • {“Invalid type”, “1005”}
  • {“Invalid amount”, “1006”}
  • {“Invalid Refid”, “1007”}
  • {“Duplicate Transaction”, “1008”}
  • {“Invalid Request”, “1009”}
  • {“Invalid topuptoken”, “1010”}
  • {“Duplicate Refid”, “1011”}
  • {“refid must match an existing preauth”, “1012”}
  • {“Unable to find PreAuth”, “1013”}
  • {“Capture amount is greater than PreAuth amount”, “1014”}
  • {“Transaction already Voided”, “1015”}
  • {“Transaction already Captured”, “1016”}
  • {“Unable to find original transaction”, “1017”}
  • {“Refund amount larger than original transaction”, “1018”}
  • {“Total of partial refunds cannot exceed original transaction”, “1019”}
  • {“Cannot Void Refund”, “1020”}
  • {“Error pairing Terminal”, “1100”}
  • {“Error parsing PairTerminalResponse”, “1101”}
  • {“Error mapping pairTerminal”,”1102″}
  • {“IO Error pairTerminal”,”1103″}
  • {“Error parsing pairTerminal null”,”1104″}
  • {“pairTerminal eConduit error”,”1105″}
  • {“Error saving Terminal”,”1106″}
  • {“Transaction Error”,”2000″}
  • {“Terminal is Offline”,”2001″}
  • {“Terminal busy”,”2002″}
  • {“Response not received”,”2003″}

In the case of error 2000 additional error information will be provided in the text.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request