How shushi0209/video-kyc works
Video KYC is a browser-assisted identity-verification product: an applicant enters a case ID, completes a recorded session with face/liveness checks, questions, and document capture, then evidence can be reviewed and approved or retried. The frontend API client and backend routers connect these stages to persistent workflow state and media storage. Several routes and frontend details are documented by module names and contracts rather than sampled call sites, so those links are omitted where ownership cannot be established.
Main entry points: api.py Session API · main.py Application server · database.py Relational database · api_evidence.py Evidence and review API
Components 16
Applicant experience
- Case entry
frontend/src/App.tsx - Session experience
frontend/src/VideoKyc.tsx - API client
frontend/src/api.ts - Liveness interface
frontend/src/providers/LivenessProvider.ts - Browser liveness
frontend/src/providers/BrowserLivenessProvider.ts
Verification workflow
- Session API
backend/api.py - Question API
backend/api_questions.py - Document API
backend/api_documents.py
Evidence and review
- Evidence and review API
backend/api_evidence.py
Runtime platform
- API schemas
backend/schemas.py - Workflow records
backend/models.py - Relational database
backend/core/database.py - Media storage
backend/core/storage.py - Configuration
backend/core/config.py - Application server
backend/main.py
Other components
- Applicant
Connections 23
- Applicant → Case entry: enters case
frontend/src/App.tsx - Case entry → Session experience: opens session
frontend/src/App.tsx - Session experience → API client: requests workflow
frontend/src/VideoKyc.tsx - Session experience → Liveness interface: uses provider
frontend/src/VideoKyc.tsx - Browser liveness → Liveness interface: implements
frontend/src/providers/BrowserLivenessProvider.ts - Application server → Session API: mounts routes
backend/main.py - Application server → Question API: mounts routes
backend/main.py - Application server → Document API: mounts routes
backend/main.py - Application server → Evidence and review API: mounts routes
backend/main.py - Session API → Workflow records: reads and writes
backend/api.py - Session API → Relational database: queries state
backend/api.py - Session API → Media storage: stores recording
backend/api.py - Question API → Workflow records: reads and writes
backend/api_questions.py - Question API → Relational database: queries state
backend/api_questions.py - Document API → Workflow records: reads and writes
backend/api_documents.py - Document API → Relational database: queries state
backend/api_documents.py - Evidence and review API → Session API: uses workflow helpers
backend/api_evidence.py - Evidence and review API → Workflow records: reads and updates
backend/api_evidence.py - Evidence and review API → Relational database: queries state
backend/api_evidence.py - API client → Application server: calls HTTP API
- Session API → API schemas: validates responses
backend/api.py - Configuration → Relational database: configures connection
backend/core/database.py - Media storage → Configuration: reads storage root
backend/core/storage.py