Hyperverge e-KYC

Applications
An application is the complete journey of an end user through a workflow supported by HyperVerge.

It is automatically created by HyperVerge everytime a user starts onboarding either on your app(through the SDK integration) or through an onboard link.

You can view & manage your applications in the applications tab of the dashboard

Application Lifecycle
Application Life Cycle

Understanding Application Statuses
An application can have one of the following 'statuses':

Started
The user has started with the application and is going through various steps of the workflow
Auto Approved
User's application has reached 'auto approved' state in the workflow
This ideally means, everything is fine with the application
Findout the when an application can reach this state by going through your workflow on the dashboard
Auto Declined
User's application has reached 'auto declined' state in the workflow
This ideally means, some flags were found while processing the application, due to which this user had to be declined
Findout the when an application can reach this state by going through your workflow on the dashboard
Needs Review
User's application has reached 'needs review' state in the workflow
This ideally means, the application requires manual intervention to decide whether it should be approved or declined
Findout the when an application can reach this state by going through your workflow on the dashboard
Manually Approved
When a review agent(from your organisation) manually approves the application
This is done by clicking on the 'approve' button corresponding to the application, on HyperVerge's dashboard
Manually Declined
When a review agent(from your organisation) manually declines the application
This is done by clicking on the 'decline' button corresponding to the applicaion, on HyperVerge's dashboard
User Cancelled
When a user drops off the flow by clicking on the 'X' icon in any of the SDK pages
Please note that if the user drops off by any other means (Eg: killing your app, deleting the app etc), the status would remain as 'started'
Error
When an unexpected error happens during the user journey
Please refer to SDK Errors page to learn more about this.
The Transaction ID
Every application is uniquely identified by an ID called 'Transaction ID'
This transaction ID is provided by you at the time of SDK initialisation or while creating an onboard link
A customer's application can be found on HyperVerge's dashboard or retrived from HyperVerge's backend(via Results API) by using the Transaction ID
It is recommended that, the transaction ID sent to HyperVerge is same as the customer's identifier(eg: userID, customer ID) that's stored in your system. This makes fetching of applications from HyperVerge easier
Common Questions
How to know when an application status has changed?
The Results Webhook is triggered everytime an application's status is changed - either on SDK/Onboard Links or through a review action on the dashboard

工作流程
什么是
工作流程是最终用户（及其应用程序）为了完成入门而经历的一系列步骤。

HyperVerge 提供了多种开箱即用的工作流程，针对跨地区的各种业务用例进行了优化。您可以使用这些工作流程之一，也可以自定义它们（无代码）以满足您的业务需求

要使用工作流程来加入您的客户，您可以集成我们的低代码SDK或直接与您的客户共享我们的加入链接，而无需编写任何代码

的一部分
样本工作流程

一般来说，工作流程由 3 个组件组成：

模块
模块是工作流程的构建块。

每个模块都有独特的功能（如“身份证验证”或“数据库检查”）。根据您的要求，可以使用适当的模块集以正确的顺序构建您的工作流程，以优化您的业务指标。

您可以在此处阅读有关模块的更多信息。

条件
条件用于根据某些规则对流程进行分支。它们本质上是引入到您的工作流程中的“if...else”场景。由条件创建的每个分支可以具有更多模块或以最终状态结束。

例子：

If“ID号可用”执行DB检查。else触发身份证验证模块
如果id_card_validation模块未检测到 ID 卡，则“自动拒绝”用户。否则继续selfie_validation
3.最终状态
工作流中的每个分支都应以结束状态结束。这些是auto approved或auto declined之一needs review。

如果应用程序达到其中任何状态，则应用程序的状态会相应更改。了解申请状态