# Overview

A high-level orientation to the Namirial Onboarding Suite — what it is, why it matters, and how the pieces fit together.

## Vision & Objectives

Namirial Onboarding envisions a future where digital onboarding is universally seamless, secure, and fully trusted. They aspire to be the global leader in digital trust services, empowering businesses of all sizes to efficiently and compliantly acquire and manage customers entirely online. Their vision is to create a world where geographical boundaries and complex regulations no longer hinder digital expansion, fostering a truly interconnected and secure global digital economy for everyone.

### Mission

Namirial Onboarding's mission is to streamline and secure the digital customer onboarding process. They aim to provide businesses with a comprehensive, compliant, and user-friendly platform that simplifies identity verification, electronic signatures, and contract management. Their goal is to accelerate customer acquisition while ensuring regulatory adherence and a seamless experience for both businesses and their customers.

### Objectives & Metrics

- **Maximize Onboarding Completion Rate** - Percentage of users who finish the entire onboarding flow.
- **Minimize Onboarding Drop-off** - Identify steps where users abandon and eliminate friction.
- **Decrease Onboarding Time** - Mean time taken by users to finalize all onboarding stages.
- **Increase User Confidence** - Time until a new user performs their first valuable action.
- **Promote Automatic Process** - Percentage of onboardings requiring human intervention.


### Customer Values

- **Simplicity & Ease of Use** - Excellent User Experience
- **Security & Compliance** - Reliability & Peace of Mind
- **Speed & Efficiency** - Time to Value
- **Reliability & Availability** - Zero Downtime & Robustness
- **Sustainability** - Reduced Environmental Impact


### Customer Segments

- Financial Institutions (Banks, Insurance Companies, Fintechs)
- Telecommunications Companies
- Utility Providers (Energy, Water, Gas)
- Public Administration / Government Bodies
- Large Corporations (various sectors)
- Healthcare Providers


## High-Level Architecture

### Environments

| Production | Test | Development (only for developers) |
|  --- | --- | --- |
|  |  |  |


### Structure

Namirial Onboarding has a core that orchestrates multi-step journeys (identification, data collection, signing) and manages the data produced across steps. A back office lets teams review requests, configure processes and, where allowed, edit data.

Many capabilities are powered by modular integrations built by Namirial or third parties. For identity, ID HUB centralizes digital identity providers; its evolution focuses on new countries and segments. Alongside it, recognition systems such as ID SELF Fast, ID SELF Max, ID DOC Check and third-party solutions extend coverage.

Verification of data gathered during recognition and entry (also known as data enrichment) is handled by the DATA HUB. It selects the best provider(s), routes requests, aggregates checks and produces scores that indicate data quality and potential fraud.

Document files collected for enrichment can be processed by DOC PROCESSOR for AI-based extraction. Together, DATA HUB and DOC PROCESSOR constitute the suite's Data Intelligence layer: usable standalone, but especially valuable when combined within onboarding journeys.

Namirial Onboarding can be used via APIs or via the back office UI to create onboarding requests. API usage is the most frequent, enabling integration from any service capable of calling RESTful APIs.

### API & Back Office

Namirial Onboarding can be used via APIs or via the back office UI to create onboarding requests. API usage is the most frequent and enables integration from any service capable of calling RESTful APIs.

## Modules

### Orchestration & Integration

Namirial Onboarding is the conductor of digital customer acquisition: it connects eKYC, signatures, document flows and compliance (AML, GDPR, eIDAS) to automate multi-step journeys end-to-end. Result: fewer hand-offs, less friction, consistent compliance across countries, and faster time-to-value.

#### Functional Specs

- **Workflow orchestration**: define multi-step flows, branching, and conditional rules; reorder/activate steps easily.
- **eKYC integration**: video ID, doc verification, selfie-with-ID, biometrics; real-time checks incl. liveness.
- **Digital signatures**: SES/AES/QES per eIDAS; OTP via SMS/email/app; integrity & non-repudiation.
- **Form & data capture**: rich fields, validation, prefill from sources; file uploads.
- **Document management**: secure storage; dynamic document/contract filling via templates.
- **Compliance & audit**: KYC/AML/GDPR/eIDAS controls; immutable audit trail; compliance reporting.
- **APIs & webhooks**: integrate CRM/core banking/ERP/3rd-party; status callbacks for automation.
- **User UI**: responsive, guided UX; multi-language.
- **Admin & reporting**: configure flows/users; dashboards on completion, drop-off, SLAs, compliance.
- **Error handling**: clear messages; pause/resume incomplete sessions.


#### Interfaces / APIs

REST APIs are the backbone: define/manage workflows programmatically, abstract ID & signature steps, and receive real-time updates via secure webhooks. Tight integration with Namirial QTSP services turns complex onboarding into secure, legally valid operations.

#### User Scenarios - Examples

- Open a digital current account with eKYC, data capture, and QES.
- Subscribe to a new insurance policy: upload documents, and complete the QES on the proposal.
- Activate an online SIM with complete document and face checks, and sign the service agreement.
- Mortgage application with multi-doc upload, guided steps, and full compliance.
- Employee onboarding by ID verification, contract signing, and privacy/security forms.
- Trading account with strong KYC/AML included. PEP/sanctions & consents.
- Public service registration via SPID/CIE and secure enrollment.
- Professional order enrollment with certs, IDs and declarations.
- Contract Amendment for Telecom Plan—Review and Sign Online.
- Consumer credit: streamlined flow, instant decision, e-signature.


### Identity Modules

| **ID HUB** | **ID DOC** | **ID Self** |
|  --- | --- | --- |
| Central identity layer abstracting providers and eID schemes. Routes requests, enforces policies, aggregates results for a single compliance view; configurable per country/segment. | Automated document checks: capture, OCR/AI extraction, fraud/tamper analysis for IDs (passport, ID card, driver's license). Produces detailed evidence for audit. | Self-service verification: selfie-with-ID + liveness; compares face and document; flags cases for review when needed. Back-office can inspect artifacts. |


### Data Intelligence

Data Intelligence = DATA HUB + DOC Processor: unify, validate, enrich and score data from forms, IDs, documents and external sources.

| **DATA HUB** | **Rules Engine** | **DOC Processor (LLM/VLM)** |
|  --- | --- | --- |
| Authoritative store and router for verified onboarding data; syncs to AML and enterprise systems. Ensures consistency and instant availability to sales/ops/compliance. | Configurable decisioning on unified data: dynamic routing, enhanced due diligence for high-risk profiles, auto-approve low-risk; adapt rules without code. | LLM/VLM-powered extraction beyond OCR. Reads invoices, payslips, tax notices, bank statements, KBIS… (PDF/JPEG/PNG, 1–2 pages, ≤20MB) and returns structured JSON; supports FR/EN/DE/IT/ES. |


## Glossary

**Data Enrichment**
A step where forms are filled out, contacts verified (via OTP), and files uploaded for analysis (ID DOC Check or DOC Processor); this step may span multiple pages and sections.

**Journey (or User Journey)**
The end-user experience through the onboarding steps. It can vary by organization and the type of request.

**Organization**
A container for configurations and all requests created for a specific client; it associates its own request types and templates.

**Request**
The core entity representing steps, UI theme, data collected/produced, and artifacts. Subject to anonymization and retention policies.

**Request ticket**
The access link generated after request creation (e.g., via API), with pre-authentication and limited, configurable duration.

**Request type**
Defines the process configuration: journey, modules invoked, decisioning rules, allowed methods, fields, ticket duration, and retention.

**Template**
Visual theme: logos/colors for the journey. Configured in the back office and referenced during request creation to ensure brand continuity.