Skip to main content
A POS-enabled mobile device can run a restricted customer-facing Terminal mode or receive a payment sent from another device. These are related but distinct workflows: terminal mode changes the target device shell, while remote payment dispatch chooses a registered POS target.

​
Who can do this?

Owners and Managers and Staff 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

On the target Management Native App, enable POS mode in Profile settings. Terminal mode then appears on that current-device card. During an eligible POS checkout on another device, use the send-to-another-device option and select a POS target.

​
Steps

  1. Register the target device, mark it for POS, bring its app online, and confirm recent last seen.
  2. For Terminal mode, open its row, read the one-time iOS/Android kiosk guidance, create and confirm the local terminal PIN when first enabling, then confirm entry.
  3. The device enters a persistent terminal shell and reports an active terminal session to the backend.
  4. For remote payment, select the target from POS-enabled devices and send the order. Follow status on both devices and avoid starting a duplicate collection.
  5. Exit Terminal mode only through the protected terminal exit flow.

​
Platform notes

Terminal mode accepts only Tap to Pay and QR Code dispatch methods; the server also enforces this while the device reports an active terminal session. iOS provides written Guided Access guidance because no public settings URL exists; Android can open security settings. Remote dispatch lists only POS-enabled devices and can report busy-device conflicts.

​
Market notes

The device workflow is shared by GB and DE. Available collection methods still depend on market, shop settings, user permissions, supported hardware, and provider readiness. Terminal mode is not a fiscal configuration and does not replace DE compliance setup.

​
Troubleshooting

If there are no connected targets, register another device, enable its POS flag, and refresh. If Terminal mode rejects a method, use Tap to Pay or QR rather than bypassing the restriction. For a busy target, inspect its active dispatch before deciding whether the product’s explicit supersede flow is appropriate.