📄️ Introduction
Add a dependency, make four calls, and your app can take a card payment. The Halo UI SDK owns everything in between: amount entry, the card-reading screens, the PIN pad, the result screen and the receipt. It is built with Jetpack Compose and designed to be driven from a Flutter or React Native host just as easily as from Kotlin.
📄️ Installation
Follow these steps to integrate the Halo UI SDK into your Android project.
📄️ Configuration
HDConfig
📄️ Usage
The Halo UI SDK uses Kotlin Coroutines to provide a clean, asynchronous way to launch the UI and wait for a result.
📄️ Inbound Payments
Besides charges you start with HaloSdkUi.launch, the SDK can be opened by a payment that arrives from outside your app — another app handing over a transaction, a halo:// link, an App Link, or a scanned QR code.
📄️ Push to Terminal
A fourth door, alongside the three in Inbound Payments: a payment sent to a named device. A merchant system calls the kernel's POST /consumer/push naming one of its registered devices, and that device opens on the tap screen with the amount already on it — no QR to show, nothing for the cardholder to scan.
📄️ Telemetry
The SDK can report what it did and what went wrong into your own Firebase project. It is off by default, and it never carries a payment's details.