RURequest a demo

The verkyc platform

One platform to verify people and companies

Documents, the NFC chip, the face, the company, sanctions lists and monitoring work within one case. Every check returns its own result with a reason, and your policy makes the decision.

Request a demoAPI documentation

How a verification is built

A case ties together the applicant, the purpose, the country and the policy version. Individual checks run inside the case.

  1. Data collection

    The applicant completes the steps via a link, an embedded widget or your app with the SDK. The server issues the steps according to the case policy.

  2. Checks

    The document, chip, face, registries and lists are checked independently. Each check has its own outcome, reasons, algorithm or source version and time.

  3. Decision

    The decision policy combines the outcomes: approval only when required checks pass, everything else goes to manual review or a request for more data.

  4. Report

    A signed report lists the checks performed and not performed. Anyone can verify the report by its reference without sharing personal data.

Six outcomes instead of yes or no

A missing result is never treated as a positive one. Every check ends with one of six outcomes:

  • pass: the check ran and the condition was confirmed within the source;
  • fail: the check ran and the condition was not confirmed;
  • inconclusive: not enough data to conclude, for example an unreadable image after the allowed retries;
  • not_supported: the document type or country is outside the coverage profile;
  • unavailable: the source or engine is temporarily unavailable;
  • not_performed: the check did not run, with the reason stated.

See it on your own scenarios

Tell us who you need to verify and where. We will prepare a demo, test API access and a price estimate.

Request a demoRead the docs