Readiness and target architecture
Assess use cases and gaps in current identity, signing, evidence and integration.
CURRENT FOCUS · 2026—2027
Preparing for EUDI Wallet, AMLR and DÁP integration.
EUDI Wallet, AMLR onboarding and DÁP connection need shared building blocks: identity, attributes, evidence, decision, signing and preservation.
The exact obligation and deadline must be assessed for each organisation and use case; this page is implementation guidance, not legal advice.EUDI Wallet availability
As member-state wallets emerge, cross-border testing and relying-party readiness become business priorities.
AMLR applies
Identity and CDD processes, controls and evidence need reassessment for the new AML framework.
Wallet acceptance
Relying-party obligations and timing depend on the service and applicable eIDAS implementation detail.
EIDAS 2.0
EUDI Wallet: accept data and issue attestations
Wallets can present personal identification data and electronic attestations of attributes. Integration connects data requests, authenticity checks and documented results to the business process, and supports attestation issuance from enterprise records.
- Wallet Gateway and the accepting service provider’s (RP) API
- Request the data and attestations needed for the transaction
- Wallet Studio / QTSP
- Wallet identity plus electronic signing
AMLR
Onboarding: primary eID, controlled fallback
Orchestrate eID / wallet, document / NFC, biometrics, video and data checks in one governed journey.
- Method matrix by country and risk
- Request types, rules, retry and fallback
- Webhook, evidence export and institution CDD decision
- QES / contracting at the end
HUNGARIAN ECOSYSTEM
DÁP eIdentification and eSignature
Our DÁP eIdentification component is ready for integration with existing customer journeys. eSignature integration is in its final development phase.
- Completed eIdentification component
- Data enrichment and business checks
- eSignature integration under development
- Onboarding and signing-system integration
ONE TARGET ARCHITECTURE
Shared building blocks prevent three isolated projects.
Onboarding and Signing API provide one integration layer to business systems, while national eID, EUDI Wallet, DÁP, QTSP and document components remain replaceable and extensible.
Business channelOnboarding / CDDSigning APIeID · Wallet · DÁPQTSP / AttestationDMS / Trusted Archive
READINESS → ROLLOUT
Recommended readiness programme
Scope
Affected products, journeys, obligations and organisational owners.
Gap assessment
Current eID, KYC, signing, DMS, audit and evidence retention.
Use case and target
Primary and fallback routes, system boundaries, decisions and responsibility.
API and evidence
Requests, webhooks, presentation requests, validation and retention package.
Pilot
Wallet, DÁP and onboarding scenarios with positive and negative tests.
Rollout
Go-live, monitoring, audit, certificates and further use cases.
DELIVERY MODEL
Roles and responsibilities.
Contum provides business analysis, solution design, its own Signing API middleware and integration. Namirial can provide wallet, onboarding and signing technology alongside qualified trust services (QTSP services). The organisation providing the service remains responsible for customer due-diligence (CDD) and compliance decisions.