Error Response Codes
Overview
The following appendix contains information regarding error response codes and how to handle certain errors.
Note: These error codes only apply to the errorCode response field.
| Code | Description | Comments |
|---|---|---|
| 5900 | Global Error | Generic Error Message for all uncaught exceptions generated by the application. |
| 5901 | Invalid Message Structure | The https request with parameters structure did not conform to our expectations. Example: invalid JSON format, missing request keys, etc. |
| 5902 | Invalid Request Value | There was a value in the http request that did not match our expectations. Example: incorrect value for terminalId, amount etc. |
| 5903 | Unable to Locate Pinpad | We were unable to located a PINpad by the references that was sent in. Example: The PINpad is disconnected, PINpad is disabled, etc. |
| 5904 | Pinpad is Currently Performing Another Transaction | The PINpad is currently performing another transaction and is unable to perform the valid transaction that you had sent us. |
| 5905 | Invalid PostbackUrl | We were unable to perform a https GET request against the provided postBackUrl. |
| 5906 | Pinpad connection has timed out | Likely the result of an intermittent internet connection issue on the merchant/integrator side. |
| 5907 | Pinpad was disconnected during a transaction. | Returned when the server detects that the PINpad has been disconnected while in the middle of a transaction. |
| 5908 | The pinpad is unable to connect to the cloud service | Indicates the PINpad may require replacement. Please contact your support representative for further instructions. |
| 5909 | Gateway Error | Moneris gateway was not available to authenticate this transaction, please try again when Moneris gateway is available. |
| 5911 | Invalid Parameter | This error code applies to all fields. |
| 5912 | Invalid Length | This error code applies to all fields. |
| 5913 | Invalid Format | The parameter structure did not conform to expectations. |
| 5914 | Missing Parameter | This error code applies to all Required fields. |
| 5915 | Duplicate Value | This error code is returned when Idempotency Key in the request matches one of the records in the terminal log but the transaction type or amount are different. |
Error Code ‘5906’ (Only Cloud Integration)
The error code ‘5906’ is generated when the terminal's connection with Moneris' servers was disrupted during a transaction. The error code is generated when the server notes that the connection to the pinpad was dropped due to a lack of application level keepalives.
{
"receipt":{
"apiVersion":"3.0",
"statusCode":"5476",
"status":"Communication error",
"dataId":"example_dataId",
"dataTimestamp":"1969-12-31 23:59:59",
"data":{
"response":[
{
"idempotencyKey":"example_idempotencyKey",
"orderId":"example_orderId",
"statusCode":"5476",
"status":"Communication error",
"cloudTicket":"example_cloudTicket",
"linkId":"example_linkId",
"terminalId":"example_terminalId",
"errorDetails":[
{
"errorCode":"5906",
"issue":"Pinpad connection has timed out"
}
],
"completed":"true"
}
]
}
}
}Error Code ‘5907’ (Only Cloud Integration)
The error code ‘5907’ is generated when the connection logs a network level error (For example EPIPE and ECONNRESET).
{
"receipt":{
"apiVersion":"3.0",
"statusCode":"5476",
"status":"Communication error",
"dataId":"example_dataId",
"dataTimestamp":"1969-12-31 23:59:59",
"data":{
"response":[
{
"idempotencyKey":"example_idempotencyKey",
"orderId":"example_orderId",
"statusCode":"5476",
"status":"Communication error",
"cloudTicket":"example_cloudTicket",
"linkId":"example_linkId",
"terminalId":"example_terminalId",
"errorDetails":[
{
"errorCode":"5907",
"issue":"Pinpad was disconnected during a transaction"
}
],
"completed":"true"
}
]
}
}
}
Error Handling
Communication Error - ‘5906’ and ‘5907’
When these two responses are received, it can either indicate a momentary disconnection due to cellular / Wi-Fi connection drop, an effect of a network outage, the network on the merchant’s server, or the public internet.
In both error code scenarios Moneris suggests that the merchant retry the same transaction again to attempt to retrieve the previous transaction, the terminal buffers the final receipt if the transaction was successfully processed.
If these responses were generated by a network outage, we expect that the merchant will receive a lot of ‘unable to locate pinpad’ responses, because of this, when attempt to retry to transaction, please attempt this at 30 second intervals for up to 5 minutes. If multiple devices are having this issue, proceed with internal network diagnosis in the following order:
- Is the terminal able to connect to Wi-Fi / cellular.
- Is the network disrupted on site?
- Is the location able to connect outbound to the internet?
- Is there network outage between the site and Moneris?
- Reach out to Moneris support to see if there is an incident.
There is an edge case where ‘5906’ ‘5907’ is returned and the terminal provides another kind of negative response or queues up the transaction again on the terminal.
Testing Communication Errors
'5906'
- Perform financial transaction (ex, Purchase/ Independent Refund).
- On the card entry screen - disabled Wi-Fi & 4G connections.
- Then Tap/Insert the card and wait for transaction to get declined at the terminal.
- Moneris Cloud will return an error code 5906.
- Enable Wi-Fi/ cellular connection.
- Resent the original request to Moneris to get the final response.
‘5907’
- Perform financial transaction (ex, Purchase/ Independent Refund).
- On the card entry screen - disabled Wi-Fi & cellular connections for 2 seconds and enable Wi-Fi.
- Then Tap/Insert the card and wait for transaction to get approved/declined at the terminal.
- Moneris Cloud will return an error code 5907.
- Resent the original request to Moneris to get the final response

