Chip-Based ID Card Readers with a Web API for Developers — iNut's Integrated Solution

Since the chip-based national ID card became the mandatory identity credential for eKYC, time-and-attendance, front-desk check-in, transaction counters, and public-service kiosks, countless organizations have bought dedicated readers to scan the NFC chip instead of relying on phones (which often scan slowly, unreliably, or fall short of biometric-verification standards). But technical teams keep hitting the same bottleneck: the reader they bought only works with desktop software preinstalled on Windows, or requires integration through a vendor-specific SDK/DLL — the moment you need that data on an internal web system, a mobile app, or a multi-branch dashboard, you're stuck writing your own bridge layer, which costs time and gets brittle every time the vendor updates its SDK.

The problem was never reading the chip — NFC/ICAO technology has long been standardized. The real problem is getting that data out through a simple Web API that any system can call with a single HTTP request, instead of being locked behind a closed desktop application. That's exactly the gap iNut fills.

Looking across the market, chip-based ID authentication devices (NFC/MRZ readers, with or without a face-capture camera) have done the "read fast, read accurately, comply with ICAO/ISO 7816" part well, and most also meet the mandatory technical regulations. What most of them have in common: they ship with a desktop app installed on a PC or provide an SDK/DLL for a specific language (.NET, Java...) — fine for a single transaction counter, but rigid the moment you need to embed it into a running web system, sync data across branches, or build a mobile app sharing the same authentication source.

iNut supplies a complete hardware combo: a chip-based ID reader (NFC scanning to ICAO/ISO 7816 standards, with face authentication) paired with a processing board developed by iNut. Instead of forcing every workstation to install desktop software or embed an OS-specific DLL, this board exposes all the captured data through a REST/JSON Web API — callable with a plain HTTP request, regardless of what language the backend is written in (PHP, Node.js, Python, Java, .NET...) or whether it runs on Windows, Linux, or the cloud.

The current demo — successfully integrated — uses the Hanel HN-212 reader. If you already own a different ID reader model, iNut can customize the processing board for compatibility — just get in touch to discuss your specific device.

Identity verification isn't just a technical challenge — it's a legal one too. The ID reader used in the demo (Hanel HN-212) has been tested and certified against the applicable technical regulations and is eligible for the certification sticker issued by the center under C06 — Vietnam's Ministry of Public Security, reading the chip to ICAO and ISO 7816 standards. iNut's processing board and Web API sit as the integration layer behind it — they don't change how the reader reads the chip, they simply expose that data through an open standard your system can consume.

Because the data comes straight out through a Web API, iNut's solution slots easily into any workflow that needs chip-based ID authentication:

Detailed configuration, the list of compatible readers, and pricing based on your rollout (number of sites, whether you already own a reader or need a new one) aren't something we publish in full here — message iNut directly for detailed guidance and a quote that fits your setup.

Does your system already have a Web API ready to receive ID authentication data, or are you still opening a separate desktop app every time you need to verify someone?