enc_U2FsdGVkX1/usnr0ethRy+nWGd7fd9mlCiSZ3JFFqQqh7Lol8BWLOZaDiPrNXUvfyF9MdMrh953ksdFUwH2fA4vwx3OOOAj49GvixOEH7B3UOm1Si1ZgrOBfRxUDFkYgFHesn0l38lsn3yyAjlSPhbUVKgIX8ywKhYCWJgzhEfWHqdgE9N56wVz67durCxkZJ3oEGEcu7SGxKqrLcuZDyKAFDDDF3mEXdUipxoZyjHybDbSuBIDvH8c4CiyPSnfxh30Ku6am2s3xk/7VbiYRy4boOIo6Saz8GBYPPxE++YKGen+CHQ6J4gAV0oEd4ayKRVWwk1yD8BdBgKRwLWFiexsaoPscKEr91wH631KmBlKxB6MhoyaXLPi3cmwB0oajSiToTnYSdMN2S2klM45+O4PZ8Rkai5Loj5TR4I1ztIpFGXZooa19n4hIp19dqbx6hyVMbOxmNiQv1Fa7Ex8EP93uij4q4WJctLh4xDfW+TmmO/mQ7/6wtT61MOs4fIaYetJoJZjWwWKf7WvFcw9iBkO2NLe8uzglyEaH5jZoY3RRmsgK7EAH+dKTMEjgGr/v_enc

Before launching the onboarding session, our client’s customer needs to provide some preliminary information (first name, last name, birth date, email and phone number) for further verification during the session. Any scenario then contains a list of questions (depending on the client requirements) of the following kind:

  • Identity verification: an identity document needs to be scanned and will be analyzed via authenticity controls and will return a score
  • Face match: if available, the identity document face will be compared to the video onboarding face and scored. Additional controls are done to detect abnormal face emotions or person of interest (PEP, SIP, …).
  • Data verification and information request: the answer will be compared to known information or to pre-defined list of accepted answers.
  • Document upload: a document (proof of address for example) needs to be uploaded from our client’s customer device or a picture of the document needs to be taken using the camera.
  • Antibot verification: our client’s customer needs to read numbers that appear on the screen, to make sure he/she is not a robot.

enc_U2FsdGVkX1+LY7T1to9jNuFEQG2SoCKUjYrYpXu8UmTbf67NlviPuDy7ZOBCKxV2eKIvWpMPVRrILEZW5X9eAB5zj88GQK66UTGYuBBmNiboAxPcer2cQCT6CtJstws0E1X42kHxgklOccqMuw1yPmsCEGOuGAW8MRybnA2D7olSulnl4nYGZYjpXiVJvvNw_enc

enc_U2FsdGVkX1+Y6xVlXOr9cLXYdCz6b3aYEscu3FbrlSNB7s1VRgy4Ca/VL6hgQYCllAMu8MV8TeS10Mf+4gn08ACikZSx7Lhjo/qdyuBy7x8fPOi7DJMMKwrWkjOa8Nn5QoYZr3s1DQmkOqVJXfDZQRTskWTNkF+kJHm/WFwzVCoihx0CuLYjjzz3uTLx3WEjYxDnZz3VW2s0yIqNr8bPMA==_enc

enc_U2FsdGVkX1/pMclKwk99hRyiS8Zg/QEw+ghZ03lnSHwGXHfh6+I4Q36FthAS8X0SsyNGo9p9f1W/OfHUh+k3zI027LhtzU7uJq+80NpWduPZW6K7PB7hXNW4dSlj24W08KBRCQWt6Jwtzb2vYfitxG2A2rSLPY54X0ATmpzZxO+9KklyqxZ3J53WgpuJkUwWeJj5DsZFOHcEb9LZWfXrAdESqLp0+Uw9Dc8zg8UCac1ulMuIY6NQa4gK1Ssfr+v/lgh5unoJVDRHXuocMY0mCiyOE4xYRj9nL0eLzsf0fgBw4RHHyE4wZWZT1+s7TTzJAILi/DbQZCXq0EfoUIon5CajvCrG+tjKZylq7YbPpZz91TFXS8BeKbDIrNqy9719S1AlUKyOBs7kUNlXCLaz62lIJYziRfPVQzoxCrd3Zol9Q4Hz17IX3lkKpavYiO3WRQkfBC8h/ZFyC2HGUKL17A==_enc

The Go!Vid frame is fully web based and responsive. It can be attached to a mobile app or a desktop website for instance. Only camera and audio accesses need to be enabled. Texts and colors can be customized to match our client’s brand and onboarding process.

​
enc_U2FsdGVkX1/YAz00BP5Gi1p8AgnVxZ66YuqL1TawbZevkEu8Xx1NumkE7lLM9AgA_enc

As mentionned above, each finished session is given a score that is computed depending on the scenario configuration.

Go!Vid also provides a set of features to review sessions and define their status using labels. These labels can be automatically or manually set.

In the following document the merchant will be the integrator of the solution.

​
enc_U2FsdGVkX18DQBI2BTPq9ofsoqV5fUjJlbWCC4YBSKU=_enc

​
enc_U2FsdGVkX18XtJYz74/ssTaj6/3Sb/IbPqvyNw2gOBg=_enc

