Skip to content
Masanchara
An overhead exploded diagram of a POS terminal and merchant workflow reference

Merchant knowledge base

Documentation

Masanchara helps merchants run sales, manage stock, track credit, and close the business day with the app that is actually installed on the device.

Setup & security

Device-bound security & PIN lock

What this protects

Masanchara is designed for a single physical device and a shared till environment. The app includes device-bound activation checks, local PIN sign-in, app lock, and timed session expiry. These controls help protect a local POS app from casual misuse, but they are not a substitute for securing the device itself and keeping backups off-device.

Staff sign-in and lock behaviour

  • Use the PIN flow for staff sign-in and authorisation.
  • The app also includes an app lock and session timeout setting, which can be configured from the settings area.
  • When the device is idle for the configured period, the app locks locally rather than relying on an external service.

What to expect in practice

  • The app checks the current device state during activation and licence validation.
  • A PIN or security action is local to the device; it is not a cloud login that automatically follows a user between devices.
  • Ledger entries and security-related records are part of the same local data set, and the app includes integrity checks to detect tampering and drift in its own verification paths.

Important limits

  • Device binding and local integrity checks help with device-level security and evidence, but they do not make the system immune to theft, a compromised Android device, or a restored backup created from an untrusted source.
  • If a device is lost or replaced, the safe recovery path is to restore from a verified backup and re-activate the device according to the app's licence flow.