KYC document capture
Read and validate passports, driver’s licenses, and ID cards during account opening with OCR and MRZ parsing.
Banks, lenders, and payment providers verify identity at account opening and re-verify it at high-risk moments – wire transfers, limit increases, password resets. FacePlugin runs that verification layer entirely on your own infrastructure, so biometric templates and ID document images never leave your data center or private cloud.
Read and validate passports, driver’s licenses, and ID cards during account opening with OCR and MRZ parsing.
Confirm the person opening the account matches the photo on their ID with 1:1 face verification.
Block printed photos, replayed video, and masks during remote onboarding or video KYC.
Financial institutions operate under some of the strictest data-residency, audit, and vendor-risk requirements of any industry, and many banking regulators expect institutions to know exactly where customer data is processed and stored. Running identity verification on a third-party cloud API adds a vendor and a data flow that has to be reviewed, audited, and justified every time regulations change.
FacePlugin's SDKs remove that dependency: face recognition, liveness detection, and ID document recognition all run on servers, private cloud, or devices your institution already controls. You license the software once and keep every face template, document image, and match decision inside your own environment – the verification logic becomes part of your infrastructure instead of a recurring API call to someone else's.
Combine these SDKs — licensed once, run on infrastructure you control — to fit your existing workflow.
Read and validate passports, driver’s licenses, and ID cards during account opening with OCR and MRZ parsing.
Confirm the person opening the account matches the photo on their ID with 1:1 face verification.
Block printed photos, replayed video, and masks during remote onboarding or video KYC.
Flag AI-generated or manipulated faces before synthetic-identity fraud reaches account opening.
Require a fresh face-and-liveness check before high-risk actions like wire transfers or limit changes.
Run on your own data center, VPC, or air-gapped environment to satisfy data-residency requirements.
Verify a new customer’s identity against their ID document during remote onboarding, without a branch visit.
Add a step-up face-and-liveness check before releasing a large or unusual transaction.
Confirm a caller’s identity before discussing account details or processing a change request.
Verify the enrolled user’s identity before approving a password reset or access-recovery request.
No. FacePlugin provides the identity-verification and biometric layer – face recognition, liveness detection, and ID document recognition – that financial institutions typically combine with their own AML, KYC, and sanctions-screening systems. It doesn’t check watchlists or perform transaction monitoring.
FacePlugin can replace the identity-verification and biometric-matching components of a KYC stack specifically. Document-data extraction, liveness, and face matching run on your infrastructure instead of a vendor's cloud; your compliance team still owns the overall KYC policy and any screening steps around it.
FacePlugin doesn’t process or store your customers’ data on its own servers – the SDKs run inside your infrastructure, so the data never leaves an environment you already control and audit. Your institution’s existing compliance program covers that environment; FacePlugin isn’t a separate data processor in the flow.
Yes. The server SDK runs on Linux via Docker or a local Python install with no required outbound network call once licensed, which is why it fits air-gapped and VPC-restricted banking environments.
Talk to our team about your compliance requirements and infrastructure — we’ll point you to the right SDK combination.