eKYC архитектура для банка

Зачем банку платформа eKYC

Onboarding, periodic refresh, sensitive transaction step-up, partner verification — все требуют identity verification. Без unified capability — каждый flow свой стек.

eKYC platform — reusable, callable из multiple scenarios.

Структурные компоненты

Document capture с UX guidance, quality detection.

Document validation. OCR + structural (форма, holograms, MRZ). Fraud detection.

Biometric capture. Selfie с ML models для local population.

Face matching. Selfie ↔ document.

Liveness detection. Active или passive — anti-spoof.

Registry checks. ОМС, sanctions, blacklists, PEP.

Risk scoring. Combined score → decision: pass / step-up / decline.

Audit trail. Full evidence chain per verification.

Reuse layer. Existing identity reusable для new product activation.

Banking-specific concerns

Regulatory. cbu.uz биометрические требования с апреля 2026 — обязательно.

KYC level differentiation. Basic vs enhanced — разные thresholds.

Beneficial ownership для корпоративных. Multi-step KYC.

PEP screening — ongoing, не one-time.

Suitability assessment — для investment products.

Где обычно ломается

Multi-vendor stack без unified accountability.

OCR работает на 80% документов, manual queue растёт.

Liveness устарела — deepfake проходит.

Registry API нестабильны — eKYC останавливается.

Reuse не реализован — повторный KYC frustrate customers.

Operating model

Owner — Head of Identity / Head of Trust.

Teams: platform engineering, identity science, compliance, partnership integration.

Routine — monthly pass/fail/step-up rates, fraud incidents review.

Связанное

• /solutions/banking-digital-onboarding-platform/ — onboarding solution
• /insights/banking-biometrics-april-2026/ — biometrics
• /architecture/banking-realtime-decisioning/ — decisioning
• /expertise/banking-identity-trust/ — identity expertise