> 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/configuracion-tecnica-del-cliente/sdk-mobile/idv-mobile.md).

# Flows & IDV Mobile Integration

The documentation includes specific integration sections in [Android](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/sdk-mobile/android-sdk.md) and in [iOS](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/sdk-mobile/ios-sdk.md).

The functionality is based on flows and integrations.

## Flows

Creation of a Mobile flow:

<figure><img src="/files/b467ddd6ae59b549f8e353ab99f54e893f139b54" alt=""><figcaption></figcaption></figure>

When creating the flow, we can choose a template from the available ones or a blank page:

<figure><img src="/files/b44e6bc3d451582d92dc635683d8e2774b192949" alt=""><figcaption></figcaption></figure>

For example, if we select Identity Verification, we would have the steps for an Onboarding preconfigured.

<figure><img src="/files/f09636ed8939814ffdbd8d2118091e88cc113451" alt=""><figcaption></figcaption></figure>

There are two ways to add steps:

* By clicking on the element: this will add it to the end.
* Dragging it: this allows it to be inserted between two existing steps.<br>

To delete elements, we drag downward.

<figure><img src="/files/755da029e65539122b26035fcda49a8353719dca" alt=""><figcaption></figcaption></figure>

Once all the steps have been configured using the guides attached to this documentation (for example the [*Component - Document*](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/sdk-mobile/idv-mobile/componente-documento.md)), we change the name:

<figure><img src="/files/12adc1d73b91da5abe602f7db5a10ef2e8f3c737" alt="" width="375"><figcaption></figcaption></figure>

And we can save.

<figure><img src="/files/a43930b04f8a1f2df671c84f27399897ce8a1c45" alt="" width="375"><figcaption></figcaption></figure>

Now the flow can be added to an Integration.

## Integration

There is one Integration for each application and platform (Android/iOS). An Integration can have N flows associated with it.

To create a Mobile integration:

<figure><img src="/files/9691231aaf9cd49e13a3f2923de8dd0dcbd1ff48" alt="" width="375"><figcaption></figcaption></figure>

And we choose the flow we just created:

<figure><img src="/files/29dd43346c9423b54d8ee0b99b803fe6c6a48c2c" alt="" width="375"><figcaption></figcaption></figure>

Once a flow is selected, we save. The platform will take us to the next configuration step:

<figure><img src="/files/ac2eb56e58358bb3405eeedbcc25712bd076d08f" alt=""><figcaption></figcaption></figure>

There are 4 sections here:

### Flow selection

We can associate as many flows as we want with the Integration. Deleting a flow using the trash icon does NOT delete the flow, it only unlinks it from this integration. Editing a flow DOES edit it for all the integrations it is associated with.

### Customization

The next step allows configuring the interface of the SDK Mobile.

<figure><img src="/files/4a64c683de2e2874ecfb4f9038ca3e695c48202f" alt=""><figcaption></figcaption></figure>

The customization wizard allows us to modify different options such as the name of the integration, the app colors (both in *light* and in *dark mode)* and the appearance of the buttons.

<figure><img src="/files/5f0c2bb783af3a47651f8c3d066db16e9cc4b931" alt=""><figcaption></figcaption></figure>

The view on the left is only visible in the SDK Mobile if the "Initial tip before capture" parameter has been enabled in the flow component.

The view on the left is only visible in the SDK Mobile if the "Error diagnostics screen" parameter has been enabled in the flow component.

### Connect

IDV operations can be associated with a webhook.

### Configure

#### Language

Default language selection from among the available ones.

#### Platform

The integration must be associated with an Android or iOS application.

#### BundleID

The Bundle ID (iOS) or ApplicationID (Android) is the identifier to which the license generated for this integration will be associated. The structure of this identifier is usually *com.mycompany.product.*

<figure><img src="/files/289dd9a3dc219d2e885a291c0ab6d7c2bfd055dc" alt="" width="375"><figcaption></figcaption></figure>

If we now click Next, we will have an integration with an associated flow. If we want to use it, we will need to request publication.

Once published, we will need the *ApiKey* that will have been generated in order to license the app where we integrate the SDK Mobile.