Hi Support Team,
We are using your product for an international event registration and access control system. After our experience, we identified two friction points that we need your assistance for:
PIN Requirement: Many attendees forget the security PIN they created during remote pre-enrollment. This causes significant delays at the event entrance.
Request: Is there a way to programmatically set a default PIN for all users, or completely disable the PIN requirement for our application ID? We need the facial match to be the sole credential.
Request: Does the current SDK allow us to enforce stricter "Liveness" or quality filters during the enroll() call? We want to ensure that the biometric template captured remotely is high-quality enough for professional scanning hardware.
Process Control: We need more granular control over the workflow. Is there a "Manager Mode" or an API configuration that allows us to override a failed face match if we manually verify the ID?
We are looking for the best technical approach to minimize friction at the entrance. If these features require a plan upgrade or a specific configuration on your backend, please let us know.
Best regards,
Resolving FACEIO PIN and Enrollment Issues for Trade Fair Access
✓ Accepted Solution
Hello,
Thank you for reaching out, and welcome to the FACEIO support center. To answer your inquiry:
-
PIN requirement and reducing entrance friction
You can relax the PIN confirmation during authentication directly from the Application Manager in the FACEIO Console by disabling the PIN fallback option for your application. This usually helps reduce friction for large public events such as trade fairs.
That said, if the facial match confidence drops below a minimum safety threshold, the PIN may still be prompted even when disabled. This is an intentional security safeguard and helps protect both your organizers and attendees from spoofing attempts, poor lighting captures, or borderline matches.
For events like yours, a practical approach is to minimize remote PIN reliance and keep supervised re-enrollment or assisted verification available at the entrance for edge cases. -
Enrollment quality control and remote capture reliability
The enroll() process already performs multiple-frame capture and internal quality checks to build a stable biometric template. This process generally compensates for typical variations in camera quality, lighting, and angles, so you are already reasonably protected.
If you want additional robustness for the 2026 event, upgrading to the Business Plan allows activation of enhanced deepfake detection and face anti-spoof protection from the Application Manager. This adds extra validation during both enrollment and authentication.
Operationally, many event organizers also complement remote enrollment with controlled on-site capture stations to ensure consistent template quality for high-throughput gates. -
Process control, overrides, and administrative workflows
There is no native “manager override accept” button in the standard authentication flow. Any manual override workflow should be handled at your application level, typically by verifying ID visually and triggering a supervised re-enrollment if needed.
You can also programmatically manage your application using the FACEIO REST API documented here:
https://faceio.net/rest-api
Through the API you can delete facial IDs upon request, update payload metadata, reset or change PINs, and manage enrollment data to support your operational workflows.
Additional note on upcoming improvements
We are introducing enhancements where multiple faces may be present during authentication. The engine will automatically select the front-facing subject and ignore background faces, which should further reduce friction at busy entrances such as trade fairs.
Plan considerations
If you anticipate large attendance volumes, stricter anti-spoofing, or more customized operational control, a Business Plan upgrade or an enterprise/on-premises configuration may provide the additional flexibility needed. Feel free to share expected attendee numbers and peak entry throughput so we can guide you more precisely.
Do let us know if you need further assistance,
Regards;
