Skip to main content

Verification Process

Overview​

The onboarding flow can be composed by a single step or multiple steps. Any onboarding flow contains at least one Identity Verification step (IDV) such as a Document Verification or a login with eID. Typically, a complete identity verification flow includes both a Document Verification step (to scan and validate the identity document) and a Liveness Verification step (to ensure the person is real and matches the document). All critical operations such as document scanning and liveness checks are always performed on our platform through a secure HTTPS connection. That way we can add a first layer of security ensuring that the acquisition is performed properly, reducing the risk of deep fake.

The platform provides two distinct methods to integrate with your app:

Each onboarding flow is associated with a unique public web link that can be shared with the users. Once they click on it, they are redirected to a designated flow on our platform. In this setup, users must authenticate via email by manually entering their email address, clicking the link sent to their inbox, and completing the flow.

It involves the following steps:

  • The user clicks a button on your website containing the link to the proper verification flow on the Zyphe Platform
  • The user is redirected to the Zyphe platform
  • The user authenticate on the Zyphe platform with his email
  • The user performs any verification step directly on the Zyphe platform
  • Zyphe notify your backend about the verification result via the Webhook and make the result accessible within the dashboard

Here, you can find a video that demonstrates integration and identity verification using the public web link:

View on Youtube

SDK​

The SDK integration supports 2 different approaches:

Using the nodejs SDK it's possible to dynamically generate the verification session together with a link that redirects to our platform to complete the verification.

Embed into your web app​

Using the browser SDK it's possible to embed the verification flow directly into your application through an iframe.

info

The browser integration is done through an iframe to ensure that the javascript that is executed is not manipulated and the communication between the SDK and the backend is properly authenticated.