Out of cash, out of receipt paper, offline, or a door opened when it should not be — you want to know before a customer does. A lightweight agent on each terminal publishes health and events over MQTT; ConnectMQ delivers them to your monitoring, cash management and field service systems. Transactions stay on your payment network.
No card required
PUBLISH terminals/atm/atm-ist-0231/cash
{"cassettes":{"c1":312,"c2":95,"c3":1480},"low":["c2"],"paper_pct":18,"ts":"2026-10-22T09:12:40Z"}QoS 1 · TLS 8883 · PUBACK
ATM monitoring often relies on periodic status polls and vendor-specific tools, and POS terminals in stores report almost nothing until a cashier calls the helpdesk. Cash-outs, printer faults and tamper alarms surface late, and a simple configuration change means a site visit or a slow overnight batch.
An agent on the ATM PC or POS terminal publishes device health — dispenser, card reader, printer, network — plus cassette and paper levels. No card or transaction data.
Tamper, safe door and fault events are published with QoS 1 the moment they occur; each terminal’s latest status is retained.
Threshold rules and your monitoring console flag low cash, paper-out or an offline terminal; cash management plans the next replenishment and field service gets a ticket.
Your terminal management system publishes a config change — screen content, parameters, log level — to that terminal’s command topic, and the agent confirms it.
Every terminal connects over TLS with its own username and password, so one compromised device can be shut out without touching the rest of the fleet.
Per-topic ACLs let a terminal publish only its own status and read only its own command topic; monitoring can read everything but send nothing.
Last Will publishes an offline status the moment a terminal drops its connection, instead of waiting for the next poll to time out.
QoS 1 makes sure tamper events reach the broker, and persistent sessions hold a config command until a terminal that was offline reconnects.
terminals/atm/atm-ist-0231/health (retained)
terminals/atm/atm-ist-0231/cash (retained)
terminals/atm/atm-ist-0231/events
terminals/pos/pos-0412-03/health (retained)
terminals/pos/pos-0412-03/cmdFor operational data, yes, when it is set up properly: ConnectMQ encrypts every connection with TLS, gives each terminal its own credentials and limits it with per-topic ACLs. Keep monitoring separate from the payment path — health, levels and events over MQTT, card and transaction data on your payment network. Your own security and compliance review covers the full design.
No. ConnectMQ is meant for operational data such as device health, levels, events and configuration. Card data and transactions stay with your switch, processor and payment network.
An agent running on the ATM PC reads device status from the XFS or XFS4IoT layer or the vendor’s monitoring software, and publishes it over MQTT with any standard client library. On POS terminals, the same agent can run in the terminal app or on the store server.
Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.
