Arkadiz Insights
Practical, vendor-neutral guides on the EU Digital Identity framework for the teams that have to implement it: verification, attestations, registration and compliance.
Vezi blogul în românăThe EUDI Wallet makes selective disclosure technically possible, but it does not make your data collection GDPR-compliant by default. Here is what relying parties actually need to get right.
Every vendor quotes the API integration as a few sprints. The real cost of accepting the EUDI Wallet sits in registration, certificates and ongoing conformance. Here is the honest breakdown.
Romania is building its national EUDI Wallet under the same eIDAS 2.0 framework as every other Member State. Here is what is defined, what is still evolving, and how to prepare.
Banks and fintechs sit at the intersection of two regulatory tracks — PSD2/PSD3 and eIDAS 2.0 — that are converging on the same wallet. Here is what that means for SCA, account opening, corporate mandates and the business case for moving early.
Regulators want reliable age checks; users and DPAs want no identity data collected to get one. The EUDI Wallet's selective disclosure model is the first mechanism that satisfies both — here is how it works in practice.
Document scans and liveness checks are the most expensive, highest-abandonment step of onboarding. The EUDI Wallet replaces them with a signed, reusable credential — here is what that migration actually looks like.
You don't need to become a Qualified Trust Service Provider to put attestations into millions of EUDI Wallets. Here is the practical path most organisations should actually take.
QEAA and non-qualified EAA are not two flavours of the same product — they carry different legal weight, different issuer obligations, and very different costs. Here is how to choose.
An EAA lets any organisation issue a signed, wallet-ready claim about a person or entity — employment, membership, licence, entitlement. Here is how the data model, lifecycle and revocation actually work.
The ARF is the living technical rulebook behind every wallet, issuer and Relying Party in the ecosystem. Understanding how it changes matters as much as understanding what it says today.
Every wallet presentation request you sign relies on a certificate chain that expires, rotates, and can be revoked. Here is what actually running that infrastructure involves.
Accepting EUDI Wallet credentials means implementing a presentation protocol, verifying a signature chain, and shipping a UX your users trust. Here is the practical path, end to end.
Registering as a Relying Party in every Member State you serve is expensive to build and to maintain. The intermediary model exists to make that a single integration instead.
Before your service can ask a wallet for a single attribute, you must be a registered Relying Party. Here is what that process actually involves, country by country.
eIDAS 2.0 is not an IT footnote — it is a regulation with deadlines, mandatory acceptance rules and financial penalties. Here is what actually applies to your business.
The EU Digital Identity Wallet turns identity into a verifiable, user-held credential. Here is what it changes for platforms that need to know who their users are.
One integration for EUDI Wallet verification and non-qualified EAA issuance across Member States.
Contact the team