Any scenario is configured with:

  • a list of available labels to set once a session ends. Each of these labels can be used by Go!Vid automatically at the end of a session or only manually.
  • a session score threshold to determine if the session state is negative, positive or neutral.

Once the score of the session is computed (see next section about “scoring sessions”) we use the session score threshold configuration to decide if the session state is negative (red), positive (green) or neutral (orange).

enc_U2FsdGVkX1+HlxF1WmUyqGX8LoLiDpmYmQgzcIrt2u3qjr9p9j7QWlGWTf26qgryRsVRjLyc3DYo6jPQVzX7R67F3yCvMUS3ZJ3sf3/g0eAobOAK32G7zBYDSJPxcFecPMQIyIKXwl7KtU13GSe6quYewyeJMXzRmVyT0I/myQxVJHW2q5sv2DEHPOUD2SQ7BIhydxlXsdEAFdb+E18+77BxMzPZjzu0LdbYDhVlZfsbfnfG8dz4BZw0w2tn72Iw6tWVxhuU2HYEZfHjUpulyl2VCjfm/HQlngFzpM2t/+WlCfaT+3LCZDEXYES4mgUT_enc

enc_U2FsdGVkX1+H0KPt0dBym1X7eQx1/Uze+bWX/IEdFQdA0djEYbAQErLlxjvUiCsNj05lY85HrSoOfNcwJbyHcy/KGyjho7JSE7OggDR3jA796OltZL4ufBfNgwru5t0d_enc

enc_U2FsdGVkX197WamSnAKybcmGV88S3Lis63P8STjZZvpBki4B+E7BXb+DHWy8pWbAMuHnCQR5kNi+1zklxX1MGDOUzmJhlEwEahUbqMKwkCMOhOq2aNlC77Uo028Z8YIc_enc

​
enc_U2FsdGVkX1+p8C0e34cH027hhOxGLtI6VwClpecb03w=_enc

Let’s use this set of labels:

In this example, the algorithm is allowed to set three labels by itself: “NOPASS”, “PENDING” and “PASS_PENDING”. But only a human agent can give the final approbation for the “PASS” label.

​
enc_U2FsdGVkX1/MYpUWSQKQyqwrOXBSXMxrlUMslntr1QAXIHDtAS/Pp8Uy8SZMtSrF_enc

enc_U2FsdGVkX19+mnpXY/UrfLLR/aDOoIRKLG52vEJATMTXCGB5YJcgmKW/fuvW6wf+wV5q7ClFmBB+34sB1omCCYaXJlG/VMC1UU3uvMbzSBY=_enc

enc_U2FsdGVkX198hFj/BXcArJQ2xajcWRWpqklxpoVz1e4ztrzuLDooqZb2wwzsNtL6HyuJXJDNXx+5ppi2POeU1winDwC8kYbjn4UJqLZ1qipuAonqE4+UX5tqdEAyWjlGae0Uk5Q/bb6kcqwlEDPXGmD2XuiRvC9jGx7tS94PPOEvdMmdkHuIODt4cqqAtjLSvi2wXXQunO+qbIUYVBJ/XDm7idXFAHedLNmRV5zjYzTZh/zVcZ+qPay6rdR1D37Bppz5GCC+OD4no8WJgfapt4aLt5l6fxYonTv7Gncj6v21jrOXVXv3LN6SBU48EpqInCv5iA1YFni97mFTnVw1jq5dUTEYVY7ZS+VTxtfeCTE=_enc

Note: The label can be updated automatically by the robot, or after some delay it can be updated by a human agent, see previous section about labels.

Note: To determine if a customer session was successful or not, the session final label should be used preferably over the score itself.

You can read our integration documentation here.

​
enc_U2FsdGVkX1/8xJaDohUyr8sQIRYJIb1+IFLVmxmFSFgvXfGllyU1QbsC2xFjt9JO_enc

enc_U2FsdGVkX18S5cBSCPf8gCvwejRl/m0UiRLwhGSwtntbXT6ro25TUL7qcQuBKhNsaUXE5NtGy6+arwH5EtFkyGvN/6wKLOHQeX87LReHOWZgHEu43Rb7td9IgN6oULy7K2IIsNVR7ugX2CDoWStWMmKkT/4qpMcsjXhK9+P3zlfcOEp3eHH0OP4PNpQdRPoetOfL5thYX/e9k3uCfO3+3rLBfPMWuheACnSrudvPlExiJuU5zbiZX0JxcM3NcUC0bRam90EHsG3ZN29EP0tFytSbItiLy1Hb5J2SrNNXmWttbBhruZLPuBzcDp5VU7Im_enc

Depending on the onboarding scenario, you must provide the customer information for the link generation. This information includes: first name, last name, birth date, nationality, address, and phone number. You can also add additional custom data.

​
enc_U2FsdGVkX18Xxps7naz0hI0zEWPmosBdpAe8eexHU3XDhSWRc/Wd5WiM5T4TkYpI_enc

In this schema, we emphasis that the label change can come from an automatic scoring or a human verification depending on your setup. As described in the labels section, multiple labels can be defined for each of the categories “POSITIVE”, “NEUTRAL” and “NEGATIVE” (here represented by “Pass”, “Pending” and “Fail”).

WatchlistsScoring