Tip of the day

Support tickets can be submitted directly from application


Estimated reading: 4 minutes 196 views

Why would I want to use this?

When interacting with remote client our commitments are:

  1. Produce engaging data collection processes where data can be collected and validated inline and through interaction with secured APIs
  2. Provide you with the tool set to manage a risk of a remote client identity

While we require a client mediation to drive a business cycle forward to completion, we are also looking at a remote client identity as a potential risk that needs to be managed.

Questions such as: Who is (s)he? Do we hold accurate email, phone numbers data that correspond to his/her identity at all? All these are legitimate questions that needs an answer, specially when business cycle is involved with confidential information or processes with high risk profiles such as health, insurance, human resources, purchase, statutory, legal activities etc.

For that purpose Cellosign platform already encapsulates powerful instruments to follow this through. Modules such as OTP, Challenge questions, validating against data injected into the process and more that can be folded into business processes with a click of a button, and we encourage you to use them.

CIV module is an important addition to our fraud-management capabilities in order to provide you the assurance and means for authenticating and carry out corrective actions in regards to your client identity.

How does it work?

Once CIV module is enabled on a project settings you will be able to integrate a CIV flow into a template.

In template editor drag a CIV element into the form

Now we need to select and set up the verification process.

We already have built-up set of designated flows to speed up the process. Simply select the required components of the CIV process.

First, select Identification document applicable for the process:

  1. ID
  2. Driving License
  3. Passport

Choosing one Identification document would require solely that specific document . However, choosing more than one will require one document OR the other.

Alternatively you may configure the form with more than a one CIV process that can be triggered according to a client selection or data injected, for example if a client selects in the form that he/she has a foreign residency than a verification process with Passport only can be activated, or in case of a local residence, ID or driving license CIV process can be activated.

Second, select if the process requires a “Liveness” test. This to make sure our client is a real person. This process will require a client to interact with a mobile device that will capture live gestures and authenticate this a real person rather than an image.

Third, select if the a bio-metric test should be activated. This test compares our client image from the Identification  document and compare it with the image captured in Liveness test.

Note that bio-metric comparison can only occur if at least one document and Liveness test are selected. Configuring CIV as illustrated above will trigger a CIV process that will require image above will trigger ID, Liveness test and bio-metric comparison.

CIV process produce a comprehensive data-sets that can be incorporated  into the form logic:

  1. Test result success or failure, for each of the tests
  2. Data set for each of the tests, for example name, address and image collected from each document
  3. Score on bio-metric test, this number, between 0 to 1 will provide an assurance on how we are sure this is the same person. results over 0.7 is “pretty sure”, below 0.7 will require human intervention

This data sets can be easily be configured into workflows and incorporated into forms in order to govern the process continuity.

Failed CIV processes will be documented in Audit dashboard. However we strongly recommend to build CIV enabled processes with BPM or Workflow in order to enable timely intervention of an Agent or back-office that will be able to re-validate the client authenticity in case of indecisive results.

For security reasons we encourage you to limit the inclusion of data-set into the form for the minimum required.

For the same reason, data extracted from the documents which are not incorporated in a form will be archived solely with API and will not be sent in mail to agent nor the client.

How CIV interaction feels like?

This is CIV process that combines ID check, Liveness and Bio-metric comparison. The bio-metric test does not require client intervention and it occurs in background.

Feel free to drop us questions, email us to: service@cellosign.com

Leave a Comment

Share this Doc


Or copy link