Skip to main content
Custom BuildsReady-to-Launch
Sandbox

Selfie Verification

Introduction:​

The integration of financial services carries the risk of fraud and resulting financial losses. While various fraud prevention measures exist, they often struggle to balance the need for fraud risk mitigation with maintaining a positive user experience. To address this challenge, Unit has implemented Selfie Identity Verification.

Selfie verification is a automated method for verifying identity and authenticating a photo ID. The process is integrated into the customer application process, during which, the user is prompted to take a selfie which is then compared in real-time to the provided ID document to confirm that the user's identity matches the one on the document. This technique provides effective fraud prevention while minimizing impact on the user experience.

Application Steps:​

  1. Obtain approval from banking partner - Contact your Customer Success manager to guide you through the approval process.

  2. Embed the document collection component in your onboarding experience

Flow description:​

  1. Set the value of the useSelfieVerification evaluation parameter of the application:
  • If the applicant is an individual, the selfie verification setting is done on the application level by adding the useSelfieVerification attribute to the Create Application
  • When the applicant is Business, Selfie Verification can be done either for the Officer, any of the Beneficial Owners, or both. You’ll have the flexibility to ask for Selfie Verification for any of these individuals by adding the useSelfieVerification attribute to these entities in the Create Application

Possible Values:

  • Never - This is the default value. When the useSelfieVerification attribute is NOT added to the application request the value, Selfie Verification will never be required by default. If needed, you can add this attribute and set it to Never to achieve the same result.
  • Replace Identification - The requirement to provide an ID Document will be replaced with the requirement to perform a Selfie Verification. When the value is set to ReplaceIdentification and an ID document is required, a document of type SelfieVerification will be included in the response (instead of document type of IdDocument).

  1. An application.awaitingDocuments webhook will be fired.

  2. Initialize the Document collection component: The Customer (or the Business’s officer or Beneficial Owner) should now be taken through a selfie verification process using the component.

  3. Once both the Selfie picture and ID picture are taken, the component will process the inputs and return a response back to Unit. Unit will then to evaluate the Selfie, in order to make a decision if the application is approved or denied. In some cases the application will need to be manually reviewed in order to make a decision. In these cases you should expect the application to be in PendingReview status until a decision is made and the application is Approved or Denied.

Integration guidelines​

See Document collection for more details on how to embed the component in your onboarding experience.