A payment terminal can be powered on and still be unable to take a payment. The app, parameters, keys, and terminal health all have to be right before the first transaction, and none of them is visible from the counter.
A terminal management system (TMS) gives your team a control plane for payment and point-of-sale (POS) fleets. We scope how changes are staged, who can make them, and what the fleet reports back.
What we scope
Configuration and app deployment happen remotely, with key and parameter management written against your acquirer’s rules. Health, heartbeat, and last-seen give your operations team something to act on before a shop calls to say the terminal is dead. Rollouts are staged—pilot shop first, then the chain—so a bad profile costs one site instead of all of them. Roles decide who can change what, which matters more the moment the fleet outgrows one administrator.
Your acquirer host remains the acquirer host. Terminal management is how your team changes apps, parameters, and keys across the fleet without a truck roll for every device. Which system owns the terminal, the parameters, and the reporting feed is named during systems integration.
Sits on: Payment and point-of-sale handhelds
Feeds: Fleet insights
Beside: mobile device management (MDM) when the operating system must also be locked
Turnkey stacks name the hardware, software, and services included, with responsibilities agreed per project: Retail and payments · Hardware and software
Used in: Field operations · Logistics and warehousing
FAQ
Is this a transport management system?
No. On this site, a terminal management system (TMS) is the control plane for payment terminals: apps, parameters, keys, and terminal health.