PALM TERMINAL ARCHITECTURE

A managed palm terminal for payment and more

The reference terminal supports Palm Vein/Palm Print capture, server-defined UI, two operating modes, multiple network options and centrally governed device lifecycle.

01

HOST / USB mode

The existing POS or PC remains the controller.

Command channel

Documented USB HID, CDC or vendor protocol carries UI, capture and result commands.

Business logic

Amount, merchant, order and workflow remain under the host application.

Use cases

Payment, attendance, access control, identity and custom approved flows.

02

Direct backend mode

The terminal becomes a managed IP endpoint.

OpenAPI control

Backend authorizes business requests and stores system state.

MQTT command plane

MQTT 5.0 over TLS/mTLS delivers UI, commands, events and results.

Fleet operations

Certificates, configuration, logs, firmware, health and alerts are governed centrally.

03

Procurement deliverables

A device is accepted as a system component, not only hardware.

Protocol pack

USB manual, OpenAPI, topic catalogue, error model and sample code.

Security pack

Firmware identity, secure update, device certificate, hardening and vulnerability process.

Test pack

Palm quality, PAD/liveness evidence, performance, endurance and integration test cases.

MOBILE-ID

Plan a measurable PalmPay PoC

Align the business case, identity path, terminal mode, bank integration, security controls and acceptance metrics with Mobile-ID.

Contact Mobile-ID