Getnet DocsGetnet Docs

Response and Error Codes

This reference describes the response and error codes used by Integrated POS operations. All operations return at least a numeric Code and a Message.

What are response and error codes

Every Integrated POS operation returns a response with a numeric Code (Int) and Message (String).

All values listed below are returned in the same Code field. The categorization into “Response Codes” and “Error Codes” is for documentation clarity and logical grouping only.

Response structure

All operations return a structured response containing at minimum:

FieldTypeDescription
CodeStringResponse code (see table below).
MessageStringHuman-readable result.

A response code of 0 indicates success.

Common response codes

CodeDescription
0Operation executed successfully
1Operation denied
2Operation canceled by user
3Error found during operation processing
4Unknown error – check message details
5POS Integrated still on WAITING_CONFIRMATION status. Send a Polling command to initiate.
6Cancel operation executed successfully

Codes 2 and 6 both relate to cancellation but mean different things. 2 (Operation canceled by user) is returned by a command — Sale, Refund, or Pre-authorization — that was aborted. 6 (Cancel operation executed successfully) is returned by the Cancel command itself. Both apply to the SDK (USB / HTTP) and Cloud2Cloud modes.

Code 5 signals that the terminal must re-establish its connection (for example after a reboot or a dropped link). Re-run Polling on the same Connector, resend the setup parameters, then retry the command. See Polling and Reconnection.

When Code is 3 for Sale, Refund, Pre-authorization, or Shift, the Message field is a JSON-encoded string describing the failed validations. See Validation Errors.

Error codes for Integrated POS mode

These codes typically appear in activation, reconnection, or connection-loss scenarios.

The table below lists all error codes defined in the manual.

CodeDescription
1-500The terminal wasn’t able to initialize proper dependencies for open serial port.
1-501Connectivity problem on trying to setup Wi-Fi connection. Check if Wi-Fi is enabled in terminal.
1-502Error on try open the terminal serial port.
1-503The user requested to exit Integrated POS Mode.
A-503The Wi-Fi or USB connection is unexpectedly finished while the application is listening to commands.
A-504The user is trying to quit Integrated POS Mode, but the application couldn’t close communication.
A-505An interface disconnection was detected and the Integrated POS Mode was disconnected.
G-XXXXErrors related to the Cloud Integration Provider, such as G-Services.
S-100There was an internal error in POS or an interface disconnection and the communication was interrupted.

For connection-related codes (e.g. A-503, A-504, A-505, S-100), follow the reconnection flow described in the Core Concepts. Do not assume the Connector is still valid.

Transaction status codes

Returned in the Status field of a CheckStatus response. These describe the state of a past transaction, not the outcome of the CheckStatus command itself — that is in Code.

Status codeStatus nameDescription
0APPROVEDTransaction captured. Used for standard card sales and QR Code with card.
1AUTHORIZEDTransaction authorized (pre-authorization or QR PCT).
2REFUNDEDTransaction refunded (D+1).
3CANCELEDTransaction canceled (D+0).
4REVERSEDTransaction reversed (undone).
5NOT_FOUNDNo transaction found for the given CallerId.
6UNKNOWNUnmapped status.

QR Code payment methods behave differently. QR PCT (Point of Capture) transactions always return AUTHORIZED and never APPROVED. QR Code with card follows the same behavior as a standard card sale.

Error handling guidelines

  • Always check the response Code before proceeding (e.g. 0 = success).
  • Do not retry operations blindly; revalidate terminal state with Polling after errors.
  • For code 5, send a Polling command before continuing.
  • For connection-related errors, follow the reconnection instructions in this documentation.