Troubleshooting
“400 Bad Request”
The JSON standard mandates that string characters are encoded using UTF-8. Such characters may result in multiple bytes per character. Any JSON request that is not well-formed according to the JSON standard will not be processed successfully.
To address this issue:
- Ensure characters submitted in your requests to us are encoded in UTF-8.
- Our JSON library handles such encoding automatically.
“401 Authorization Required”
The following is an example response that may be returned:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html>
To address this issue:
- Ensure you have submitted your Web Services username and password correctly in the request.
- Restrictions can be put in place to ensure that only Web Services requests originating from your IP (or range of IPs) are accepted by Trust Payments. This error is returned when we receive a request originating from an IP outside of this range, which is first defined when creating the “Webservices” user in MyST.
- It is possible to modify the range of IPs that we accept by modifying the “Webservices” user in MyST.
“10205 Malformed JSON”
The following is an example response that may be returned:
{"requestreference":"W23-rd55dned","version":"1.00","response":[{"errorcode":"10205","requesttypedescription":"ERROR","transactionstartedtimestamp":"2016-11-10 12:18:50","errormessage":"Malformed JSON","errordata":["invalid json"]}],"secrand":"Z0Xk"}
To address this issue:
- Ensure that all comma separators are correct (No comma should be inserted after the last field value in the request string).
- Ensure any opening bracket has an associated closing bracket.
- If you are developing your own library, this kind of error can occur when the request header’s Content-Length is calculated before encoding the request. The Content-Length must contain the number of bytes in the actual payload of the request and therefore must be calculated after any character encoding is performed.
“60018 Invalid requesttype”
The following is an example response that may be returned:
{"requestreference":"W72-g9wv2j5c","version":"1.00","response":[{"errorcode":"60018","requesttypedescription":"ERROR","transactionstartedtimestamp":"2017-04-19 12:56:11","errormessage":"Invalid requesttype"}],"secrand":"qTFlr"}
The above error can be caused when malformed JSON is submitted in the request.
To address this issue:
- Ensure that all comma separators are correct (No comma should be inserted after the last field value in the request string).
- Ensure any opening bracket has an associated closing bracket.
- Ensure that all fields submitted by the API are defined in our specification.
“60019 No searchable filter specified”
The following is an example response that may be returned:
{"requestreference":"W72-g9wv2j5c","version":"1.00","response":[{"errorcode":"60019","requesttypedescription":"TRANSACTIONUPDATE","transactionstartedtimestamp":"2016-11-29 12:06:42","errormessage":"No searchable filter specified"}],"secrand":"qTFlr"}
To address this issue:
First of all, ensure that you have specified a supported filter in the request, and that this has been spelt correctly. If the error still occurs, this could be because the formatting of the filter fields is incorrect. Please ensure the filter tag has the same structure as in the examples provided in the transaction query or transaction update documentation, depending on the type of request you are attempting to submit.
Transaction update errors
If you are having problems when performing updates, please check the following:
- Ensure you are only updating valid request types (refer to the “Requirements” section on the Transaction Updates page).
- Ensure you specify both a site reference and transaction reference in the filters. This informs us of which transaction needs to be updated.
- Ensure you only attempt to update the fields listed above and that the values submitted are valid (refer to the Transaction Updates page for further details).
- You cannot update transactions after Settlement has begun. Ensure the settle status is not “3”, “10” or “100” before performing an update.
| Error code | Error message | Next steps |
| 0 | Ok | The update was processed successfully. |
| 30000 | Invalid field | The errordata field returned in the response should contain the name of the field that was submitted with invalid data. Please ensure the data meets our specification. |
| 60011 | Wrong number of transactions | Only one transaction can be updated in a TRANSACTIONUPDATE request. Please ensure the filters specify only one valid transaction. |
| 60013 | No valid updates specified | You are only able to update the fields listed on the Transaction Updates page. If you attempt to update any other fields, you will be returned this message in the response. |
| 60014 | Transaction reference not found | Please ensure you have submitted the correct transaction reference in the request. |
| 60016 | settlebaseamount too large | When updating the transaction settlebaseamount, the value can never be greater than the amount originally authorised by your bank. Therefore, please ensure this value is equal to or lower than the authorised amount. |
| 60017 | Transaction not updatable | Transactions can only be updated when in settlestatus “0”, “1” or “2”. Click here to learn more about settlement. |
| 60018 | Invalid requesttype | You can only update requests with the request types listed on the Transaction Updates page. |
| 60019 | No searchable filter specified | Please ensure you have submitted valid filters in the request, so we can correctly identify the transaction you would like to update. |
We’re here to help
If you require further assistance, please get in touch with our Support Team.