> For the complete documentation index, see [llms.txt](https://docs.facephi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.facephi.com/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code.md).

# 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.**\
For that, the platform offers two main Integration approaches:

* **No-code Integrations**
* **Low-code Integrations** (web and mobile)

This section provides a **general overview** of both, and in the following points we will go into detail on each one.

***

#### **What is a no-code Integration?**

An Integration **no-code** is the fastest and simplest way to put a Flow into production without needing 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.

Key features:

* **Development** minimal effort on the client's side to cover security aspects.
* It allows you to launch **pilots, POCs, or simple projects** in a very short time.
* Ideal when:
  * The client has not yet defined all of their digital channels.
  * You want to **validate the process** of 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?

Integrations **low-code** are intended for when the client wants or needs to **integrate IDV Suite into their own digital channels**, but without having to build all the Onboarding/authentication logic from scratch.

At a high level:

The Flow is still **orchestrated and governed from IDV Suite**, but the experience is consumed from the **web** or the **client's mobile app**, through SDKs.

Within low-code, we distinguish two main families:

* **Low-code Web / Mobile**
  * Integrate the Flow into an existing web application or portal.
  * It allows the user to perceive the process as a natural part of the client's web or mobile application.
  * The SDK takes care of biometric/document capture and communication with the platform, using the **Integration ID** of the Integration.
  * It allows a high degree of **control over the UX**, taking advantage of 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 in which the client team **does not have immediate development capacity**.
* POCs and quick pilots, where what matters is **testing the process**, rather than the full Integration with the client's systems.
* Use cases with **little dependence on custom UX.**

**Typical Low-Code use cases (Web / SDK Mobile)**

* Projects in which the verification Flow must be integrated in a **native way into the client's web or app.**
* Need for a **finer control over the user experience** (navigation, design, behavior).
* Deep Integrations with internal systems (Core, CRM, signing, etc.), where it makes sense for the client's own channel to centralize interaction with the user.

***

#### What all Integrations share

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

* They are based on a **defined and published Flow.**
* They generate **operations** that are managed from the [**Operations Module**](https://github.com/facephi/facephi-gitbook-docs/tree/master/docs/productos/idv-suite/modulos-manual-de-usuario/operaciones/README.md).
* They can **notify results** using [**webhooks**](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/webhook.md) or equivalent mechanisms.
* They benefit from the same cross-cutting platform capabilities:
  * Security, auditing, compliance, scalability, etc.

***

#### Integration lifecycle

1. **Create Integration**
   * Select between no-code or low-code
2. **Flow selection**
   * Add the [Flows](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/que-es-un-flujo-de-onboarding-autenticacion.md) created previously
3. **Define the look\&feel**
   * Configure the color palette that defines your company.
4. **Configure the webhooks**
   * Define the URL where the events will be received
   * Key-value and required password (or another authentication method)
   * Select the events for which you want to receive information
5. **Final touches**
   * Select default language
   * For mobile, the bundle-ID or App-Name must be included.
   * 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. You will receive an email from the support team with the License.