Incode Technologies is positioning a new iBeta certification as proof that its face liveness stack can withstand the kinds of presentation attacks enterprises are increasingly worried about in the age of generative AI. The company says its Deepsight platform passed iBeta Quality Assurance’s Level 3 Presentation Attack Detection (PAD) evaluation on both iOS and Android, with zero errors across 900 Level 3 attacks.
iBeta’s confirmation letter lists Incode Technologies’ Deepsight v1.0 as having achieved Level 3 under ISO/IEC 30107-3, with certification dated February 16, 2026. Level 3 is the most demanding tier in iBeta’s publicly available PAD program and is intended to represent advanced spoofing scenarios that can include high-quality replays and synthetic media techniques.
The dual-platform point is central to the company’s claim. Mobile ID World readers will recognize why that matters: enterprise onboarding flows often need consistent performance across iOS and Android devices, and liveness systems that are strong on one platform but brittle on the other can create policy and risk gaps. Incode’s announcement asserts that both mobile platforms were evaluated at the top tier with no successful attacks.
Incode is framing the result as a response to rising deepfake-enabled impersonation pressure. In a note accompanying the announcement, the company said independent biometric validation is becoming more important as spoofing becomes cheaper and more scalable. Founder and CEO Ricardo Amper summarized the message bluntly: “Proof is becoming more important than claims.”
iBeta’s public list of ISO 30107-3 confirmation letters shows multiple vendors pursuing Level 3 results. In January, Yoti’s MyFace passive liveness was listed as having met Level 3. Incode’s announcement differentiates itself by claiming the first Level 3 pass on both iOS and Android at a zero percent error rate, and by emphasizing that the underlying test included 900 Level 3 attacks.
The certification also intersects with government procurement credibility. Incode has previously pursued federal readiness milestones and holds identity proofing contracts that depend on strong anti-spoofing controls. The iBeta letter provides a third-party artifact that procurement teams can reference, rather than relying solely on vendor-reported performance claims.
Sources: iBeta, iBeta Confirmation Letter (PDF), Incode
–
By the Mobile ID World Editorial Team
