Getnet DocsGetnet Docs

Customization Model

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 SDK White Label ships with its own screens for the transaction flow and lets you tailor them to your brand. Customization is layered: you choose how far to go, from a color change to replacing a full screen. All customization is optional — without it, the SDK shows its default screens and theme.

The levels

The SDK offers three progressive levels for the screens, plus a separate track for printed receipts.

ApproachWhat it changesWhat it preserves
Theme (Level 1)The color palette of the SDK screens.The screen structure, the flow sequence, and the behavior.
Slots (Level 2)Inserts one of your screens between two SDK screens.The original SDK screens, the sequence, and the behavior.
Overrides (Level 3)Replaces the appearance of an SDK screen.The flow sequence and the screen’s behavior.
ReceiptsReplaces the printed receipt layout.The moment of printing and the transaction data.

Choosing an approach

  • Only the colors need to match your brand — use Theme.
  • You need an extra screen between two steps, without changing the logic — use Slots.
  • You need a screen to look different while keeping its behavior — use Overrides.
  • You need the printed receipts to reflect your brand — use Receipts.

When customization applies

The theme is set on the Builder. Slots and overrides are grouped in a navigation configuration that you apply either once, at initialization, or dynamically at runtime — the second option fits products that change the experience per session, user profile, or business rule.