Namirial

Namirial identity verification combines document checks with facial comparison and liveness assessment across different identification methods. The portfolio includes automated self-service journeys, hybrid checks and video identification with a trained operator. Document chip reading provides another way to examine supported identity documents during remote onboarding.

The appropriate method depends on the financial product, supported country and available customer evidence. Buyers should establish when automated verification is sufficient, when human review applies and how applicants receive a usable alternative after an unsuccessful attempt.

The Namirial Onboarding documentation describes ID Hub as a way to connect national electronic identity providers within customer journeys. Examples across the wider portfolio include SPID and CIE in Italy and ID Austria in Austria. A financial institution can examine these methods alongside document-based verification when planning a European rollout.

Availability of an electronic identity does not establish that every applicant can use it. Institutions should check country coverage, assurance requirements, returned attributes and the route available when a customer cannot complete that method.

Namirial Sign supports simple, advanced and qualified electronic signatures through signing applications and integration interfaces. Signing workflows can define participant roles, completion order and deadlines for a document transaction. For financial services, that connects identification with the practical task of completing an agreement.

Loan applications, insurance contracts and account agreements can require different evidence and signature arrangements. Buyers should choose the appropriate electronic signature level for each transaction and confirm certificate validation, document delivery and access to the completed evidence.

The Namirial Wallet portfolio separates three functions that financial buyers should assess individually. Wallet Gateway connects business systems with credential issuance and verification, while Wallet App provides a user-facing place to hold and present credentials. Wallet Studio manages credential templates, lifecycle rules and related configuration.

These roles matter when a financial institution requests an income attribute, issues an attestation or accepts an identity credential. Planning for the European Digital Identity Wallet should distinguish the demonstrated interaction from future compatibility claims and certification requirements.

Namirial Onboarding describes configurable workflows with conditional branches, pause and resume behavior, and connections between identification and signature steps. Its documentation presents REST interfaces alongside back-office tools for operational teams. Those capabilities are relevant when one application must coordinate several checks before a financial institution reaches its decision.

A pilot for identity orchestration in finance should follow the complete application, covering each stage of the customer journey. Confirm how evidence, outstanding tasks and final outcomes appear in the institution application and operational review tools.

The onboarding documentation describes configurable retention and anonymization alongside audit information for completed workflows. Procurement teams should translate those capabilities into explicit agreements about stored evidence, access permissions, deletion timing and support responsibilities. A configurable product feature does not itself determine the institution retention policy.

Identity checks, electronic signatures and wallet credentials produce related but different evidence for financial decisions. The broader discussion of reusable KYC helps identify which information can be reused and which checks require refreshed evidence or additional approval.

Start evaluation with the countries, customer groups and document types needed by the actual financial service. Test representative documents, interrupted journeys, operator escalation and delivery of signed agreements across those markets. Include operational staff who must investigate exceptions and explain an incomplete application to a customer.

Compare implementation effort, supported languages, accessibility, availability commitments and charges across the proposed modules. Request evidence for the specific deployment and trust services being purchased, establishing the certification and contract scope for each product.

Does a wallet replace an entire onboarding process?

A wallet can supply identity credentials or selected attributes within an onboarding journey. The financial institution still decides what additional checks and evidence its product requires.

Are identification and qualified signing the same service?

Identification establishes evidence about a person, while signing records agreement with a document. A complete contract journey can combine both services while retaining their different evidence and responsibilities.