Face Comparison
Compare the guest to the submitted identity document.
Compare a live capture with an identity-document photo, supported NFC portrait, or previously verified reference to confirm the same person is present.
- Part of a guest compliance session
- Hosted, API, and webhooks
- Configured human review
How it works
Match the face behind the identity
Capture a trusted reference, confirm presence, and return a configurable decision.
Capture a trusted portrait
Use the image from a verified identity document, supported NFC chip, or approved previous session.
Complete liveness
Confirm that the comparison capture comes from a real person who is present during the session.
Compare the faces
The biometric comparison produces a configured similarity result using the live and trusted portraits.
Apply decision rules
Approve, retry, reject, or route the session for additional verification or authorized review.
Identity binding
A valid document still needs to be connected to its holder
Face Match links a live, liveness-checked capture with a trusted portrait so the workflow can detect impersonation and route uncertain cases consistently.
Document ownership
Compare the person completing the session with the portrait on the submitted identity document.
Step-up verification
Confirm identity again before account recovery, profile changes, access release, or other sensitive actions.
Reviewable outcomes
Keep the configured comparison result and session context available for authorized review and audit workflows.
Capabilities
Face comparison within the wider workflow
Combine comparison with the source and assurance level the use case requires.
Discuss your workflow- 01Selfie-to-ID comparison
- 02Selfie-to-NFC portrait comparison
- 03Liveness pairing
- 04Configurable thresholds
- 05Step-up routing
- 06Reviewable session evidence
Use cases
Where Face Match fits
- Guest-to-document confirmation
- Remote arrival clearance
- Self check-in access
- High-risk booking review
- Repeat guest rechecks
- Dispute evidence support
Security and privacy
Controlled by design, documented in public.
Every module uses the same access, output, audit, and retention boundaries as the wider guest compliance workflow.
Minimum necessary output
Operators receive the approved status and fields rather than unrestricted document copies by default.
Booking-linked history
Configured consent, status, access, and review events remain tied to the relevant session.
Controlled retention
Access and retention rules are configured for the customer's workflow and applicable obligations.
FAQ
Frequently asked questions
Key implementation and workflow questions for face comparison.
Configure your flow
See Face Comparison inside a DocinVault workflow
We will map the module to your customer journey, operating market, and review requirements.