Compare a Live Face With a Trusted Reference
Compare a live browser capture with an ID portrait, customer record, or other trusted reference image. Use the result in onboarding, account recovery, and sensitive-action workflows. For backend-only image comparison, see the online face verification API.
Connect to the FACEIO Console to create applications, manage APIs, and configure webhooks for enrollment, authentication, and Facial ID events.
Face Verification vs. Authentication: Understanding the Difference
They solve different problems. Getting the distinction right is critical for compliance, security, and user experience.
Authentication matches a returning user against an enrolled face index. Face verification compares a live capture with a separate reference image and returns technical match signals. Your backend decides how those signals affect onboarding, recovery, or access. For authentication-specific architecture, see biometric authentication for web apps.
Authentication
"Is this the person who enrolled?"
Works by matching a live capture against the application's enrolled face index through the configured facial recognition engine. Your app receives a Facial ID and authentication result, not raw face material. See face recognition login flows and the Facial ID reference.
Verification
"Does this person match a reference I trust?"
You are comparing a live face with external evidence, such as a government-issued ID photograph, customer record, or previously reviewed profile image. The match result does not authenticate the document or establish legal identity. API details are in the face verification API.
Compliance Context: A face-match result can be one signal in a customer-managed KYC ↗ workflow. FACEIO does not authenticate documents, perform KYC or AML checks, or determine compliance. Use the Developer Guides for implementation details and Privacy Best Practices.
How the Verification Flow Works
An online face verification flow runs in three distinct stages. All three stages complete directly within the browser, with no native app installation, plugin, or specialized hardware required.
1 Capture
The user allows camera access. FACEIO captures a live facial image via the browser. This real-time input, not an uploaded photo, is what makes liveness detection possible.
2 Verify
The live capture is matched against your system's reference image (e.g., an ID scan). FACEIO returns a similarity score and a precise boolean match result.
3 Decision
Based on the result, your backend proceeds with onboarding, permits the action, or routes to manual review. The identity signal comes from FACEIO, but the decision logic stays with you.
Verification media is processed in memory and removed after the result is generated. Your application remains responsible for its own retention policy, consent records, and audit trail. For request and response schemas, consult the Developer Guides.
Fraud Threats You Must Defend Against
Identity verification pages are attractive targets, especially when a basic camera check is the only control between an attacker and account access.
Online identity verification is a common target. Attackers try to bypass KYC checks, create fraudulent accounts, or recover access to accounts they do not own. The three most common attack vectors are:
Replay Attacks
A previously captured image or video of the real applicant is played back to the camera instead of a live capture. Without liveness detection, systems cannot distinguish the difference.
Screen Presentation
A photograph or video of the target is displayed on a secondary screen held in front of the camera. The visual quality easily defeats naive matching systems.
Deepfakes & AI
AI-generated video that mimics a real person's appearance is injected into a virtual camera feed. This is the fastest-evolving threat vector today.
Each attack exploits the same gap: a verification system that matches faces without checking that the capture is live and physically present.
The FACEIO Approach
FACEIO evaluates three parts of a browser-based verification flow: live-presence indicators, presentation-attack indicators, and the face comparison. These are technical signals for your backend policy, not a guarantee that every spoofing attempt will be detected.
1. Active Liveness Detection
Evaluates whether the input shows live-presence indicators during the request and helps identify photographs, pre-recorded videos, and static images before matching.
2. Anti-Spoofing Signals
Analyzes the media feed for presentation attacks, synthetic content, and virtual camera abuse used to impersonate another person during the capture step.
3. Face Match Verification
Once liveness and authenticity are checked, the live capture is compared against the reference image. FACEIO returns match signals that your backend can use with the confidence threshold required for your workflow.
For security architecture details and threat model documentation, review Security Best Practices, Privacy Best Practices, and the Trust Center.
Where Verification Fits in Your Workflows
Online face verification fits workflows that need a live face compared with a separate reference image rather than an enrolled returning-user index. Common deployment contexts include:
-
User Onboarding and KYC
Compare a live selfie with the portrait on an ID during account creation. This result can be one signal in your onboarding, AML, or KYC workflow, while your application remains responsible for document authenticity and identity decisions. See fintech and eKYC solution guidance or use ID Match when you need document scanning and selfie matching in one widget.
-
Account Recovery
Compare a fresh capture with the reference image held for the account. Your backend can use the match result with device, session, recovery, and support controls before deciding whether to restore access.
-
Sensitive Action Gating
Request a fresh face comparison before selected actions such as fund transfers, beneficiary additions, or access to sensitive records. Your backend remains responsible for authorization and any additional checks.
Conclusion: Online face verification provides live capture, liveness checks, and face-match results for onboarding, recovery, and sensitive actions. FACEIO performs the requested comparison; your backend interprets the result and makes the final decision.
Implementation resources
Build Online Face Verification Workflows
Add online face verification to onboarding, account recovery, and sensitive actions with a browser-based flow. Use the docs below to create an app, connect the SDK, validate results, and monitor verification events.
Build a Browser Verification Flow
Create a FACEIO app, review the integration guide, and connect browser-based face verification to your onboarding, recovery, or sensitive action workflow. Your backend keeps final control over the decision.