Cash both ways
The kiosk buys and sells: notes in for crypto out, or crypto in for cash out. The footer states the range plainly — cash ↔︎ BTC, ETH, USDC — so the machine serves both halves of the street.
Cash-level alerts
ATM-0017 at Gara de Nord sits at 8%, flagged cash-low against the 15% refill threshold. The operator sees the flag before a customer meets an empty machine.
Remote lock, with a reason
Any machine locks from the console, from anywhere — and the lock asks why. A reason and a note go to the audit log with the action, and the machine stays dark until someone has looked at it.
Health and uptime
Every machine carries a state — online, offline, in service — and a 30-day uptime figure; ATM-0042 shows 99.2%. The view itself stays fresh, updated 26 seconds ago in the demo, so the console describes now rather than this morning.
One view across locations
Bucharest, Cluj-Napoca, Iași, Brașov, Timișoara — the demo fleet spans 6 cities and lands in one table. The operator sees a fleet, not a folder of individual machines.
Operations as a workflow
Machines, cash ops, transactions, alerts, and reports are separate tabs of one console, and the data exports to CSV for whatever runs alongside. Adding a machine is a button on the same screen.
The reject bin is a state
Jammed and suspect notes land in the reject bin, and the bin is tracked like a cassette — 42 notes flagged for review on ATM-0042. Emptying it is part of the refill, and the count is part of the record.
A service log per machine
Every machine keeps its own history — replenishments, alerts cleared, firmware updates, consumables — each entry stamped with who did it: a crew id, a remote push, or auto. Thirty days of answers before anyone picks up a phone.
Refills as scheduled work
Refills are scheduled from the machine page, executed by a named crew, and closed with counters reset and the reject bin emptied. Last refill and next estimate are both printed — the schedule is data, not folklore.
Firmware without a site visit
The demo machine took 4.2.1 →︎ 4.3.0 as a remote push, self-test passed, one line in the log. Updating the fleet is a rollout, not a road trip.
Crypto float, watched like cash
Each machine holds two inventories: notes in cassettes and a hot-wallet float — 0.42 BTC on ATM-0042, marked in range. Both run against thresholds; both flag before they run empty.
Heartbeats before complaints
Machines report in constantly, and the console shows the age of the last heartbeat next to uptime. A machine gone quiet for minutes flags red before a customer finds it dark.
Actions gated by role
Locking a machine is immediate — and ops-admin only. Privileged fleet actions carry role gates and audit notes, the same discipline the rest of the platform runs on.
Transactions, per machine and per fleet
Every kiosk order lands in the transactions tab, filterable down to a single machine. What the street did today is a query, not a reconciliation project.
Reports that leave the console
Reports summarize volume by day and by machine, and everything exports to CSV. The accountant's system gets numbers, not screenshots.
Export the log
A machine's full log exports in one action from its own page. When a dispute or an audit asks what happened on the 12th, the answer is a file, not a recollection.
Your brand on the street
Kiosk UI and console both run whitelabel. The machine on the corner carries your name; the operations behind it carry the same discipline either way.
Add a machine in a sitting
A new machine is a row before it is a route: register it with its serial, location, and network, and it appears in the fleet with its own heartbeat. Provisioning is console work, not a project.
Alerts close themselves
The 15% flag scheduled a refill; when the refill landed, the alert cleared — logged by auto. Alerts resolve when reality changes, not when someone remembers to tick a box.