4 Modules

Verification Modules

Modular verification components that adapt to your specific requirements. Enable only what you need.

Module System

okID's verification process is built on a flexible module system. Each module handles a specific aspect of identity verification and can be enabled or disabled based on your requirements.

How it works

  • 1.When generating a verification, the backend determines which modules are required
  • 2.The verification flow guides users through each required module in order
  • 3.Each module validates its data independently
  • 4.Final validation happens after all modules are completed

Available Modules

Terms & Conditions

Legal agreements and consent

Optional

Present terms of service, privacy policies, or other legal documents that users must accept before proceeding with verification.

GDPR Compliant
Custom Terms
Multi-language

Document Verification

ID card, passport, or driver's license

Core Module

Capture and verify government-issued identity documents. Supports automatic document type detection, OCR data extraction, and authenticity checks.

OCR Extraction
MRZ Reading
Anti-forgery

Liveness Detection

Face matching and anti-spoofing

Core Module

Verify that the person is physically present during verification. Uses advanced face detection, liveness checks, and biometric matching against the document photo.

Face Matching
3D Liveness
Anti-spoofing

Form Data Collection

Additional user information

Optional

Collect additional information from users through customizable forms. Perfect for compliance requirements, KYC processes, or gathering business-specific data.

Custom Fields
Validation Rules
Dynamic Forms

Module Configuration

Modules are configured at the organization level through the admin dashboard or API. The verification flow automatically adapts based on enabled modules.

// Example verification response showing module configuration
{
  "verificationId": "abc-123",
  "modules": {
    "terms": { 
      "required": true,
      "version": "2024-01-15"
    },
    "document": { 
      "required": true,
      "supportedTypes": ["passport", "id_card", "drivers_license"]
    },
    "liveness": { 
      "required": true,
      "confidenceThreshold": 0.95
    },
    "form_data": { 
      "required": false 
    }
  },
  "flow": ["terms", "document", "liveness"]
}

Best Practices

Start with core modules

Document and Liveness modules provide the foundation for identity verification

Add modules progressively

Start simple and add modules as your compliance requirements grow

Consider user experience

More modules mean longer verification times - balance security with convenience

Test your flow

Always test the complete verification flow from the user's perspective