Product · Digital KYC

Make identity verification part of your customer experience.

Add document and identity check steps to your digital application flow. Guide users with clear instructions; pass results that need review to your team.

User journey · 4 steps Sample data

Select a step; the screen the user sees at that moment appears on the right.

  1. The document is framed; MRZ and visual fields are read. If quality is insufficient the user retries.

  2. On a supported document and device, chip data is read via NFC and checked for consistency with the document.

  3. A liveness check and face matching against the document photo are applied.

  4. Automatically completed and review-required cases are separated; the team receives a reviewable record.

09:41Legichain KYC
Step 1/4 · Document

Place your ID document in the frame

Keep the whole document visible; avoid glare and shadow. The back side is requested after the front.

Screens are synthetic; they contain no real ID number or photo. A success screen is shown only when the real check has completed.

Steps

Every step has a purpose.

  • 01

    Document data

    Capture the details on the identity document with the supported method.

    Input
    Document image, chip data where available
    Output
    Read fields and consistency check
  • 02

    Person check

    Apply the face and liveness checks the flow requires.

    Input
    Short camera interaction
    Output
    Liveness result and document-match indicator
  • 03

    Result assessment

    Review the check output together with the application record.

    Input
    Step results and application reference
    Output
    Completed automatically or review required

Coverage

Plan document and device coverage in advance.

Country, document type, operating system and NFC availability affect the flow. Do not leave users on a vague error screen in unsupported cases; define the alternative process and retry conditions.

  • CountryDocument and field coverage varies by country
  • Document typeID card, passport and chip support
  • Operating system and versionCamera and NFC capabilities
  • NFC availabilityDevice, document and browser capability are checked together
  • Alternative flowDefined retry or review path in unsupported cases

Recovery flows

Error moments are part of the experience too.

Technical limitation, quality issue and review need are not reduced to the same message. Each case has its own explanation and next step.

Clear instruction

State what is expected from the user.

Controlled retry

Explain the reason for the failed step safely and clearly.

Review path

Route applications that cannot be completed automatically to the institution's process.

09:42Step 1/4

Insufficient quality

Document could not be read

Glare detected. Place the document on a flat surface, move away from the light source and capture again.

Quality issue: reason + retry
09:43Step 2/4

Not supported

Chip reading is unavailable on this device

The device or document does not support NFC reading. You can continue with the alternative flow defined by your institution.

Device incompatibility: alternative process
09:47Step 4/4

Review required

Your application is under review

One field could not be verified automatically. No further action is needed; the outcome is communicated through the institution's process.

Review path: routed to the team

Separate steps, separate outputs

From identity check to risk assessment.

Design the identity check and AML screening as steps with separate purposes. Keep it explicit in your integration which step produces which data and result.

Digital KYCDocument and person check result
Application recordRead fields, step states
AML screeningSeparate request; candidate records and source
FindingsEach step's own output
ReviewTeam decision and rationale

Discuss integration requirements

Frequently asked questions

About Digital KYC.

Is every identity document supported?

Support depends on document and country coverage. Do not finalise the user flow before evaluating the current list.

Is NFC mandatory?

The available method depends on the document, the device and your institution's process requirements. Define the supported flow in the coverage discussion.

Does a liveness check verify identity on its own?

A liveness check is one component of the identity verification flow. It does not replace other checks such as document and person matching.

Let's define the flow that fits your needs.

Let's discuss your document, device and process coverage and clarify the user flow together.