Signature Verification

biometric-core signature engine + provider interface.

Roadmap

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

Engine

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

API

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

Roadmap service — not part of the Veridexa launch

Signature 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 signature engine implements the shared biometric-core contract (capture quality, template extraction, 1:1 verify, audit). A mock adapter powers tests today; the interface is stable so a certified signature provider can be registered without touching call sites.

What is implemented

  • Engine contract: enrol, extract template, verify 1:1
  • Provider registry with mock/production gate
  • Wired through /enroll and /compare APIs
  • Persistence via unified biometric_templates catalogue

Modules

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