Configure a merchant end-to-end: their device groups (device-manager assigns devices into these),
their own LiteCard account, and their theme. Pick a merchant to begin.
🧩 Device Groups
Two independent group trees for this merchant. Redemption (CFD) groups control where a promotion can be redeemed; Signage groups control which displays show it. Each is a Location (a physical place) holding sub-groups — devices are assigned to a sub-group over in Device Manager.
🧾 Redemption groups — CFD devices
📺 Signage groups — signage displays
🔐 LiteCard Credentials
This merchant's own LiteCard account.
⚠️ The API is currently plain HTTP — until TLS is in front, avoid entering production
passwords over an untrusted network. Fine on a trusted LAN / for the shared demo account.
🔗 Consumer Check-in Link
The public, no-login page where this merchant's customers view and claim their rewards —
identified to this merchant by an opaque code. Customers just enter their number once (no login).
—
📌 Add this URL to the Link section of this merchant's template, and ensure it's displayed on the back of the pass — so a customer can tap it from their wallet pass and land on this merchant's check-in page.
🎨 Theme Next sprint
Per-merchant theme selection is deferred. Signage currently themes per-SKU (only
coffee and donut are implemented), and nothing reads a merchant-level theme yet.
Wiring merchant theme into signage/passes — and adding real theme presets — comes in a future sprint.
🖼️ APK Landing Page Image Next sprint
The idle/landing image shown on the redemption terminal. Upload & per-merchant assignment
arrives in a future sprint.
📺 Idle Screen
Control what this merchant's signage shows between scans — featured items, an image carousel, and scheduled happy-hour overrides.
This archives (#): it's removed
from the back-office roster and its operator logins are disabled. Its data is kept —
consumers, promotions and history are retained. (Hard deletion is a separate testing-only action.)