Design and configuration

The flow module is the starting point for working with IDV Suite.

From this module, product, business, and technology teams can:

• Design what the Onboarding or authentication flow (which steps it includes and in what order).

• Decide how that flow is exposed across the customer's different channels:

  • Integrations no-code (hosted experiences, links).

  • Integrations low-code (SDK Mobile/web)

All of this is done from a graphical interface. The goal is for the customer to be able to evolve their digital identity processes at the same pace as their business or regulatory needs change.

Steps to have an end-to-end flow in IDV Suite

To put an Onboarding or authentication flow into operation in IDV Suite, from start to finish, the journey is:

1. Design and configure the flow in the IDV platform

   • Access the flow module of IDV Suite.

   • Create a new flow, choosing whether to start from a template or design it from scratch.

   • Configure all capture components (document, biometrics, NFC, etc.) and the functional logic (OCR, Matching, Liveness, morphology, etc.).

2. Generate the Integration

   • No-code option. Landing environment.

   • Low-code option (web or mobile).

3. Configure and publish the Integration

   1. Adjust specific integration parameters:

   2. Look & feel (logo, colors).

   3. Webhook / callback subscription to receive events and results.

   4. Publish the Integration in the corresponding environment and note the Integration ID associated with the published Integration.

4. Integrate the channel (SDK Web / SDK Mobile) using the Integration ID

   • Low-code:

     • Integrate the SDK Web/Loader or SDK Mobile of IDV Suite into the client's applications.

     • Configure the SDK to run the flow using the Integration ID obtained after publication.

   • No-code:

     • Backend configuration.

   • In both scenarios, the license that the support team will provide once the Integration has been published is required.

5. Run tests and review the operations on the platform

   • Perform end-to-end tests from the integrated channel (web or app).

   • Verify that operations are generated correctly and review them from the IDV Suite Operations Module (results, details, possible manual reviews).

Prerequisites

Before following these steps, the following must have been requested/provided:

• Client and tenant created.

• SDK credentials configured.

• Licenses active for the components that will be used.