Online service registration
For organizations that need to review an applicant's identity information before activating an account or providing a service.
Digital identity · Verify individual identity
Identity VerificationKnow your users. Start services with greater confidence.
When a service depends on knowing who a user is, onboarding information needs a clear review process. Liyan connects authenticity checks and identity data matching with your organization's workflows to support more structured user acceptance decisions.
The verification flow is defined around your service, risk level and available data sources.
From information to a decisionA conceptual verification workflow
Collect information
The inputs and documents needed for onboarding
Review and match
Compare against trusted sources and business rules
Review outcome
Continue the workflow or refer for further review
Identity Verification · Digital identity · Verify individual identity
Enterprise use cases
Where does identity review matter?
Assess the solution wherever knowing a user's identity is part of accepting a request or delivering a service.
Customer and partner onboarding
For workflows where reviewing personal information and documents is part of accepting an application or starting a relationship.
Service access requests
For flows that require identity review before granting access. Access permissions remain subject to your organization's policies.
Core capabilities
Identity checks within your workflow
Create a clear identity review stage with defined inputs, understandable rules and an outcome your systems can use.
Information and document checks
Information and documents submitted during registration form the basis for reviewing a person’s identity. The outcome supports user acceptance or the continuation of a service.
For a clearer view of submitted informationIdentity data matching
Review inconsistencies between submitted information and reference data. The reference sources must be available and approved for your organization.
For decisions based on consistent informationOnboarding and service integration
Use the identity review outcome in registration or service delivery. Define continuation, information correction and human review around your acceptance rules.
For coordination with existing systemsThoughtful workflow design
Clarify these points before deployment
A dependable workflow needs clear operating rules. Discuss these topics during requirements analysis and solution design.
Required data and access
Which information does your service need, and who may view it? Define retention periods and deletion processes around your organization's policies.
Sources and connections
Which data sources are available and can be connected? Review dependencies, access requirements and workflow behavior when a connection is unavailable.
Acceptance and human review
Which outcomes allow the user to continue, and who reviews uncertain cases? Walk through acceptance, non-approval and correction scenarios before launch.
Identity verification FAQs
What does Liyan Identity Verification do?
The system reviews information and document authenticity and matches identity data. The outcome is used in registration or service delivery. Account sign-in and access permissions are separate topics.
Is identity verification the same as account sign-in?
On this page, verification refers to reviewing a person's identity during onboarding or a service request. Account sign-in and access permissions are related areas whose requirements and connections are reviewed separately.
Can it connect to our existing system?
Integration with existing workflows is a core area of the solution. Feasibility and connection methods are determined after reviewing your systems, available interfaces and data exchange requirements.
Which documents and sources are supported?
Required documents depend on your service. Before starting, confirm the supported document list, available reference sources and the method used for each check. Accepting a document does not imply support for every possible authenticity check.
What happens with incomplete or inconsistent information?
These outcomes are defined during workflow design. Your policies may call for corrections, human review or pausing the workflow until an outcome is established.
How are pricing and deployment timing determined?
Cost and timing depend on the scope of checks, required integrations and usage volume. Share your requirements with Liyan to discuss implementation and commercial terms after reviewing the scenario.
Getting started
From a real scenario to a suitable solution
Start with an example of your current onboarding or acceptance process to clarify requirements, integration points and decision criteria.
Describe your workflow
Share your service, users, required documents and the challenges in your current process with Liyan.
Review the scenario and connections
Discuss review stages, data sources, existing systems and how you will use the outcome during the demo and technical review.
Define the implementation scope
Once requirements are clear, discuss the capabilities needed, deployment, support, timing and cost.
Where should your identity verification journey start?
Introduce your service and current workflow to discuss identity review and how it can connect with your systems.