Terminal Management System
Wink-owned TMS that pushes WinkPay-bundled apps and updates to multi-vendor Android payment terminals (Sunmi, PAX, Landi, Elo, …). The same backend distributes the WinkPay SDK AAR feed that Android POS apps depend on.
This page is a placeholder. The TMS portal (live UI for enrolling terminals, managing app deployments, pushing updates) is being built as a sibling project — see winkpay-android-tms. Once it has a public portal URL we'll cross-link from here.
What the TMS does
Android POS terminals can't ship apps from Google Play — most vendors lock or strip GMS. The WinkPay TMS provides a vendor-neutral distribution pipeline that pairs with terminals through one of two bootstrap paths:
- Device Owner (commercial off-the-shelf Android) — the TMS provisions itself as Device Owner via QR or NFC bump at first boot, then installs the WinkAgent which subsequently pulls updates.
- Vendor TMS deploy (locked PTS terminals) — the vendor's existing terminal-management system runs a one-shot install of the WinkAgent; from there WinkAgent handles all subsequent updates.
Once an agent is paired, the TMS pushes:
- Merchant POS APKs (Demo APK, Freshbite APK, custom builds, …)
- WinkPay SDK AAR updates (the same artifacts the SDK reference page documents)
- Config + key-rotation payloads
Where to integrate
If you're building a POS app with the WinkPay SDK, you don't talk to the TMS directly. The TMS picks up your built APK from the release feed; terminals receive it on their normal poll cadence. Builds + signing + release flagging happen out-of-band from your dev workflow.
Status
The TMS backend is in early build (.NET 9 on Azure Container Apps, Postgres for terminal inventory + deployment state). The portal UI lands separately; this page will gain a sign-in link to it then.
Need terminal provisioning today? Contact the Wink team directly. The portal is the eventual self-serve story; for now device enrollment is handled out-of-band.