Selfie Reverification

What is Selfie Reverification?

Selfie Reverification enables organizations to reverify users who have already completed a successful Document Verification process. Instead of requiring a user to reupload their identity documents, the system captures a new selfie and compares it to the headshot from the previously accepted DocV transaction.

This ensures that the returning user is the same person who originally passed identity checks—while maintaining a fast, low-friction experience. Selfie Reverification includes liveness detection, injection attack protection, and Digital Intelligence signals, providing strong safeguards against impersonation and synthetic media.

How it works

• Selfie capture only: The user captures a fresh selfie using the Capture App or SDKs.
• Biometric & liveness validation: Ensures the selfie was captured live and not spoofed.
• Selfie-to-headshot comparison: Compares the new selfie to the headshot from the user’s previously accepted Document Verification.
• Fraud monitoring: Device integrity and Digital Intelligence help detect unusual or risky activity.
• Decisioning: Returns Accept / Reject / Resubmit / Review with reason codes for operational routing.
• Global coverage: Available in 180+ countries worldwide.

Verification checks

Selfie Reverification applies the following checks to each captured selfie:

Prerequisites

Selfie Reverification requires a previous_reference_id — the referenceId from a prior accepted Document Verification evaluation. Without this, the API returns an error because there is no baseline headshot to compare against.

Consumer flow

The following diagram shows the screens a consumer sees during the Selfie Reverification flow in the Capture App:

Retake

Submit

Terms & Consent

Selfie Capture

Selfie Preview

Confirmation Screen

1. Terms & Consent — A mandatory notice and consent screen. This screen can't be removed, customized, or disabled.
2. Selfie Capture — The consumer captures a live selfie using the device's front-facing camera. If auto-capture is enabled, the system automatically takes the selfie when the face is properly positioned.
3. Selfie Preview — The consumer reviews the captured selfie and confirms it is clear, or retakes the photo.
4. Confirmation Screen — Confirms the selfie submission was successful.

What you can do with Selfie Reverification

• Reconfirm identity without requiring document resubmission.
• Protect high-risk actions such as transfers, withdrawals, and profile changes.
• Support account recovery during lockouts or lost-credential flows.
• Perform periodic reverification for compliance or trust & safety requirements.
• Strengthen fraud detection when behavior, device, or context looks suspicious.

Unique features

• Selfie-only reverification flow: No document upload required for returning users.
• 1:1 biometric comparison: Matches the new selfie against the previously approved DocV headshot.
• Liveness detection: Confirms real user presence.
• Digital Intelligence: Device and behavioral insights for additional risk assessment.
• Injection & deepfake detection: Identifies synthetic or manipulated media.
• Reason-coded decisions: Clear routing for accept, reject, resubmit, or review outcomes.

Integration options

Integrate with the Predictive Document Verification SDKs to embed the Capture App into your mobile application, then verify a consumer’s identity by calling the Evaluation endpoint.

The Capture App provides a guided, mobile-optimized workflow for capturing IDs, selfies, and supporting documents.

• iOS SDK — Integrate the iOS SDK into your native mobile application.
• Android SDK — Integrate the Android SDK into your native mobile application.
• React Native — Cross-platform bridge built on the iOS and Android SDKs.
• Web SDK — Launch Capture App flows from desktop or mobile browsers.

Example response

The following is an example of the selfieReverification object returned from the Evaluation endpoint:

{
  "selfieReverification": {
    "previousReferenceId": "738508b3-0dee-4302-ba8f-ba90b454ba",
    "decision": {
      "strategy": "standard",
      "value": "accept"
    },
    "reasonCodes": [
      "I834"
    ],
    "digitalIntelligence": {
      "decision": {
        "strategy": "standard",
        "value": "accept"
      },
      "reasonCodes": [
        "I401"
      ]
    }
  }
}