Skip to main content

Selfie Verification

Introduction:#

When embedding financial services, fraud is an inherent risk that may cause financial losses. Reducing fraud may result in an inferior user experience and there is a real challenge in maintaining the same level of user experience while reducing the amount of fraud. Selfie Verification is considered an effective tool that enables to reduce fraud while maintaining a limited impact on the user experience.

Prerequisites:#

  • Approval from banking partner. Contact your Customer Success Manager to guide you through the approval process.
  • Public token to initialize Vouched SDK. Contact your Customer Success Manager to get the token.
  • Live integration with Vouched JS Plugin or mobile SDKs.

Flow description:#

  1. The ability to ask for Selfie Verification is slightly different depending on if the applicant is Individual or Business:

    • When the applicant is Individual, Selfie Verification will be done on the application level by adding the useSelfieVerification attribute to the application payload.
    • When the applicant is Business, Selfie Verification can be done for the Officer, any of the Beneficial Owners, or all of these related individuals (Officer and Beneficial Owners). You’ll have the flexibility to ask for Selfie Verification for any of these individuals by adding the useSelfieVerification attribute to these related individuals in the application payload.
  2. According to your business logic and per applicant, you’ll be able to decide between two options:

    1. Selfie Verification isn’t required

      • This is the default option. When the useSelfieVerification attribute  is NOT added to the application payload the useSelfieVerification will be set to Never. If needed, you can explicitly add useSelfieVerification = Never to the application payload to achieve the same result.
      • When evaluating the end-customer’s application where useSelfieVerification = Never, Unit will potentially ask for documents based on the evaluation results. If documents are required, you should expect the application’s response to include some documentType but NOT documentType = SelfieVerification.
    2. Replace ID Verification with Selfie Verification 

      • Add useSelfieVerification = ReplaceIdentification attribute to the application payload.
      • When useSelfieVerification = ReplaceIdentification, the evaluation will be done as usual and the only change that you’ll experience is that the requirement to provide ID Document is replaced with the requirement to perform Selfie Verification. When the result of the evaluation is “Selfie Verification Required” it will be included in the application response as a document with documentType = SelfieVerification.
  3. When “Selfie Verification Required”, application.awaitingDocuments webhook will be fired.

  4. Based on the application response and the webhook event, you’ll be able to take the End-Customer (or the Business’s officer or Beneficial Owner) through a selfie verification journey by initializing Vouched SDK using the public token.

  5. Once both the Selfie picture and ID picture are taken, Vouched will perform a job to process these inputs and respond with a result that will include a jobId.

  6. In order for Unit to evaluate the Selfie, you’ll need to call the POST Verify Document endpoint with Vouched jobId that was provided to you by Vouched as a result of the SDK operation.

  7. With Vouched jobId Unit will extract the Selfie data of your End-Customer (or the Business’s officer or Beneficial Owner) and will evaluate the results against predefined rules and thresholds in order to make a decision if the application is approved or denied.

  8. 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 (with Approved status) or Denied (with Denied status).

Integration guidelines#

  • Vouched is the supported vendor for Selfie Verification. In order for Unit to evaluate the application against the selfie verification results you’ll need to integrate with Vouched and embed the Vouched SDK into your web/mobile user interface.

  • With Vouched integration you’ll be able to support:

    • Web applications using Vouched JS Plugin.
    • Mobile applications using Vouched Mobile SDKs for iOS and Android devices. Helper guides for both SDKs can be provided upon request.
    note

    In order to receive Vouched's tokens and for any guidance throughout the integration process, contact your Customer Success Manager.

  • These are Vouched supported features (some of these features are configurable and allow you to customize and own the experience:

FeatureAdditional info
Facial recognition & MatchingDetects, verifies and analyzes a user’s face to match it with the photo on the user’s identity document.
ID Examination & Data ExtractionBy using OCR technology, data from the ID document is extracted and examined to it can used during the evaluation.
Liveness DetectionFour types of liveness gestures are supported:
  • Look straight ahead [straight]: the user takes a selfie and Vouched detects minor facial movements like blinking.
  • Look left, look right [orientation]: the user takes a selfie and moves their face left and right.
  • Open-close mouth [mouth]: the user takes a selfie and is asked to open and close their mouth.
  • Distance check [distance]: the user takes a selfie and is asked to move away and closer to the camera to detect distance.
  • Guided Photo CaptureUser is automatically guided with prompts such as "move closer", "move further", "there is glare on the ID", etc. You will be able to write your own instructions to better guide the user throughout the process until the Selfie and ID Document photos are taken.
    Auto CaptureThe photos will be automatically taken when the conditions are optimal. Because users will often try to take photos in poor conditions (e.g., a dark room) where conditions will never be suitable for a good photo, Vouched provide the ability to revert manual control to the user after a specific number of seconds, configured by you.
    White LabelingYou can change the logo, colors, and even the text to make sure it meets your needs and matches your brand.
    ID/Selfie Score ThresholdsScores are given across these three categories:
  • ID: Overall identity score of the ID
  • Selfie: Overall identity score of the selfie
  • Face Match: how the face match the ID
  • RetriesSettings for amount of time and number of attempts to capture the user’s ID and selfie images.

    Supported documents:#

    • Vouched can support a variety of document types in different geographies as described here, Unit only allows these combinations (when the combination is not supported, the application will be automatically denied):
    Document TypeUSNON-US
    IdentificationYESNO
    Drivers-licenseYESNO
    PassportNOYES
    • When end-customer has a US SSN the end-customer is considered a US Person and the supported documents are Drivers License or State ID so when in Vouched results “type”: “drivers-license” OR “type”: “identification” it will be supported on Unit’s side, otherwise the evaluation will fail and the application will go back to awaitingDocuments status so you’ll be able to send a new document.\ See below examples for happy and non-happy flows:

      • Happy flow:\ Individual application with SSN.\ AND\ Vouched result includes “type”: “drivers-license”\ → Evaluation is continued
      • Non happy flow:\ Individual application with SSN\ AND\ Vouched result includes “type”: “residence”\ → Evaluation is failed and application status goes to awaitingDocuments status
    • When end-customer has NO US SSN and a passport number is provided instead of SSN the end-customer is considered a Non-US Person and the supported documents are only Passport so when in Vouched results “type”: “passport” it will be supported on Unit’s side, otherwise the evaluation will fail and the application will go back to awaitingDocuments status so you’ll be able to send a new document.\ See below examples for happy and non-happy flows:

      • Happy flow:\ Individual application with no SSN\ AND\ Vouched result includes “type”: “passport”\ → Evaluation is continued
      • Non happy flow:\ Individual application with SSN\ AND\ Vouched result includes “type”: “drivers-license”\ → Evaluation is failed and application status goes to awaitingDocuments status