Skip to main content

Biometric Identification Service

Biometric Identification Service (formerly LFIS) is a high-performance, server-based biometric API for 1:N identification and 1:1 verification using face and palm modalities. It is the path for centralized, large-gallery identification beyond the on-device 1:N limit (~1:50K). Built with cloud-native principles, it can be deployed on-premises or in the customer's cloud. Passive liveness detection is available as an add-on for both face and palm.

Client application kiosk · handheld · phone Biometric Identification Service REST API Detection Liveness Extraction Matching Watchlist server-side gallery image / template identity result watchlist & members search · enroll

Capabilities​

FeatureDescription
Detection & quality assessmentAutomatic detection of faces and palms from incoming images, including quality assessment to ensure compliance with recognition thresholds.
1:N identificationSearches a live-captured image or extracted template against a specific watchlist – or all watchlists at once – and returns the best match, or a ranked candidate list when configured. Face and palm.
1:1 verificationCompares a probe against a reference facial image and returns the confidence they are the same person. Face only.
Passive liveness detectionDetects presentation attacks without requiring user interaction, for both face and palm modalities.
Watchlist managementEnroll, update, and remove biometric data via the API. Supports dynamic creation and management of multiple watchlists within the database.
RESTful APIReal-time matching, asynchronous queries, and secure communication (TLS, authentication tokens). Integrates with web, mobile, or embedded client applications.
Cloud-ready deploymentRuns as a local server component or scaled on Kubernetes/Docker-based infrastructure.

Modalities​

  • 1:N identification – face and palm.
  • 1:1 verification – face only.
  • Passive liveness – add-on for both face and palm.

When to use it​

Use the service for centralized, large-gallery identification that exceeds the on-device 1:N limit, or when many client devices must share one gallery and identities are managed centrally – for example watchlist screening, airport monitoring, attendance systems, and payment kiosks. Client devices (kiosks, handhelds, phones) get real-time identity results without holding the gallery locally.

In this section​

  • Integration – interfaces, and how to send images or templates.
  • Deployment – where and how the service runs.
  • REST API – endpoints, sample requests, and the full generated reference.

See also​