signzy

API Marketplace

downArrow
Logo
Responsive
Decorative line

Genuine Presence (liveness outcome)

Overview

Genuine presence is the affirmative result of a liveness check confirming a real person is present during biometric capture. It underpins remote onboarding and step-up authentication by ensuring the selfie or video is not a replay, mask, or synthetic media. Systems derive this outcome from active prompts, passive cues, or depth sensors and pair it with secure capture, device attestation, and quality thresholds.
Because false accepts carry high fraud risk, thresholds are tuned by scenario, and outcomes feed risk engines along with document checks and registry hits. Programs should log evidence, SDK versions, and decisions, and periodically validate performance with attack testing. A clear genuine-presence signal reduces impersonation, improves regulator confidence, and enables lower friction elsewhere in the flow.

FAQ

What determines a genuine presence pass?

Consistent biometric signals across frames, expected motion or depth responses, and integrity markers from secure capture that collectively resist spoof and injection attempts.

How is it different from a face match?

Face match confirms similarity to a reference. Genuine presence verifies a live capture by the real person, stopping printed photos, screens, or deepfakes from passing.

When should thresholds be stricter?

New account creation, high-value actions, or risky corridors. Lower friction is acceptable for low-risk logins if combined with other strong factors.

What evidence should we store?

Outcome, reason codes, capture metadata, SDK version, and minimal frames if permitted. Retain only as long as policy or regulation requires.