# Make identity verification part of your customer experience.

> Add document and identity checks to your onboarding flow. Review the scope, user steps and integration of Legichain Digital KYC.

Canonical URL: https://legichain.com/en/digital-kyc
Language: en
Other language: https://legichain.com/digital-kyc

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

- [Book a demo](https://legichain.com/en/contact?topic=demo)
- [Discuss document and device coverage](https://legichain.com/en/contact?topic=integration)

_Interactive example (synthetic screens): document capture → chip read (NFC) → person check (liveness and face matching) → result; a field that cannot be verified automatically is passed to the team as a finding that needs review._

## Every step has a purpose.

- **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
- **Person check** — Apply the face and liveness checks the flow requires.
  - Input: Short camera interaction
  - Output: Liveness result and document-match indicator
- **Result assessment** — Review the check output together with the application record.
  - Input: Step results and application reference
  - Output: Completed automatically or review required

## 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.

- [Discuss document and device coverage](https://legichain.com/en/contact?topic=integration)
- **Country** — Document and field coverage varies by country
- **Document type** — ID card, passport and chip support
- **Operating system and version** — Camera and NFC capabilities
- **NFC availability** — Device, document and browser capability are checked together
- **Alternative flow** — Defined retry or review path in unsupported cases

## 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.

_Three sample error screens (synthetic): insufficient quality → retry; device without NFC support → alternative flow; field that cannot be verified automatically → review path._

## 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.

1. **Digital KYC** — Document and person check result
2. **Application record** — Read fields, step states
3. **AML screening** — Separate request; candidate records and source
4. **Findings** — Each step's own output
5. **Review** — Team decision and rationale

## 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.

- [Book a demo](https://legichain.com/en/contact?topic=demo)

---
Legichain — technology for identity verification, AML and blockchain screening. Contact: contact@legichain.com