Regulatory transition
AMLR, AMLA CDD RTS, eIDAS-based identity and local AML rules must work together.
← Home
IDENTITY & KYC · ONLINE ONBOARDING
One customer journey. Multiple identity methods. An auditable decision.
Online onboarding can connect data collection, customer identification, required checks and contracting in one online journey. We integrate Namirial Onboarding with your systems and customer due-diligence rules to reduce manual data handovers.
Available solution with a remote-identification reference
We do not force one identity method on every customer. Primary and controlled fallback routes can vary by country, risk, customer type and product.
Unified APIStart different identity methods and retrieve their results through one integration.
Request typeA reusable configuration defining the onboarding steps, required data, documents and checks.
Validation dataIdentification results, documents and audit records (evidence) can be passed to the business system to make the process traceable.
Starting point
An identity result is not yet a customer due-diligence decision.
Technology checks must be embedded in the obliged entity’s own CDD, risk and evidence-retention model.
Missing customer data
Identification may not provide everything needed for customer due diligence (CDD). Missing data must be requested separately or obtained from other trusted sources.
Different customers and countries
Individuals, legal entities, existing and new customers, and different available eIDs.
Assessing the results
A completed technical workflow (COMPLETED status) is not the same as successful customer due diligence. The service provider makes its decision using the detailed results and its own rules.
Capabilities
Modular identity with unified orchestration.
ID Hub
Connect national eIDs and wallet-based identity methods, subject to country and environment availability.
ID Doc
Process identity documents, extract data and perform document checks.
ID Self
Remote document and face capture, biometric checks and review appropriate to the configured flow.
LiveID+ / ID Video
Operator-assisted live video identification under the selected service model.
Data Hub
Connect supplementary data checks and external sources to the customer journey.
DocProcessor
Extract structured data from supporting documents. Specific features and production availability are confirmed for the selected configuration.
Integration
One API for eIDs, EUDI Wallet and alternative remote methods.
The onboarding orchestrator returns a unified result while the final CDD decision stays with the obliged entity.
Institution system
Application, customer data, product, risk classification and final decision.
→Onboarding API
Request creation, request type, status, webhook and evidence export.
→Orchestrator
Method selection, sequencing, conditions, retry, fallback and operator work.
→Identity channels
eID or EUDI Wallet, document and NFC checks, selfie and liveness, video identification and external data checks.
→Due diligence and contracting
Checks on politically exposed persons (PEPs), sanctions and ultimate beneficial owners (UBOs) inform the provider’s decision on contracting. Electronic signing can follow approval.
Journey
Example: remote retail-account opening.
The primary eID or EUDI Wallet route and the alternative remote route are handled in the same controlled workflow.
Application
Product, customer type, country, consents and risk context.
Primary identity
eID or EUDI Wallet PID; where needed, document and NFC checks plus biometrics.
Enrichment
Missing attributes, customer declarations and supplementary data sources.
Due-diligence checks
Check sanctions lists, politically exposed person status and beneficial ownership according to the service provider’s rules.
Decision and contracting
The service provider uses the check results to decide whether to establish the customer relationship. Following approval, the customer can sign electronically and the supporting records can be retained.
Use cases
Typical applications
Identification for certificate issuance
At NN Hungary, we delivered remote identification for issuance of signing certificates.
Financial-services onboarding
Connect identification, required data checks and digital contracting to the service provider’s own CDD process.
EUDI Wallet and DÁP
Add new identity methods to the existing journey, with separate checks of availability and applicability.
Delivery
Journey, controls and responsibilities must be designed together.
Contum provides design, configuration, integration and support, with business and compliance advice. We involve legal partners where required. The customer due-diligence decision remains with the service provider.
Business process and risk
Customer type, country, product, risk category and required controls.
Method matrix
Primary eID or EUDI Wallet route and permitted alternatives by country.
Request type and integration
API, webhook, evidence export, CDD data model and signing connection.
UAT and compliance
Positive and negative tests, fallback, operator process, evidence and go-live.
Related regulation and modules
Namirial OnboardingID Hub · ID Doc · ID SelfLiveID+ / ID VideoData Hub · DocProcessorSigning APIAMLR · eIDASCompliance assessed for the specific journey
ONBOARDING QUESTION
For which customer segments should EUDI Wallet be the primary route, and what is the controlled fallback?
Together we map the method matrix, request types, institution decision points and evidence package.
Onboarding workshop↗