Modules form the core of an onboarding flow in Uniify. They establish a connection between Uniify and external entities that possess and manage specific datasets. These integrations enable seamless access to data, enhancing the functionality and capabilities of the flow. The modules ensure that data is utilized securely.

A flow is a sequence of modules arranged in a specific order and identified by a unique name and code. Our solution offers two types of flows: background flows and frontend/onboarding flows.

A background flow consists solely of background modules. These modules operate in the background without being visible to the end-user and automatically submit data without user interaction. A background flow may include modules such as CPR Registry, REST API, or PEP/AML.

For more details on our modules, please refer to our module types documentation.

An onboarding flow is a type of frontend flow that guides the end-user through a series of steps, such as filling out custom forms or ID verification. This flow is designed to enhance the user's onboarding experience. A frontend flow can include both frontend and background modules.

A case represents both a company and a customer (primary entity) and can consists of one or more secondary entities. Secondary entities may include people associated with a company or potentially a partner in a private person's case. Each entity contains existing entity flow codes that are linked to the specific flows assigned to that entity. All collected data is stored on the platform under the corresponding case.

An entity in Uniify refers to either a company or an individual. Entities are linked to and stored within a case and contain one or more entity flows. Each flow has a Primary Entity, which represents the person or company undergoing the onboarding process.

The entity flow is the most detailed object in the data structure. It contains basic information derived from the entity it belongs to, as well as a collection of all available module data for the given flow.

Document objects serve as accessible components at the case, entity, and entity flow levels. These objects are available from both the backend and frontend of the application and encompass a wide range of documents. Examples include documents generated from Creditsafe, custom forms, or uploads of driver’s licenses.

For more details, please refer to our Documentation and API references.