Fingerprint Verification

biometric-core fingerprint engine + provider interface.

Roadmap

Runs against the biometric-core fingerprint engine (mock adapter until a certified provider is registered).

Engine

src/lib/verification/biometric-core/fingerprint (mock adapter — ready for provider)

API

POST /api/public/biometrics/v1/enroll · /compare

Roadmap service — not part of the Veridexa launch

Fingerprint Verification is on the Veridexa roadmap. It is not offered commercially today: no certified engine, hardware, or trust anchors are integrated, and nothing on this page should be read as an available production capability. The contracts, storage schema, and API surface documented below exist so a certified provider can be integrated later without call-site changes. Mock adapters are used for tests only and never produce verification evidence.

Live Veridexa services today: Document Fraud Detection, Face Verification, and Biometric Portrait Consistency.

The fingerprint engine mirrors the shared biometric-core surface. A mock provider is registered for tests and CI; a certified fingerprint SDK slots into the same provider interface without any call-site changes.

What is implemented

  • Engine contract: capture, extract, verify 1:1
  • Provider registry validated by tests
  • Exposed on /enroll and /compare
  • Stored in the unified biometric_templates table

Modules

src/lib/verification/biometric-core/fingerprint/
  engine.ts
  types.ts
  mock-adapter.ts
src/lib/verification/biometric-core/providers/mock-fingerprint.ts
biometric-core.api/v1 · isolated from Fraud Detection · mock adapters clearly labelled; certified providers register behind the same contracts.