02 Product

One endpoint for every peripheral.

Devices Server turns device protocols into ordinary HTTP requests. Your application sends JSON; the server deals with firmware versions, buses, retries and the realities of cash-handling hardware. It is one product on the platform behind PILOT and SolarView.

Interface / HTTP · JSON Hardware / 05 device classes Clients / any HTTP client

— The problem

Hardware shouldn't shape your codebase.

Every device family has its own dialect, and every firmware revision adds a footnote. Integrating them directly means protocol code, device-specific edge cases and a support burden that grows with each installation.

Devices Server removes that layer. It presents one stable API, and absorbs the differences underneath — so your team can spend its time on the product.

Protocol-agnostic Firmware-aware Language-agnostic

device-gateway / example JSON

Request

POST /v1/devices/dispenser-02/dispense
Content-Type: application/json
Authorization: Bearer <token>

{
  "units": 5,
  "currency": "PLN",
  "idempotency_key": "tx_8f21c"
}

Response

HTTP/1.1 200 OK

{
  "status": "settled",
  "device": "lcdm-2000",
  "protocol": "serial",
  "reconciled": true
}

Illustrative interface — shape of the API, not a live endpoint ● serial

— How it works

A short path between software and hardware.

The server runs beside your application, or in the operating environment you already manage.

01 / Your app

Call the API

Send an HTTP/JSON request from C/C++, PHP, Haskell, TypeScript — or a single curl command.

02 / Request

Describe intent

Accept a note, dispense five units, print a receipt: operations, not protocol sequences.

03 / Server

Translate & execute

The server selects the protocol, drives the device and handles retries, timeouts and errors.

04 / Device

Money moves

The physical operation happens once, with a reconciled result returned to your application.

— Supported hardware

Built for the peripherals you actually run.

Plus 50+ printer models and banknote recyclers including CashCode B2B.

Bill acceptors & recyclers

NV9, NV10 and CashCode B2B recyclers across pulse, ccTalk, ID-003, MDB, eSSP, EBDS and ICT-104.

Printers

Hwasung, TG02, SP1, CR158 and more than 50 ESC/POS and SSP printer models.

Dispensers & scanners

LCDM1000, LCDM2000 and LCDM4000 cash dispensers, plus FM100 and FM3056 scanners over RS-232.

Because the API is the contract, hardware can change underneath it. A new printer model or a firmware update becomes a server-side concern — not a release of your product.

One API · future device support

The API surface is deliberately small and documented. That keeps integration short, makes behaviour predictable and leaves room for new device support without breaking existing clients.

Scope your hardware See the platform products

— Why teams choose it

Less protocol code. Fewer surprises.

01Faster time to marketIntegrate against one documented API instead of nine protocols.
02No language lock-inAnything that speaks HTTP can drive the hardware.
03Firmware handled for youDevice quirks and firmware variants live behind the interface.
04Room to growNew devices are added server-side, without changing your client.

→ Next step

Let's build something real.

eltait.pl@gmail.com

Start a technical conversation

Phone / +48 607 186 996 Office / Raciborska 13, Gliwice, PL Hours / Mon–Fri, CET