Frequently asked questions

It puts a self-service machine online end to end: Hero Nexus, our Android edge software inside the payment terminal, takes payment and drives the machine; QuadC, our cloud, collects telemetry, manages devices and distributes updates; and HERO, our browser-based dashboard, is where operators watch sales, stock and alarms live — with no software to install.

Vending and coffee machines over MDB or Executive, machines driven directly through the vending machine controller (VMC), and PLC-controlled machines — car washes, EV chargers, kiosks, lockers, laundry — over Modbus. If the machine has a controller, we have a protocol path to it.

Yes. Flower vending machines — refrigerated locker or carousel cabinets — are PLC- or VMC-controlled machines like any other we integrate: the terminal takes card, contactless and QR payments, the platform reads cabinet temperature and door state as telemetry, and HERO shows stock and sales per compartment so wilted stock and empty lockers get caught early.

Soup machines work like hot-drink machines: they speak MDB or Executive, so Hero Nexus drives them the same way it drives a coffee machine. The platform reads boiler temperature and ingredient levels as telemetry, and low-ingredient alarms reach the operator in HERO before the machine stops selling.

No — that is the point of our Smart VMC approach. A machine engineered for coins decades ago keeps its own controller; Hero Nexus registers on the machine's bus as a cashless device, so it starts accepting contactless cards, meal cards and QR payments with no change to the machine itself.

Credit and debit cards (contactless and chip through the terminal's certified EMV stack), QR payments, and the Turkish meal-card ecosystem — Edenred, Multinet, Setcard, Metropol and Sodexo — plus İstanbulkart. One integration covers all of them.

It keeps selling. Hero Nexus is offline-first: it holds a local database on the device, so payments authorize, vends complete and telemetry is recorded while the link is down — then everything reconciles to QuadC the moment the connection returns.

No. The platform is hardware-independent: it runs on Nexgo today and is built to run on PAX, SUNMI, Castles and Newland. The device-specific pieces live below the platform layer, so swapping terminal hardware doesn't mean rebuilding integrations or retraining operators.

Over the air. QuadC distributes signed updates to the fleet remotely — new features, payment configurations and fixes arrive without a technician visiting each machine.

Yes. QuadC exposes an open API for devices, sales and telemetry, and HERO exports reports to Excel and PDF. Your data is yours to integrate, whether into ERP, BI or a custom back office.

Since 1999 — we put the first online card payment on a vending machine in Turkey, on Yapı Kredi infrastructure, added contactless in 2008 and meal cards in 2015. The payment problem taught us the machines; the machines became the platform.

Talk to engineering — not a sales script. Tell us what your machines are and how your fleet runs; we'll map the integration path, usually starting with a pilot machine, and take it from there.