Skip to main content
The device list shows which installations are registered to the selected shop and when Tapp last heard from each one. It separates POS-enabled devices from other devices in the web Admin App.

​
Who can do this?

Owners and Managers can use the parts described here. Store-wide management of other devices remains limited to Owners and Managers; self-service for the current device and read-only list access have different scopes. API authorization is authoritative.

​
Where

In the Management Admin App, open Devices from the Admin section. In the Management Native App, Owners and Managers can open store devices from Settings.

​
Steps

  1. Confirm the intended shop before opening the device list.
  2. Review the POS devices and Other devices sections in web, or the native device list.
  3. Use device name and platform to identify the installation.
  4. Read Last seen as the time of the most recent recorded heartbeat, not a guarantee that the app is currently open.
  5. Refresh before acting on a stale row, especially when preparing remote payment.

​
Platform notes

The native app sends a heartbeat when it becomes active. The API returns device name, platform, POS flag, Tap to Pay flag, terminal-session state, and timestamps; the Admin list currently presents name, platform, last seen, and POS grouping. Owners and Managers can manage rows from supported UI.

​
Market notes

The device model is shared by GB and DE. Date wording follows interface locale. Last-seen age is technical status only and does not establish payment readiness, fiscal readiness, or staff attendance.

​
Troubleshooting

If the list is empty, verify the shop and register the mobile installation. If last seen is old, bring the correct app to the foreground while online. Duplicate-looking rows can represent different installations or a reinstalled app; compare platform and ownership before removing anything.