Integrate liveness detection with ISO 30107-3 PAD compliance into an identity proofing flow

Steps

1. Select a liveness vendor that has obtained iBeta ISO 30107-3 PAD Level 1 or Level 2 certification; verify the certification letter is current (iBeta issues time-limited reports) before procurement.
2. Determine whether passive liveness (no user action, analyzes depth/texture/motion cues) or active liveness (user prompted to blink or turn head) fits your UX requirements; passive is preferred for low-friction flows.
3. Integrate the vendor's SDK or API into the selfie capture step of your identity proofing flow; pass the liveness check result alongside the biometric comparison result in your compliance audit log.
4. Record the vendor name, PAD level achieved, test date, and result in the identity proofing transaction record to support audit and NIST 800-63A-4 evidence documentation.
5. Establish a fallback path for liveness failures: allow a limited number of retries before routing to supervised (in-person or video) proofing rather than infinitely looping.
6. Review the vendor's spoofing attack taxonomy (print, replay, 3D mask) against your threat model to confirm PAD level covers the attack vectors relevant to your risk profile.