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
Flow Builder The central axis: how journeys are designed and how they are executed in web/mobile channels.
Typical use cases 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:
You design a flow
You publish it and generate an integration (Integration ID)
You connect it to your channel (web, app or no-code)
The user executes the flow (operation)
IDV Suite sends real-time events (webhooks)
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 configurationI want integrate quickly without development → Within “Flow design and configuration”, go to:
No-Code IntegrationsI want to integrate into my web or mobile app → Within “Flow design and configuration”, go to:
Low Code IntegrationsI want receive results in my system → Go to:
WebhooksI want operate and review results → Go to the
Operations module
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).
Last updated