Billable messages are those actually handed to the provider. Failed and skipped messages cost nothing and are shown separately. The rate in force when each message was sent is stamped on it, so past periods do not change when a rate is renegotiated. Set rates on the Distributor, Parent Customer or End Customer record — the most specific wins.

A role is a scope (which records it can reach) and a set of capabilities (what it can do). These are independent: granting a capability never widens scope — a role scoped to one end customer still only ever sees that customer's kiosks. Built-in roles cannot be edited; copy one to start from.

Emails administrators when something needs attention — TLS certificate expiry, failed database migrations, expired kiosk licences. Checked hourly. Each condition mails once per repeat window rather than on every check, so a persistent fault does not flood the inbox. Requires SMTP to be configured under Admin → SMTP.

Append-only record of every authenticated action and its API result. The database rejects any attempt to modify or delete these rows. Passwords, PINs, API keys and tokens are redacted before storage.

Kiosks ship pointing at this KMC and enrol themselves on first connection using the bootstrap key below. Each machine then runs on a 60-day trial from that moment, and needs a licence issued here before it lapses. Treat the bootstrap key like a password: anything holding it can enrol.

Customers created here are pushed down to the kiosks you assign them to — for a centrally supplied list of who may use the machines. Kiosks reconcile against this list, so removing a customer here removes them from those kiosks. Records created on a kiosk itself appear under Kiosk Customers and are never overwritten.

Transactions carry 10 reserved passthrough columns (custom_1…custom_10) for customer-specific business process fields. Give a slot a label to activate it — empty slots stay hidden everywhere. Enabled makes it visible on the transaction detail; Show in table also adds a column to the Transactions list. Changing a label only changes the display name; stored data is untouched.