KYC providers integration

KYC providers integration (integration of identity verification services, Know Your Customer) is the connection of a verification engine (Sumsub, Onfido, IDnow and others) to your site or app. The client uploads a document and takes a selfie with a liveness check (proof the person is real and present); the service confirms the document’s authenticity and the face match, and, if needed, screens against AML, sanctions and politically exposed persons lists. It suits regulated areas: fintech, crypto, lending, betting, marketplaces. We set up the verification flow, statuses and passing of the result to your system. Importantly and honestly, and this is the main point: we are technical integrators, not compliance and not lawyers. Whether you are obliged to do KYC at all, at what level, which checks and how long to store the data — that is decided by your compliance officer or lawyer, not us and not the service itself. The engine verifies, but the result is probabilistic and risk-based: false accepts and false rejects happen, no KYC gives 100%, and the final decision whether to let a client in and the responsibility for onboarding stay with you. This is sensitive personal and biometric data (a document, a face): under Russia’s federal data-protection law 152-FZ, biometrics are a special category with requirements for consent, storage and cross-border transfer, while in the EU it is GDPR; where the service physically stores the data and whether localization in Russia is required is critical — check with a lawyer before launch. The service is paid, usually per verification — costs grow with volume. And honestly about conversion: KYC is a barrier, it filters out some users; if the law does not require verification in your case, adding it “just in case” harms conversion. We will suggest the technical options and their cost, but whether KYC is required and at what level is a decision for your compliance or lawyer, not our advice. Also honestly: after launch you and your compliance configure the KYC policy itself (decision thresholds, what to do on a rejection, retention periods) — we advise on the technical side but do not make the policy for you. Picture this: a new client in a fintech service uploads a passport and takes a selfie — within a minute the service confirms the identity and screens against sanctions lists, while you get a ready result and decide by your own rules. The base price starts from 50,000 ₽; it depends on the service, the set of checks and your platform; a complex or multi-platform integration costs more, and the legal and compliance side you work through separately.

• The law requires verifying clients’ identity, but you do it manually and slowly.
• You do not know how to embed document upload and face checking into the site.
• You are afraid of letting through a fraudster or a person on a sanctions list.
• It is unclear how to store passports and biometrics without breaking the law.

• Connecting a KYC service (Sumsub / Onfido / IDnow and others)
• A document upload and selfie flow with a liveness check
• Verification of the document’s authenticity and the face match
• Screening against AML, sanctions and PEP lists (if needed)
• Passing the verification result to your system
• Highlighting the data requirements (152-FZ / GDPR, localization)
• Selection of technical options (whether KYC is required is your compliance’s zone)
• Documentation and (by agreement) support

• Identity verification runs automatically in your flow
• The document’s authenticity and the face match are visible
• Clients are screened against sanctions and AML lists
• It is clear where the tech ends and the lawyer’s and compliance zone begins

• We clarify with you (and your compliance) the verification level and requirements
• We connect the verification flow, the checks and passing of the result
• We test on test verifications, launch and support the start

• Will you take on compliance and the decision whether to admit a client?

  No. We are technical integrators: we connect a service that checks the document and the face and collects the result. Whether you must do KYC, at what level and which checks — that is decided by your compliance or lawyer. The final decision on the client and the responsibility for onboarding stay with you; the service’s result is probabilistic, not a verdict.

• Is it legal in terms of storing passports and biometrics?

  It depends on the setup and the jurisdiction — that is a legal question. A document and a face are sensitive data; under Russia’s federal data-protection law 152-FZ, biometrics are a special category with their own requirements for consent and storage, while in the EU it is GDPR. It matters where the service physically stores the data and whether localization in Russia is required. We will connect it technically, but check the legal side with a lawyer before launch — we will not close it for you.

• Do we really need KYC?

  Not always. If you are in a regulated area (fintech, crypto, lending, betting) — probably yes, but the level is determined by your compliance. If the law does not require verification specifically for you, adding it “just in case” is not worth it: KYC is a barrier that reduces conversion. We will help you compare the technical options, but whether KYC is required is determined by your compliance — that is not our legal advice, and we will not push anything unnecessary.