Who writes the software that runs self-service kiosks

The kiosk is the easy part. The software is the moat

Analysts put the self-service kiosk market at roughly $39.1 billion in 2025 and about $67.2 billion by 2031, a ~9.5% CAGR, with self-checkout the fastest-growing segment (Ken Research, 2026). That is a tailwind for everyone in the space, but it guarantees nothing for any single point.

Walk any 2026 trade-show floor and the hardware looks finished. The catch is that the same enclosure can either bring in money every day or quietly lose it — and the difference is not the screen but the layer beneath it. That layer is the hardest part to get right and the easiest to underestimate.

Does the payment actually reach the machine

On an MDB bus inside a vending machine, or on an RS-485 line, the controller is the master and the reader answers only when it is polled. If the two disagree on level or address, the reader can report “paid” while the machine does nothing. The software has to speak the device’s protocol rather than assume that a working terminal means a working system.

This is the first thing to check when “the terminal sees the payment but nothing is dispensed”: not the terminal, but whether the controller polls the address the terminal sits on, and whether both sides settled on a shared protocol level.

What happens when the network drops

For unattended points an outage is the normal case, not the exception. The terminal may approve a payment offline; the question is whether the bay still starts and whether the event survives the outage. The answer is a durable local log — what, when, which device, the response code, the outcome — stored in UTC and synced to the server later, once the link returns.

Without such a log every outage becomes a hole in the books that cannot be closed afterwards. With it, an outage is a line in the report rather than a lost day of revenue.

Who reconciles the shift

Three numbers must match: the post, the bank, and the cash box. That reconciliation should arrive by itself, every morning, rather than being assembled by hand at month end. A mismatch that repeats every shift is not a random glitch — it is a design gap in the system.

“AI-ready” is a hardware label. “Reconciled by morning” is a software promise. The kiosks shipping now are built to host AI and richer payments, and that only raises the stakes for the layer underneath: more payment methods, more devices, more edge cases — and the same unglamorous requirement to prove, two days later, exactly what happened at each machine.

Frequently asked