SDK White Label Overview

Welcome to the SDK White Label documentation. The SDK White Label is Getnet's white-label solution for Android POS terminals. It lets your application run complete card-present payment flows directly on the terminal, without handling the hardware or the payment services yourself. In code, its entry point is the ApoloSdk class.

What is the SDK White Label

The SDK White Label is an Android library that you embed in your own application. Once integrated, your app can start sales, refunds, and receipt printing through a single entry point, ApoloSdk.Builder.

The SDK handles three areas that would otherwise demand significant effort from you:

  • Terminal operation — the SDK drives the terminal hardware needed for a transaction.
  • Payment-service communication — authentication, authorization, capture, and availability checks run inside the SDK.
  • Ready-made flows — screens, transitions, error states, and cardholder messages ship as a package, with defined extension points.
The SDK does not keep a transaction history, and it does not replace your backend for reconciliation, fiscal issuance, or reporting. Those remain your application's responsibility.

Because it depends on hardware and services that exist only on POS devices, the SDK does not run on emulators, virtual machines, or ordinary Android phones.

How it works

The SDK follows a Single-Activity model: every screen of the transaction flow lives inside a dedicated Activity hosted by the SDK. Your application triggers an operation, the SDK takes over the interface, and control returns to your app when the operation ends.

A typical integration moves through four moments:

  1. Initialization — you configure the SDK once, during your application's startup.
  2. Warm-up — the SDK loads the terminal configuration and authenticates with the payment services, reporting progress back to your app.
  3. Operation — after warm-up succeeds, your app starts a sale, refund, or print.
  4. Result — when the flow ends, the SDK returns a typed outcome through a callback.

Between the amount entry and the final result, the SDK runs the whole transaction internally.

A white-label experience

Each operation ships with the SDK's own screens, which guide the cardholder through the journey on the terminal. You can keep the ready-made screens or make them your own:

  • Apply your brand colors through theme customization.
  • Insert screens between existing steps of the flow.
  • Replace the appearance of a screen while keeping its behavior.
  • Customize the receipts printed for the establishment and the customer.

This lets the experience range from the SDK's default screens to a flow fully tailored to your application.

Where it fits

The SDK White Label runs on the terminal, on the client side. It depends on Getnet's terminal management service for two things: the configuration it loads during warm-up, and the credentials it authenticates with. Payments are then processed card-present through SEP.

The SDK White Label targets Android POS terminals only. It is designed for partners who already have a relationship with Getnet and want to accept payments through their own application.

Next steps

To start your integration, follow the path below:

  • Prerequisites — confirm the environment, credentials, and terminal services you need before integrating.
  • Add the SDK to your project — set up the dependency, permissions, and required terminal services.
  • Quick Start — initialize the SDK and run your first sale.
  • Process a sale — run each payment method and mode, then explore refunds, printing, and customization.

On this page

SDK White Label Overview