The new FACEIO website brings together updated developer documentation, localized pages, accessibility guidance, and dedicated product pages for facial authentication, Meeting Shield, and ID Match.

For website owners and businesses, it makes the options easier to understand. For developers, it provides a clearer path from creating a FACEIO application to integrating the fio.js JavaScript library and connecting authentication results to an existing backend.

Updated Documentation, From Your First Integration to Production

The documentation follows the work developers need to do: create an application, configure it, integrate the widget, and handle the results.

Start with Getting Started, our guide to a 5-minute facial authentication integration. It walks through creating an application in the FACEIO Console, obtaining its Public ID, reviewing the security and privacy settings, and adding fio.js to your website or web app.

Then use the Integration Guide for method parameters, return values, error codes, and framework examples. It covers enroll() for registering new users, authenticate() for returning users, and session handling with restartSession().

The Developer Center connects these resources with the references you need as your implementation grows:

• Facial ID reference: understand the identifier returned after enrollment and how to associate it with your own user accounts.
• REST API reference: manage Facial IDs and use the documented backend endpoints while keeping private API keys on your server.
• Webhook documentation: receive enrollment, authentication, and Facial ID deletion events in your backend.
• Security best practices: review PIN Code validation, liveness settings, domain restrictions, and the controls needed around your login flow.
• Privacy best practices: plan notices, consent, retention, deletion, and recognition-engine deployment.

Already using FACEIO? Revisit these references before your next release, especially if you are adding webhooks, changing security settings, or updating account-deletion workflows.

Read FACEIO in Your Language

The website and developer documentation are now available in four localized versions alongside English:

• Português do Brasil
• Español de México
• Bahasa Indonesia
• 日本語

Use the language selectors in the header or footer to move between equivalent pages. Technical names such as fio.js, Facial ID, API methods, and error constants remain unchanged so they stay consistent with the code you write.

Website localization is separate from the embedded experience: the FACEIO widget supports more than 70 languages, helping teams provide enrollment and authentication flows for users in different markets.

Facial Authentication for Websites, Web Apps, and Corporate Portals

FACEIO facial authentication remains the core of the platform. It lets users enroll and authenticate through a browser widget, using the device's camera without requiring a native mobile app or a dedicated biometric sensor.

Developers load fio.js, initialize it with the application's Public ID, and connect enrollment and authentication to their existing interface. The library works with Vanilla JavaScript, React, Vue, Next.js, and other JavaScript stacks.

Your backend keeps control of accounts, sessions, recovery, and authorization. FACEIO does not store, handle, or access biometric hashes; the selected facial recognition engine manages them. The updated documentation explains these responsibilities and the available cloud and PixLab Insight on-premises deployment options.

Meeting Shield: Video Risk Signals for Business Meetings

FACEIO Meeting Shield is a Chrome extension for supported Google Meet, Zoom Web, and Microsoft Teams Web sessions.

It analyzes visible meeting video and reports suspicious signals associated with deepfakes, synthetic video, replayed footage, and manipulated facial motion. Its local-first analysis is designed to avoid uploading raw meeting video.

Meeting Shield is intended for situations such as remote interviews, executive calls, financial consultations, and customer meetings. It gives teams additional information to review before sharing sensitive information or making a decision. These signals support the organization's verification process; they do not establish a participant's identity or guarantee that every manipulated video will be detected.

Visit the product page to review how the extension works and request access through the FACEIO Console.

ID Match: Compare a Live Selfie with an ID Portrait

FACEIO ID Match brings a guided selfie-to-ID comparison into your website or web app.

It uses the same application setup and fio.js integration pattern as facial authentication. Calling idmatch() opens a popup that captures a live selfie and an ID document, performs a liveness check, and compares the selfie with the portrait extracted from the document. Your application can also request selected document fields.

Document scanning, portrait extraction, and optional field extraction are powered by PixLab DOCSCAN. Submitted images and processing data are handled in RAM and deleted immediately after the result is ready or the session fails. The processing pipeline retains no submitted images, document data, or scan logs.

ID Match compares the two faces. It does not authenticate the document, perform KYC or AML checks, or decide whether to approve a user. Your application determines how to use the returned result and any requested fields.

Accessibility Is Part of the Integration

The updated website also explains the FACEIO widget's accessibility features: visual and audio instructions, keyboard navigation, and screen-reader support with compatible browsers and assistive technologies.

These features help guide users through enrollment and authentication. Before release, test the complete experience within your own website or web app and provide another way to access an account for users who cannot or do not want to use facial authentication.

Start with the New Guides

Whether you are adding passwordless face login to a customer website, integrating facial authentication into a corporate portal, or exploring Meeting Shield and ID Match, start with the product pages and updated documentation.

Open the FACEIO Console to create an application and obtain its Public ID, then follow the Getting Started guide to integrate fio.js.

For explanations and implementation articles, explore the FACEIO Knowledge Center. For public technical questions, join the FACEIO Community Forum.

Liveness detection is a critical component in biometric security systems, ensuring that the face being scanned is from a live person rather than a photograph, video, or mask. FACEIO, a leader in facial authentication technology, addresses these challenges with its advanced AI models. This blog post explores how FACEIO resolves liveness detection issues, leveraging sophisticated algorithms and security practices.

What is Liveness Detection?

