How Does Water ATM Software Work?

A Water ATM looks simple from the outside: insert a coin or tap a card, and purified water comes out. Behind that simplicity is a software system that has to track machine health, reconcile payments across multiple methods, and give operators enough visibility to keep dozens or hundreds of machines running. This article walks through how that system actually works, using Hydrotec's own Arosia Water ATM platform as a concrete example.

The five layers of a Water ATM system

1. The dispensing unit — the physical machine, with purification (typically RO and UV stages), a payment interface, and a controller
2. Connectivity — how the machine talks to the cloud: cellular is most common, with solar and battery backup for off-grid sites
3. The cloud platform — ingests events from every machine, stores them, and applies rules (like low-tank alerts)
4. The operator interface — dashboards and mobile apps built on top of that data
5. Integrations — APIs connecting machine data to payment processors, accounting, or partner reporting

What a dispensing event actually contains

Every time a customer fills a container, the machine generates an event with several pieces of data: which machine, how much volume was dispensed, which payment method was used, and the timestamp. That event is what makes fleet-wide reporting possible — without it, an operator would need to physically check a meter on each machine.

{
  "machine_id": "arosia-500-0142",
  "site": "kasba-bus-depot",
  "volume_ml": 1000,
  "payment_mode": "rfid",
  "amount": 5.0,
  "timestamp": "2026-08-14T07:12:03Z"
}

Payment modes and reconciliation

Water ATMs commonly support three payment modes: RFID card-based dispensing (a recharged card debited per use), coin-based dispensing, and digital payment dispensing. Each mode generates its own transaction trail, and part of what Water ATM software does is reconcile all three into one revenue ledger per machine — instead of an operator manually adding up coin collections against a separate digital payment report.

Why connectivity design matters more than people expect

Water ATMs are frequently deployed in places with unreliable grid power or patchy connectivity — that's often exactly where they're needed most. A Water ATM platform built around always-on urban connectivity assumptions will struggle at a rural or off-grid site. Machines need to buffer dispensing events locally and sync when a connection is available, and hardware needs to support solar and battery power as standard options, not an afterthought.

A solar-powered kiosk running on battery backup with intermittent cellular connectivity isn't an edge case in Water ATM deployment — for many operators, it's the typical case.

Water quality: continuous vs. periodic

Where a machine has quality sensors installed, pH and TDS readings are logged continuously and tied to the machine and timestamp — the same way dispensing events are. Where sensors aren't fitted, quality is typically checked periodically and logged manually. Either way, the goal is one continuous quality record per machine rather than a certificate that goes stale the day after testing.

What operators actually look at day to day

• Which machines are online right now, and which need attention
• Revenue and volume dispensed, usually compared day-over-day or week-over-week
• Any water quality readings outside the expected range
• Open maintenance issues and their status

This is exactly what a Water ATM Dashboard is built to surface — see our dedicated breakdown of dashboard architecture and features for more detail, or our Water ATM API guide if you're integrating this data into your own systems.