Machine apps and Operator: start here

Illustrated installation atlas — Android basics, every APK role and cabinet checklist.

Use one Operator account to manage supported machines through Kiosk-X. Install the machine application on the cabinet and Operator on the owner's phone or tablet. These applications have different jobs and are not interchangeable.

Status: software and signed artifact checks are recorded below. No physical machine, card payment or product delivery was exercised during this verification. Cabinet XT-202303207146 is awaiting access for diagnosis and acceptance.

Choose the correct machine application

Use the downloads page for the current verified APK links, hashes and exact filenames. Its Download label identifies the file; Latest recorded rollout describes an update offer and may name a different build. Neither proves that a physical cabinet has installed it.

Do not install Reyeah or ZHZN software on the VC EL cabinet simply because its screen runs Android. Preserve the current machine ID, app data, controller settings, license and rollback package before changing any cabinet software. Never uninstall a signed production app just to bypass an update-signature error.

Install Operator on Android or Apple

The Operator platform guide records signed Android and Apple releases, versions, checksums, installation steps and feature differences. Android uses an APK. Apple uses an approved Apple distribution route such as TestFlight; an App Store-signed IPA is not an Android-style direct installer.

Use the fleet owner's account. Confirm the machine is assigned to that account and compare its reported machine ID with the ID shown in the cabinet software. A printed cabinet barcode and the software's machine ID can differ. Resolve that mapping before accepting payments or making stock changes.

Manuals for each job

First supervised sale

1. Confirm stable power/display/touch, the controller identity, correct signed APK and recovery material. On the flickering VC EL machine, finish diagnosis first.
2. Sign into the intended Operator tenant; claim the supported software machine ID and verify live connectivity and configuration readback. Follow address review and installation confirmation for new setup. Confirm installation only after observing this cabinet at the saved address; without onsite evidence, leave it unconfirmed.
3. Configure the correct physical lanes, products, prices and currency. Fill and count the stock; confirm the shopper screen shows the same values. A successful cloud save alone does not prove the cabinet applied it.
4. Bind the actual reader identity for transaction attribution. Separately verify the Nayax merchant account, activation and bank settlement configuration. Complete the approved server transaction integration; signing into MoMa does not connect it to Operator.
5. With the mechanism closed and the delivery area clear, run one supported service test and confirm the actual product arrived. Do not repeat a timed-out vend until its physical result has been reconciled.
6. Make one permitted test purchase. Match the product, delivered quantity, stock change, order, provider transaction, amount and currency. Confirm each stock and payment change occurs once.
7. In a controlled test setup, verify a failed delivery, provider refund or void, duplicate/late callbacks, restart and reconnect. Do not manufacture a jam by putting hands or objects into moving equipment.
8. Record the exact cabinet/controller/firmware/APK/backend/reader combination and results. Only that tested configuration can be marked accepted.

Daily operation

Check connectivity, faults, unresolved orders and refill queues before opening. Use the product/price controls supported by the installed Operator release; the web console remains available for workflows missing from a particular phone build. Count physical stock when restocking and confirm cabinet readback. Separate delivered sales from pending payment, failed delivery and refund requests.

At close, reconcile each machine and currency against its payment provider. MoMa displays Nayax data; it does not transfer revenue into Operator. Nayax pays the merchant under the merchant's agreement. Operator needs matched transaction records to report those sales. Host/venue payouts, advertising estimates and bank deposits are different records; do not add them as if they were all collected card revenue.

Partial delivery or an interrupted report

Do not repeat a vend, purchase or whole-charge refund to clear a partial or held order. A timeout can occur after the motor moved, after a database write, or after a processor accepted a payment operation. An interrupted report hold has no automatic expiry that makes repeating its effects safe.

1. Keep the original order number, cabinet/software machine ID, aisle and unit identifiers. Record reported successes, sensor-confirmed deliveries, failures and pending units separately; a reported success without drop confirmation is not physical proof.
2. Match the original reader or processor receipt, transaction reference, amount and currency. Check the actual captured, voided or refunded state. A submitted request or screen message does not establish processor completion.
3. Have the responsible onsite operator inspect the delivery area and count the affected stock before reconciling it. Preserve the original product and owner record; a late report must not be used to deduct stock from a replacement product, new owner or newer physical count.
4. Give the service owner these records to reconcile the held order. When only part of a purchase is delivered, the correct refund amount can remain unknown. Do not infer it from the whole charge or assume a zero amount. Accounting totals marked unavailable must remain out of settlement and payout decisions until the discrepancy is resolved.

For the durable ZHZN unit-report path, the backend commits that unit's order progress, relevant shelf count and touched FIFO cost records in one database transaction. The whole batch can still be incomplete. Processor capture/refund and report completion are separate steps; a database commit does not certify either, and an unresolved hold must not be cleared by replaying the motor action. Follow the payment reconciliation guide and the cabinet's accepted service procedure.

These software safeguards do not qualify a controller, prove product delivery or replace physical acceptance. Reyeah, ZHZN and any identified VC EL configuration still require their own observed hardware and payment checks.

Keep machine-specific service contacts, the accepted release record, recovery instructions and staff access current. A new APK or firmware, reader profile or controller replacement requires appropriate regression checks before normal trading resumes.