Multi-Device Palm Vein Offline Deployment

Register smart.
Match locally.
Scale across entrances.

For multiple doors, floors or sites, X-Telcom helps you plan whether users register on each terminal or use a customer-managed feature synchronisation workflow.

Local Matching + Feature Synchronisation Offline capable
Register Authorised terminal creates palm feature template
Local Server Manages and distributes templates only
Local Match Each device performs recognition independently
Entrance A
Entrance B
Floor 3
Site 2

Do employees register once or on every device?

That is the key deployment question. In pure local mode, every terminal only recognises templates stored locally on that terminal.

Few devices: register on each terminal

Simple and direct for single-door or small fixed-user deployments.

  • Each device operates independently
  • Users register on the devices they will use
  • Minimal integration work

Many devices: synchronise feature templates

A customer-managed local system distributes templates to authorised terminals.

  • Register once on an authorised device
  • Local server distributes templates
  • Each terminal still matches locally
Important Clarification

The local server does not perform recognition.

In a local matching deployment, the management server is only a template management and distribution node. The device still completes the biometric comparison locally.

Employee registers

Template generated on an authorised palm vein device.

Template is synchronised

Customer-managed local server stores and distributes authorised templates.

Devices match locally

Each terminal recognises users using its own local template database.

Feature transfer ≠ matching location

Templates can move between systems, but where the comparison happens is decided by firmware.

Local Matching Firmware

Comparison happens on device

  • Supports feature import / export / synchronisation
  • Works without cloud dependency
  • Matching cannot be moved to server by business logic
Server / Cloud Matching Firmware

Comparison happens on server

  • Device captures palm data
  • Server performs biometric comparison
  • Matching cannot be moved back to device by workflow changes

What the X-Telcom Palm Vein SDK provides

The SDK is the biometric foundation. The customer or integrator builds the business workflow around it.

X-Telcom SDK

Biometric capabilities

  • RGB / IR palm image acquisition
  • Palm print and palm vein feature extraction
  • Registration, verification and identification APIs
  • Feature template import and export interfaces
Customer Application

Business logic

  • User accounts and permissions
  • Multi-device synchronisation workflow
  • Access control, payment or attendance rules
  • Integration with e-wallet, bank, HR or ERP systems

Plan the architecture before rollout

Tell us your site layout and user flow. We help you choose the correct palm vein deployment path.

Single entrance
Multiple doors
Multiple floors
Multiple sites
Local matching
Server matching
Feature sync
SDK integration

Build the right palm vein architecture from the start.

Share your device quantity, entrances, locations and matching model. X-Telcom will help evaluate the right SDK and firmware architecture.