Kiosk Hardware Integrations in India

Integrations

Peripherals and systems AtashiTech kiosk software integrates

What can be bolted to a kiosk, what can sit behind it, and how a device that is not on this page gets qualified.

A kiosk application is judged by the things it talks to. A screen that cannot print a badge, read an identity document, take a payment or open a gate is a web page on a stand. AtashiTech writes the application and the integration layer underneath it: the code that drives each device attached to the terminal, and the code that keeps the terminal consistent with the systems your organisation already runs. AtashiTech does not manufacture kiosks, enclosures or peripherals; the hardware comes from your vendor and the software makes it work together.

The categories below cover what our packaged solutions already drive and what the kiosk application development service extends. Named products are examples of devices in each category, not an exhaustive list, and adding a model is a scoped piece of work rather than a barrier.

At a glance

Device categories we drive

Printing

Badge and label

Receipt and token

A4 documents

Scanning

Barcode and QR

ID and passport

Flatbed documents

Identity

Fingerprint

Face recognition

RFID and NFC cards

Payment

EMV card terminals

UPI QR display

Wallet and loyalty

Cash

Note acceptors

Coin acceptors

Change dispensing

Access

Wiegand controllers

Turnstiles and barriers

Relay modules

Measurement

Weighing scales

Vital-signs devices

Serial and USB instruments

Display

Token and menu boards

Cameras over ONVIF

Audio guidance

Peripherals

What each category does, and which solutions use it

Every device is a piece of integration work with its own SDK, its own failure modes and its own test cycle on real hardware.

Printers

Badge and label printers such as Zebra units driven over ZPL produce visitor and contractor passes; thermal receipt and token printers, including Epson devices addressed through OPOS, produce tokens, receipts and acknowledgements; an A4 printer inside the enclosure prints certificates where a citizen or a worker must leave with a document. Used by visitor management, queue management and bill payment.

Scanners and readers

Fixed and handheld barcode and QR scanners from vendors such as Datalogic and Honeywell read products, coupons, pre-registration codes and printed certificates. Document readers extract passport machine-readable zones, the QR code printed on Aadhaar and driving-licence barcodes by OCR. Flatbed and sheet-fed scanners capture supporting documents for an application. Used by self-checkout and patient registration.

Biometrics and cards

Fingerprint readers such as Suprema devices, face-recognition cameras, and proximity, RFID or NFC cards identify workers, contractors and staff where a policy permits it. Biometric login is what makes an unattended employee terminal safe to leave in a corridor. Used by employee self-service and contractor induction.

Payments

EMV chip and contactless terminals from providers such as Pine Labs and Worldline take card payments with the card data staying inside the terminal, which keeps the kiosk out of the most demanding part of PCI scope. An on-screen UPI QR code covers customers who carry no card, and gateways such as Razorpay settle the transaction. Used by food ordering and collection kiosks.

Cash handling

Note acceptors and recyclers from makers such as JCM, CPI and Crane, coin acceptors and change dispensers make a kiosk usable by people who do not pay digitally. Cash brings the strictest software discipline in the catalogue: the transaction is recorded the moment a note is stacked, posted once when connectivity returns, and reconciled against the acceptor's own count. Used most heavily by banks and NBFCs.

Access control and gates

Wiegand-based turnstile and door controllers, boom barriers and relay modules are driven directly by the application on a pass result, or the decision is handed to the access-control platform through its API. This is what turns an induction or a visitor badge into a physical outcome. Used by safety training and visitor management.

Scales and instruments

Weighing scales such as Mettler-Toledo units validate the weight of a bag at a self-checkout lane and price loose produce. Clinical instruments, including blood-pressure monitors, pulse oximeters and weighing scales, connect over USB, serial or Bluetooth and attach readings to a visit record. Serial devices are addressed directly or through Modbus where the plant already uses it.

Displays, cameras and audio

Token boards, menu boards and wayfinding screens are fed from the same content the kiosk sells or serves from, so the two cannot disagree; the players are built under the Android TV and signage service. Cameras integrated over ONVIF capture visitor photographs, and audio prompts carry the journey for people who cannot read the screen.

Back office

Systems behind the kiosk

A kiosk that does not agree with the system of record creates work rather than removing it.

ERP — contractors, purchase orders, items and finance postings, whether that is SAP, Oracle or AtashiTech's own ERP software.
HRMS and workforce platforms — the employee master, leave, attendance corrections and shift schedules, including our own HR & payroll platform where no HRMS is in place.
HIS, HMIS and EMR — patient lookup, registration, arrival, screening answers and vitals, over HL7 FHIR where the vendor exposes it and over the vendor's API where it does not.
POS and inventory — the item master, prices, promotions, stock and the sales postings a self-checkout lane or an ordering kiosk produces.
Learning management — where the LMS is already the official record of training, induction results are written to it rather than kept in a second place.
Payment rails — gateways for card and UPI settlement, and BBPS for multi-biller utility collection.
Messaging — SMS, WhatsApp and email gateways such as Twilio for tokens, host alerts, receipts and confirmations.
Directory and access control — Active Directory or the HRMS for host lookup and staff login, and the access-control platform that decides which doors a badge opens.
Student information and campus systems — students, courses, fee heads, library dues and hostel allocations, as used by schools, colleges and universities.

