Integrated POS Overview

Welcome to the Integrated POS documentation. This integration model allows your commercial automation system to communicate directly with a Getnet payment terminal so that payment operations can be initiated, controlled, and completed programmatically.

What is an Integrated POS

An Integrated POS is a payment terminal that communicates directly with a commercial automation system, allowing payment operations to be initiated, controlled, and completed programmatically, without manual interaction on the terminal.

Unlike a standalone POS, where the operator manually enters values and navigates screens, an Integrated POS receives structured commands from the automation system and returns structured responses through a predefined digital protocol.

If an optional parameter is not sent by the automation system, the terminal automatically displays the corresponding screen, allowing a fully or partially integrated flow depending on the system's requirements.

High-Level Architecture

In an Integrated POS architecture, the commercial automation system is responsible for:

  • Integrating the Integrated POS Library
  • Establishing communication with the POS terminal
  • Sending commands that initiate payment-related operations
  • Handling structured responses returned by the terminal
On the POS device, a Connector App receives the commands and internally launches the Payment App. This transition happens seamlessly, without operator interaction.

Once the Payment App completes the requested operation, the result is returned to the automation system, closing the communication loop and keeping both systems synchronized.

Connection Modes

The Integrated POS supports two connection modes. Both expose the same Connector instance and the same device operations — only the transport to the terminal differs.

  • SDK (USB / HTTP) — the automation system connects to a terminal on the same local network or cable. Use CreateHttp for Wi-Fi or Ethernet and CreateUsb for a serial link.
  • Cloud2Cloud — the automation system reaches a remote terminal through the Getnet cloud. Use CreateCloud. No local network access to the terminal is required.
Each mode produces a Connector instance that exposes the same set of device operation functions. From connector creation onward, the commands and business rules are identical across both modes.

Communication Lifecycle

Every interaction with an Integrated POS must follow this sequence:

  1. Create a Connector — Establish a communication channel using one of the supported creation methods.
  2. Validate connectivity with the Terminal — Execute Polling to confirm that the POS is connected and ready to receive commands.
  3. Execute Business Operations — Invoke device operations such as Sale, Refund, GetReports, or PreAuth.
  4. Finish Resources — Call Close to free all resources allocated by the integration library.

Failing to respect this lifecycle may result in rejected operations or undefined behavior.

Next Steps

To start integrating:

  • Read POS Architecture to understand components and execution flow.
  • Review Connection Models to compare the SDK (USB / HTTP) and Cloud2Cloud connection modes.
  • Follow the Quick Start to run your first Integrated POS payment.

On this page

Integrated POS Overview