Request only what the step needs
Configure an intended use and the permitted attributes for that onboarding journey. A request outside that scope is rejected before a wallet session is created.
EUDI WALLET · BANKING & FINTECH
EUDI Wallet Onboarding for Banks and Fintech #
For account opening and digital onboarding, verify customer identity with the Person Identification Data (PID) needed for that step. DLBR EID checks each request against your declared purpose before it creates a wallet session or QR code.
This step supports digital account opening, fintech user registration and other customer onboarding journeys that need verified name and date of birth without collecting unnecessary data.
A focused identity step for customer onboarding #
Keep your existing decision process
The gateway verifies the wallet presentation and returns the permitted result. Your bank or fintech remains responsible for customer acceptance, KYC and any follow-up checks.
Prepare for wallet-based authentication
Use PID verification as a defined onboarding step, with a separate path for any later strong customer authentication (SCA) flow.
Choose the PID attributes for the step #
Depending on your purpose, applicable rules and the credentials available in the customer’s wallet, an onboarding request may need attributes such as:
given_namefamily_namebirth_date
Example configuration
Intended use: “New customer onboarding – name and date of birth”
Permitted attributes: given_name, family_name, birth_date
A request for address, portrait or another out-of-scope attribute is rejected with ERR_CLAIM_OUTSIDE_INTENDED_USE before the QR code is shown.
Available attributes depend on the wallet and credential. Your organisation remains responsible for deciding what it needs and confirming that its declared purpose and registration allow the request.
How the onboarding flow works #
- Define the onboarding purpose and the attributes needed for that step.
- DLBR EID checks the request against the configured purpose before creating a session.
- The customer reviews and approves the request in their EUDI Wallet.
- Your application receives the verification result and applies its own onboarding decision.
Plan an alternative verification route if a customer has no wallet, declines the request, or their wallet does not contain a requested attribute.
What the gateway does—and does not do #
The gateway
DLBR EID verifies wallet presentations, enforces the configured request boundary, and returns permitted results. Selected claims are deleted within 30 seconds of the result; audit records do not contain claim values.
Your organisation
It does not register your organisation as a relying party, replace KYC or SCA, or decide whether to open an account. Your organisation remains responsible for registration, legal basis, customer disclosures and business decisions.
Plan onboarding with the 2027 EUDI Wallet changes in view #
Article 5f of the eIDAS Regulation sets wallet acceptance requirements for certain private relying parties that must use strong user authentication for online identification, subject to the regulation’s scope and implementation timeline. For private relying parties in scope, excluding micro and small enterprises, the acceptance deadline is 24 December 2027. Banks should confirm with their compliance team whether their services meet the conditions. This PID onboarding step can be planned alongside the separate SCA journey.
Questions about EUDI Wallet bank onboarding #
Can a bank request only a customer’s name and date of birth?
A request can be limited to attributes configured for a specific intended use, where those attributes are available in the wallet and permitted by the applicable rules. The relying party remains responsible for establishing what it needs and why.
Does PID verification replace KYC?
No. A wallet presentation can support an identity-verification step, but it does not automatically satisfy every customer due diligence, KYC or onboarding requirement. Your compliance team decides how it fits into your controls.
Does onboarding through a wallet count as SCA?
Not by itself. Identity or PID verification and strong customer authentication are distinct use cases. Payment or account-access SCA needs its own flow and policy.
Do we still need to register as a relying party?
Yes, where the applicable EUDI Wallet rules require registration. DLBR EID does not register your organisation or issue a registration certificate.
When are claim values deleted?
Selected claims are deleted within 30 seconds of the verification result. Audit records do not contain claim values.
Assess EUDI Wallet onboarding for your bank or fintech #
Tell us about your customer onboarding journey, the markets you serve, and whether you are also preparing for SCA acceptance by 2027.
Request private pilot access