Jesús Aragón | CEO & Co-Founder
Identy.io
Digital identity is quickly becoming the foundation for how people prove who they are — not just at a border, but across banking, government services, healthcare, and everyday digital life. As more of these interactions move to mobile-first, remote enrollment, the industry has gotten good at solving the pieces in isolation: capturing a face, capturing a fingerprint, validating a document. But the moment that actually determines whether a digital identity can be trusted is the one nobody talks about enough — proving that all of those pieces belong to the same person, securely, remotely, and without friction. Most identity programs today rely on document validation and facial biometrics, which work reasonably well from a smartphone. The harder problem is fingerprint capture, and binding it to the face in a manner that isn’t awkward for the user, time-consuming, or dependent on costly hardware. Mobile touchless remote fingerprint capture changes that equation. But it introduces a challenge the industry hasn’t fully addressed: how do you guarantee that the fingerprint captured remotely actually belongs to the person whose face and documents you just verified? This is the “binding” problem — and it’s the difference between a genuinely secure enrollment model and a vulnerability waiting to be exploited. Identy.io’s biometric binding architecture links face capture, document OCR, and touchless fingerprint collection into a single authenticated session. The face is real — independently validated in DHS’s RIVR evaluation with zero attack acceptance across all attack classes. The fingerprints are real — ISO/IEC 30107-3 Level 2 certified by Idiap Research Institute and Ingenium Biometrics. And they belong to each other, verifiably. Further, they are interoperable with legacy AFIS databases and watchlists, without requiring hardware replacement. No rip-and-replace. No new kiosks.
Appearances:
Identity Week America - Day 2 @ 11:30
Remote mobile enrollment: Secure face and fingerprint binding
Digital identity is quickly becoming the foundation for how people prove who they are — not just at a border, but across banking, government services, healthcare, and everyday digital life. As more of these interactions move to mobile-first, remote enrollment, the industry has gotten good at solving the pieces in isolation: capturing a face, capturing a fingerprint, validating a document. But the moment that actually determines whether a digital identity can be trusted is the one nobody talks about enough — proving that all of those pieces belong to the same person, securely, remotely, and without friction.
Most identity programs today rely on document validation and facial biometrics, which work reasonably well from a smartphone. The harder problem is fingerprint capture, and binding it to the face in a manner that isn’t awkward for the user, time-consuming, or dependent on costly hardware. Mobile touchless remote fingerprint capture changes that equation. But it introduces a challenge the industry hasn’t fully addressed: how do you guarantee that the fingerprint captured remotely actually belongs to the person whose face and documents you just verified? This is the “binding” problem — and it’s the difference between a genuinely secure enrollment model and a vulnerability waiting to be exploited.
Identy.io’s biometric binding architecture links face capture, document OCR, and touchless fingerprint collection into a single authenticated session. The face is real — independently validated in DHS’s RIVR evaluation with zero attack acceptance across all attack classes. The fingerprints are real — ISO/IEC 30107-3 Level 2 certified by Idiap Research Institute and Ingenium Biometrics. And they belong to each other, verifiably. Further, they are interoperable with legacy AFIS databases and watchlists, without requiring hardware replacement. No rip-and-replace. No new kiosks.
GET INVOLVED AT IDENTITY WEEK AMERICA
Created by
Terrapinn is proud to be a member of isla.
Working together to build sustainable events