BIOMETRIC SCIENCE

Palmprint — ridges, creases and palm texture

Palmprint is treated as a separate surface-image modality using ridge, crease and texture information, quality control, representation and matching. It is not palm-vein.

◈
SOURCEAuthoritative / document
◈
CAPTUREDevice / SDK
◈
VERIFYDocument + biometric
◈
ASSUREPolicy + risk
◈
DECIDEClaims / status
◈
EVIDENCEAudit / trace
TECHNICAL REFERENCE

Palmprint: palm-surface imagery and region-of-interest features

Palm image → ROI/quality → feature/template → matching → decision

Distinct from palm vascular

Palmprint uses visible palm-surface ridge/line/texture information, while palm vascular uses subcutaneous vascular patterns with different sensing/illumination. The modalities are not described with a shared template.

Capture geometry

Palm orientation, distance, ROI and full/partial capture affect segmentation and quality. Current documentation publishes no specific geometry without a device/test source.

ROI and quality

Quality should consider usable palm region, blur, perspective and occlusion according to the engine rather than copying face/fingerprint criteria.

Enrollment and match

Enrollment binds palm samples/templates to a subject; verification/search behavior must follow the actual matcher/process.

Device dependency

Camera/sensor, driver and illumination form part of the tested profile. Datasheet capability is not equivalent to CheckID-tested compatibility.

Failure and evidence

Incomplete palm region, poor perspective/blur, failed segmentation, missing enrollment and low match outcomes should remain distinct where the implementation exposes them.