Verification Journey
A Verification Journey is another fundamental construct within the Exchange Application, representing a series of steps designed to collect and verify data and make decisions based on predefined business rules.
Each touchpoint in a user’s workflow can be mapped to a specific Verification Journey, ensuring that the right data is collected, validated, and verified as per business needs.
Verification Journeys integrates seamlessly with the Exchange Application by acting as discrete, configurable steps that can be tailored to specific verification needs. They can be invoked at any point in the exchange transaction, allowing businesses to perform targeted verifications as required.
A Verification Journey can be configured to handle a wide range of verification tasks, from verifying a single ID like PAN or Aadhaar to more complex touch points such as verifying a user's income from either bank account statements or using account aggregators.
How to create a Verification Journey
Currently, creating a verification journey requires assistance from your account manager. Please contact your account manager to specify the exact IDs and documents you wish to collect, verify, and validate from your users.
Executing Verification Journey
To execute a Verification Journey, businesses first need to start an Exchange Transaction. Once the exchange transaction is started, the verification journey can be executed.
The following are IDs that are accepted for executing the Verification Journey
| Name | ID | Mandatory or Optional | Description |
|---|---|---|---|
| Exchange Transaction ID | exchange_txn_id | Mandatory | This ID is useful to identify which exchange application. This ID is given by Equal after successfully starting the exchange transaction. |
| Journey ID | journey_id | Mandatory | A journey ID stores all the configuration details that you would want to be applied as part of verification. This ID will be shared by Equal and will be different for every verification journey |
| request_id | request_id | Optional | You can pass a request ID to uniquely identify each attempt of the verification journey separately. |
Along with the above identifiers, the business needs to pass the respective input params which will be separate for each Journey as per the business needs.
Reusing Data Across Verification Journeys
Since a Verification Journey exists within an Exchange Application, it can reuse data from previously executed verification journeys.
For instance, if a user’s Aadhaar has already been verified in an earlier verification journey, the system can automatically leverage this data for subsequent verifications. As an example, during a subsequent PAN verification journey, the business can automatically verify the linkage between the Aadhaar and the PAN, streamlining the process and reducing redundancy.
This addition emphasizes the efficiency and data reuse capabilities of the Verification Journey within the Exchange Application, enhancing the overall verification process.
Updated 3 months ago