Handling errors

  Last updated: 

 

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 that can be returned:

 

Invalid errors

Error code Error Resolution
1001 Invalid siteid This is an input validation error. The siteid you are sending in your POST Body is incorrect. Please check and use the siteid provided by Trust Payments.
1002 Invalid token

This is an input validation error. Please ensure you have input the "token" in lowercase in the format shown below.

The "token" to be sent in the HTTP header of each transaction is a SHA256 hash that is constructed as follows:

siteid:txndate:refid:sitepassword

For example:

123456:2020-03-01:10:20:05:7876547:tv%61w%5

When hashed using SHA256, the following token is produced:

990bc7bb7efee9e383a96f6f929fd00c90f4ec94f4344270c1552e4d5d4d80c5
1003 Invalid txndate

This is an input validation error for the field txndate. Please refer to our field specification to learn about the correct format for txndate, and correct as necessary.

{
“siteid”:”123456”,
“txndate”:” 2020-03-01:12:34:01”,
“terminalserialnumber”:”6789654678”,
“type”:”sale”,
“amount”:”20.00”,
“refid”:”89045432”,
“wait”:”y”
}
1004 Invalid terminalserialnumber Please ensure you have entered the correct serial number for the terminal. The serial number can be found on the back of the terminal on the silver sticker, where it is marked by "S/N".
1005 Invalid type This is an input validation error. Please ensure you are using the correct type for the request submitted. e.g. If you are performing a Sale request, ensure you submit type "sale" in the request.
1006 Invalid amount

This is an input validation error. Please ensure a valid amount has been submitted in the request and that the field has not been omitted.

1007 Invalid Refid Please ensure the refid submitted by your system is correct.
1009 Invalid Request

This error code is returned when the request body has been left empty. Please ensure your system is submitting a valid request.

1010 Invalid topuptoken This is an input validation error. Please ensure the topuptoken submitted is formatted correctly and references an existing PreAuth that was processed at an earlier time.

 

Duplicate errors

Error code Error Resolution
1008 Duplicate transaction The refid was already used in another transaction. The refid must be unique. Please update and try again.
1011 Duplicate Refid The refid was already used in another transaction. The refid must be unique. Please update and try again.

 

Transaction errors

Error code Error Resolution
1013 Unable to find PreAuth A refid from an existing PreAuth is required. Please ensure that the refid submitted matches that of an existing PreAuth.
1014 Capture amount is greater than PreAuth amount The capture amount should be lower or equal to that of the associated PreAuth. Please resubmit the request with an amount that fulfils this requirement.
1015 Transaction already Voided It is not possible to void a transaction that has already been voided.
1016 Transaction already Captured It is not possible to capture a transaction that has already been captured.
1017 Unable to find original transaction The original transaction was not found. Please ensure the correct refid of an existing transaction has been submitted.
1018 Refund amount larger than original transaction The refund amount cannot be larger than that associated with the original transaction. Please resubmit the request with an amount that fulfils this requirement.
1019 Total partial refunds cannot exceed original transaction The total amount of all partial refunds combined cannot exceed the amount of the original transaction being refunded.
1020 Cannot Void Refund It is not possible to void a refund.
1022 Another Capture has been started but is not completed Another Capture for the same PreAuth was initiated but has not yet finished. Wait for a terminal response or try again in 60 seconds.
2000 Transaction Error An error has occurred during the transaction. A relevant description message will be returned to help you troubleshoot the error.

 

Pairing errors

Error code Error Resolution
1100 Error pairing Terminal Please ensure you are using the correct Serial Number and Site ID in the body of the request, ensuring your terminal is powered on, connected to the internet, paired with POS and try the request again. If the error persists, please raise with the Trust Payments Support Team.
1101 Error parsing PairTerminalResponse Please ensure you are using the correct Serial Number and Site ID in the body of the request, ensuring your terminal is powered on, connected to the internet, paired with POS and try the request again. If the error persists, please raise with the Trust Payments Support Team.
1102 Error mapping pairTerminal Please ensure you are using the correct Serial Number and Site ID in the body of the request, ensuring your terminal is powered on, connected to the internet, paired with POS and try the request again. If the error persists, please raise with the Trust Payments Support Team.
1103 Error pairTerminal Please ensure you are using the correct Serial Number and Site ID in the body of the request, ensuring your terminal is powered on, connected to the internet, paired with POS and try the request again. If the error persists, please raise with the Trust Payments Support Team.
1104

Error parsing pairTerminal null

If you are receiving this error, please try the following steps to help troubleshoot your device:


Ensure terminal is connected to the internet:
Instructions for Castles VEGA 3000C
Instructions for Castles VEGA 3000M/M2
Instructions for Ingenico Desk 5000
Instructions for Ingenico Move 5000


Ensure your terminal is paired with Trust Payments. This is a requirement for the correct operation of your device. Click here to learn how to perform the pairing process.


This error can also occur when the terminal is attempting to pair with a new ePoS system after previously being paired to a different ePoS system. To resolve this issue:


If you have paired your terminal with Trust Payments and are still receiving this error, please allow an hour for your terminal to sync and try again.


Check your site's firewall settings:

  • The POS (Point of Sale) Gateway requires access to IPs 193.179.205.46 & 193.85.236.92 over Port 11183.
  • The payment device must be able to contact dc.econduitapps.com on Ports 80 and 9001 and HTTPS proxy should be disabled.

If you are still having problems, please contact our Support Team.

1106 Error saving Terminal Please try the request again. If the error persists, please raise with the Trust Payments Support Team.

 

Terminal errors

Error code Error Resolution
2001 Terminal is Offline

Please ensure the terminal is powered on, connected to the internet, paired with POS following the steps found on this article, and try the request again.

If the error persists, please raise with the Trust Payments Support Team.

2002 Terminal busy This indicates the terminal is in use. Please try the request again once the previous transaction has been completed.
2003 Response not received Please ensure the terminal is powered on, connected to the internet and paired with POS following the steps found on this article. If the error persists, please raise with the Trust Payments Support Team.
2004 Terminal is busy with another transaction This indicates the terminal is in use. Please try the request again once the previous transaction has been completed.
2005 No response from terminal, unable to determine transaction approval or decline Please ensure the terminal is powered on, connected to the internet, paired with POS following the steps found on this article, and try the request again. If the error persists, please raise with the Trust Payments Support Team.
2006 Unable to obtain result from terminal, please update transaction manually Please ensure the terminal is powered on, connected to the internet, paired with POS following the steps found on this article, and try the request again. If the error persists, please raise with the Trust Payments Support Team.
Was this article helpful?
0 out of 0 found this helpful