Getnet DocsGetnet Docs

Architecture & Flow

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

The App2App integration model enables seamless and secure local communication between a third-party automation application and the Getnet Payment App installed on the same Android terminal.

Communication mechanism: Android Intents

Data exchange does not require a persistent connection. Instead, it uses Android Intents and Deeplinks to trigger commands and receive responses.

  • An Intent is a messaging object used to request an action from another app component.

  • Deeplink is a specific URI (e.g., getnet://payment/v1/payment) that acts as the “address” for a specific feature within the Getnet App.

Supported commands

This table summarizes the operations your application can request from the Getnet terminal:

OperationDeeplink URIDescription
Paymentgetnet://payment/v1/paymentInitiates a payment transaction (Card or QR Code).
Pre-authorizationgetnet://payment/v1/pre-authTemporarily holds funds on a customer’s credit card.
Refundgetnet://payment/v1/refundReverses a previously approved transaction.
Commerce Datagetnet://payment/v1/commerce-dataRetrieves merchant registration data.
Get Infogetnet://payment/v1/get-infoRetrieves technical terminal data (S/N, OS, version).
Pollinggetnet://payment/v1/pollingVerifies if the payment app is ready to handle requests.
Reprintgetnet://payment/v1/last-transactionReturns or reprints the last receipt.
Reportsgetnet://payment/v1/reportsRetrieves transaction history (detailed list or summary of totals).
Shiftgetnet://payment/v1/shiftManages shifts (set up, change, or retrieve shift information).
Cancel Operationgetnet://payment/v1/cancel-operationCancels a deeplink operation currently in progress.
Check Statusgetnet://payment/v1/transaction-check-statusSearches for the status of a specific previous transaction.

The transaction lifecycle

The process follows three main stages, ensuring UI control returns to your app after the operation:

  1. Initiation (Request): Your app triggers an Intent with a specific deeplink URI and request parameters passed as extras.

  2. Processing (UI Flow): The Getnet Payment App takes control of the UI to interact with the user or process the transaction.

  3. Return (Callback): Upon completion, the Getnet Payment App returns response parameters as Intent extras via the onActivityResult method.

Next steps