> 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/primeros-pasos.md).

# Getting Started

### Welcome to Facephi IDV Suite

This section gives you the minimum context to move quickly: **what Facephi IDV Suite is**, how it is structured (flows + integrations) and what use cases it covers. If your goal is “to get it working”, here you will find the shortest path to start with a solid foundation.

***

### What will you achieve with this section

By the end **Getting started**, you will be able to:

* Understand **what it solves** Facephi IDV Suite and in which situations it adds the most value.
* Speak the same language: **Flow**, **Integration**, **Integration ID,** **operations and events**.
* Identify which is your “route” (no-code, web or mobile) to move on to the configuration and integration part.

***

### Start here

1. [**Flow Builder**](/docs.facephi-en/products/idv-suite/primeros-pasos/flujos-and-integraciones.md)\
   The central axis: how journeys are designed and how they are executed in web/mobile channels.
2. [**Typical use cases**](/docs.facephi-en/products/idv-suite/primeros-pasos/casos-de-uso-tipicos.md)\
   Real examples to ground the value (Onboarding, authentication, multichannel).

***

### How does Facephi IDV Suite work?

In IDV Suite, everything is easier to understand if you are clear about these concepts:

* **Flow:** It is the journey the user follows, step by step, to verify their identity.\
  Example: consent → Document Capture → selfie → validations → result.
* **Integration:** It is the way to connect that flow with your digital channels: web, mobile app or no-code experience.
* **Integration ID:** It is the unique identifier of each published integration.\
  It is what your web or app needs to know **which flow** it must execute.
* **Operations:** It is each time a user executes a flow.\
  All operations are logged and can be viewed and managed from the platform.
* **Events and results (webhooks)**\
  IDV Suite sends real-time events during the execution of an operation via webhooks (HTTPS Callbacks), allowing you to track its progress and receive the final result in your system.

#### In summary:

1. You design a flow
2. You publish it and generate an integration (Integration ID)
3. You connect it to your channel (web, app or no-code)
4. The user executes the flow (operation)
5. IDV Suite sends real-time events (webhooks)
6. You receive the result and make a decision in your business process (for example, approve/reject a user's registration, etc.)

***

### What should I read next?

* I want **to configure the process** and understand the journey in detail\
  → Continue with: [`Flow design and configuration`](/docs.facephi-en/products/idv-suite/flujos-and-integraciones.md)
* I want **integrate quickly without development**\
  → Within “Flow design and configuration”, go to: [`No-Code Integrations`](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code/integraciones-no-code.md)
* I want **to integrate into my web or mobile app**\
  → Within “Flow design and configuration”, go to: [`Low Code Integrations`](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code/integraciones-low-code.md)
* I want **receive results in my system**\
  → Go to: [`Webhooks`](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/webhook.md#documentacion-de-webhooks)
* I want **operate and review results**\
  → Go to the [`Operations module`](/docs.facephi-en/products/idv-suite/idv-suite/modulos-de-idv/operaciones.md)

***

### Minimum glossary

* **Onboarding**: identity verification for the onboarding of a new user.
* **Authentication**: reinforced verification for sensitive accesses or operations.
* **No-code**: execution of the flow with very little frontend development.
* **Low-code**: execution of the flow integrated into the client's channels (web/mobile).

***