Pay At Table Fault Responses
Supported Fault Response Codes to PXP
The below table shows the FaultResponseCode values that are supported in the response back to PXP
| ResponseCode | FaultResponseCode | FaultResponseMessage | Merchant Use Case |
|---|---|---|---|
| Success | 0 | Successful Response | |
| Error | 1 | User {} invalid | Used when the Merchant System cannot validate the User ID during the Login stage |
| Error | 2 | Check/Table {} not found | Used when the Merchant System cannot locate the Check or Table number during the Check Info stage |
| Error | 3 | Unable to close check {0} | Used when the Merchant System is unable to successfully close the check in the Post Payment stage |
| Error | 4 | User {} invalid | Used when the Merchant System cannot validate the User ID during the Disconnect Message |
| Error | 5 | Itemised check {} not found | Used when the Merchant System cannot locate the Check or Table number during the Disconnect stage |
| Error | 7 | General Error | General Error is to only be used as a generic error when no other FaultResponseCode values match the use case |
| Error | 8 | Device not registered | Used when the Merchant System does not recognise the SerialNumber or PTid within the Login stage |
| Error | 12 | Check {} already paid | Used when the Merchant System cannot close a check during the Post Payment stage as it has already been closed. |
| Error | 16 | Check {} is already open on device {} | Used when the Merchant System has returned the Check Info Response to a device for a check without having received the corresponding Disconnect to unlock the Check. This prevents the Check being collected on multiple devices at the same time |
Updated almost 6 years ago