Liveness detection is a security feature used in facial recognition systems to verify that the scanned face is from a live individual. It prevents spoofing attacks by detecting natural facial movements and responses. Various techniques employed in liveness detection include:

• Motion Analysis: Detects natural movements such as blinking and head movements.
• Texture Analysis: Differentiates between the texture of live skin and that of a photograph or screen.
• Challenge-Response: Prompts the user to perform actions like blinking or smiling to prove liveness.

Implementing Liveness Detection with FACEIO

FACEIO provides an easy-to-integrate solution for facial authentication with built-in liveness detection. Here is a step-by-step guide to activate liveness detection on your FACEIO Application:

1. Setting Up FACEIO:

   • Sign up and create an account on the FACEIO Console.

2. Integrating FACEIO SDK:

   • Add the fio.js JavaScript SDK to your project by creating an application first on the FACEIO Console, and follow the integration guide using your favorite JavaScript framework whether it is React, Next, Vue, Svelte or React-Native.

3. Initializing FACEIO:

   • Initialize a new fio.js object instance in your JavaScript code with your Application Public ID as follows: javascript const faceio = new faceIO("your-application-pub-id");

4. Implementing Liveness Detection:

   • Activate Face Anti-Spoofing first by connecting to the FACEIO Console, then Navigate to the SECURITY tab from the manager main view. Once the target application selected. Activate the Protect Against Deep-Fakes & Face Spoof Attempts security option as shown below:

     async function performLivenessCheck() {
      try {
          const response = await faceio.authenticate({ action: "liveness-check" });
          if (response.livenessScore > 0.9) {
              console.log("User authenticated successfully");
          } else {
              console.warn("Liveness check failed");
          }
      } catch (error) {
          console.error("Liveness check failed", error);
      }
     }
     

Advanced Security Features of FACEIO

FACEIO's commitment to security extends beyond basic liveness detection. Here are some of the advanced features that enhance its security:

• Multifactor Authentication (MFA): Combine facial recognition with other authentication methods for added security.
• Customizable User Prompts: Tailor instructions and prompts shown to users during the liveness check.
• Analytics and Reporting: Access detailed reports on authentication attempts to monitor and improve system performance.

Best Practices for Secure Implementation

FACEIO provides several security best practices to ensure robust protection against spoofing and other security threats:

• Reject Weak PIN Codes: Ensure users create strong PIN codes during enrollment.
• Prevent Duplicate Enrollment: Avoid multiple enrollments by the same user.
• Protect Against Deepfakes: Use liveness detection to counteract spoofing attempts.
• Forbid Minors: Prevent minors from enrolling in the application.
• Always Ask for PIN Code: Require PIN code confirmation during authentication for added security.
• Enforce PIN Code Uniqueness: Ensure each user's PIN code is unique.
• Ignore Obscured Faces: Reject partially masked or poorly lit faces.
• Reject Missing HTTP Headers: Prevent requests without proper origin or referer headers.
• Restrict Domain and Country: Limit widget instantiation to specific domains and countries.
• Enable Webhooks: Use webhooks for real-time updates on user interactions.

Conclusion

Integrating FACEIO for liveness detection and facial authentication in JavaScript significantly enhances digital security. Its robust API and user-friendly JavaScript library make it easy for developers to implement biometric authentication, preventing spoofing and unauthorized access. FACEIO's advanced features and best practices ensure both security and user experience are prioritized, making it a valuable addition to any web application's defense against modern threats.

For more information, visit the FACEIO website.

---

Published in: Level Up Coding

The FACEIO development team is pleased to announce the immediate availability of our Liveness Detection, Presentation Attacks Mitigation (PAD) & Face Anti-Spoofing Security Option. A highly requested feature by our customers that is now deployed & fully operational on FACEIO thanks to a PixLab implementation.

Liveness detection in biometrics is the ability for a system to detect if the target face is real from a live person present at the point of capture or fake from a spoof artifact or lifeless body part.

Face Anti-Spoofing on the other side, is the task of preventing false facial authentication when implementing fio.js, our facial recognition library on your web site or application using a smartphone picture, or printed image for an authorized person's face.

Face Anti-Spoofing Security Option

With this security option enabled, Smartphone & Print Attacks originating from a static image or video stream are easily deterred during Authentication & Enrollment when enabled for your FACEIO application.

The Face Anti-Spoofing Security Option is immediately available to trigger from the Application Manager (Security Tab) on the FACEIO Console.

Press Release & Model Roadmap

Our Press Release document including a general overview of the approach used to implement Face Anti-Spoofing for FACEIO is available to consult at: cdn.faceio.net/faceio_liveness_detection.pdf.

This implementation & further model enhancements, are pushed transparently, and no action or code changes are required on your side. Just an option to trigger from the Application Manager on the FACEIO CONSOLE.

Implementation Overview

Once a new user enroll or authenticate on your application, the Face Anti-Spoof engine shall be triggered to filter out spoof & presentation attacks. Upon an attack is detected, the fioErrCode.PAD_ATTACK error code is raised, and you should act accordingly such as banning the acting user depending on your policy.

Please note that Face Anti-Spoofing mitigation is a resource intensive operation, therefore it is available starting from the Business Plan, and up. Nevertheless, it takes less than 600 milliseconds to execute thanks to a heavily optimized implementation.