The integration work itself is delivered by the cloud, DevOps and integration service, and where a department, bank or hospital needs an operator portal or reporting alongside the kiosk, that is built as a web application.

Method

How the integration is actually done

Four mechanisms cover almost everything a kiosk needs to talk to.

Vendor SDKs and standard interfaces

Most printers, scanners, biometric readers and payment terminals ship a Windows SDK, and retail devices frequently support OPOS. Using the vendor's own interface rather than a generic one is what makes error handling reliable: the application can tell the difference between out of paper, cover open and offline, and say something useful on screen instead of failing silently.

Serial, USB and network devices

Scales, older instruments and controllers speak over serial or USB, sometimes through a USB-to-serial bridge, and network devices are addressed over TCP. These are wrapped in a device layer inside the application so that a model change later is a driver change rather than a rewrite of the journey.

Wiegand, relays and gate control

Access decisions reach the physical world either as a Wiegand credential presented to a controller, or as a relay closure from an I/O module wired to the turnstile or barrier. The decision is taken locally on the kiosk so that a gate keeps working when the network does not.

Cloud APIs and file exchange

Back-office systems are integrated over their REST or SOAP APIs where they have them, and over scheduled file exchange where they do not, which is still common in retail and in campus accounts. Either way the kiosk holds local state and reconciles once, so an outage never produces a duplicate posting.

New devices

How a device that is not on this page gets qualified

The list above is what we already drive. Adding a model is routine, and it follows the same short path every time.

Name it exactly. Make, model, interface and firmware, because two units with the same marketing name can behave differently.
Check the SDK. Whether the vendor supplies a Windows SDK or a standard interface, and on what licence terms, decides how much work follows.
Get one on the bench. A sample device is integrated and exercised against the real journey, including the failure paths, before it is committed to a proposal.
Define the failure behaviour. What the screen says when the device is missing, jammed, empty or offline, and whether the journey can continue without it.
Add it to the fleet checks. Paper, ribbon, cash level and device health are reported to the kiosk management platform so that a fault is known before a user finds it.

Because the device list drives so much of the effort, it is settled during scoping rather than during commissioning. The scoping and quoting page explains where it fits, and the Windows versus Android comparison covers why the platform choice usually follows the peripheral list.

Send us your parts list

Tell us the devices in the enclosure and the systems behind the counter. We will say which are already integrated, which need qualifying, and what that means for the journey.

Talk to an engineer Browse the solutions

Frequently asked questions

Three categories. Badge and label printers such as Zebra units driven over ZPL for visitor and contractor passes; thermal receipt and token printers, including Epson devices addressed through OPOS, for receipts, tokens and acknowledgements; and an A4 printer inside the enclosure where a citizen or a worker must leave with a document.

EMV chip and contactless terminals from providers such as Pine Labs and Worldline, an on-screen UPI QR code for customers who carry no card, wallet and loyalty scanning, and gateways such as Razorpay for settlement. Card data stays inside the terminal rather than passing through the kiosk application, which keeps the kiosk out of the most demanding part of PCI scope.

Yes, where the enclosure carries the hardware: note acceptors and recyclers from makers such as JCM, CPI and Crane, coin acceptors and change dispensers. Cash brings the strictest software discipline in the catalogue, because the transaction has to be recorded the moment a note is stacked, posted once when connectivity returns, and reconciled against the acceptor's own count.

Fingerprint readers such as Suprema devices, face-recognition cameras, and proximity, RFID or NFC cards for workers, contractors and staff, subject to the organisation's own policy. Biometric login is what makes an unattended employee terminal safe to leave in a corridor or beside a canteen.

Yes. Document readers extract the machine-readable zone of a passport by OCR, read the QR code printed on Aadhaar and read the barcode on a driving licence, so demographic fields are filled for confirmation rather than typed. Whether the document image is retained or discarded after extraction is a per-site data-policy setting.

Yes, either by presenting a Wiegand credential to the controller, by closing a relay from an input-output module wired to the turnstile or barrier, or by handing the decision to the access-control platform through its API. The decision is taken locally on the kiosk so that a gate keeps working when the network does not.

ERP including SAP, Oracle and our own ERP software; HRMS and workforce platforms; hospital systems over HL7 FHIR or a vendor API; POS and inventory; learning management systems; payment gateways and BBPS; SMS, WhatsApp and email gateways; Active Directory and access-control platforms; and student information systems. The list is by category because every site's instance is configured differently.

Adding a model is routine. We name the device exactly by make, model, interface and firmware, check whether the vendor supplies a Windows SDK or a standard interface and on what terms, integrate a sample on the bench against the real journey including its failure paths, define what the screen says when the device is missing or jammed, and add its health to the fleet checks.

That is the point of the offline-first design. The journey is held on the terminal with the data it needs cached locally, so the kiosk keeps serving, and updates for the back-office system are queued and posted once when the link returns. Steps that genuinely need a live connection, such as card settlement, say so on screen instead of failing at the last moment.

No. AtashiTech writes the application and the integration layer; the enclosure, the PC inside it and the peripherals come from your hardware vendor. We will help you specify the parts list, because the device list drives more of the project effort than almost anything else.