For the complete documentation index, see llms.txt. This page is also available as Markdown.

IDV Suite Platform Integrations

Once the flow has been designed in Facephi IDV Suite, the next step is to decide how to expose it to the end user. To do this, the platform offers two main integration approaches:

  • No-code integrations

  • Low-code integrations (web and mobile)

This section provides an overview of both, and the following sections will cover each in detail.


What is a no-code integration?

A no-code integration is the fastest and easiest way to put a flow into production without having to develop your own application.

At a high level:

IDV Suite generates a ready-to-use experience (for example, accessible via a link) that runs the configured flow and is managed by the platform.

Key features:

  • Minimal development by the client to address security considerations.

  • Enables pilots, POCs, or simple projects to be launched very quickly.

  • Ideal when:

    • The client has not yet defined all its digital channels.

    • You want to validate the process for onboarding/authentication before integrating it more deeply.

    • A quick solution is needed for a specific use case (campaign, temporary form, alternative channel, etc.).


What is a low-code integration?

Low-code integrations are designed for when the client wants or needs to integrate IDV Suite into its own digital channels, without having to build all the onboarding/authentication logic from scratch.

At a high level:

The flow continues to be orchestrated and governed from IDV Suite, but the experience is delivered through the client's website or mobile app, using SDKs.

Within low-code, we distinguish two broad categories:

  • Low-code Web / Mobile

    • Integrate the flow into an existing web application or portal.

    • This allows users to experience the process as a natural part of the client's website or mobile application.

    • The SDK handles biometric/document capture and communication with the platform, using the integration's Integration ID .

    • It allows for a high degree of control over the UX, leveraging the device’s native capabilities.


When to Use No-Code vs. Low-Code

Although both options are based on the same flow concept, they address different needs:

Typical No-Code Use Cases

  • Situations where the client team does not have immediate development capacity.

  • Rapid POCs and pilots, where the priority is to test the process, rather than fully integrate with the client’s systems.

  • Use cases with little reliance on custom UX.

Typical Low-Code Use Cases (Web / SDK Mobile)

  • Projects where the verification flow must be integrated natively into the client’s website or app.

  • Need for finer control over the user experience (navigation, design, behavior).

  • Deep integrations with internal systems (core, CRM, signatures, etc.), where it makes sense for the client’s own channel to centralize user interactions.


What All Integrations Have in Common

Regardless of whether no-code or low-code is chosen, all integrations in IDV Suite share the following:

  • They are based on a defined and published flow.

  • They generate operations that are managed through the Operations Module.

  • They can notify you of results using webhooks or equivalent mechanisms.

  • They benefit from the same cross-platform capabilities:

    • Security, auditing, compliance, scalability, etc.


Integration Lifecycle

  1. Create integration

    • Choose between no-code and low-code

  2. Flow selection

    • Add the flows created previously

  3. Define the look and feel

    • Configure the color palette that defines your company.

  4. Configure webhooks

    • Define the URL where events will be received

    • Key-value pair and required password (or another authentication method)

    • Select the events you want to receive information about

  5. Final touches

    • Select the default language

    • For mobile, you must include the bundle ID or app name.

    • For web, the origin URLs from which the integration will be launched will be included.

  6. Publish the integration

    • Wait for it to be published while the license is being generated. The support team will email you the license.

Last updated