Fintech & banking
Verify the right attributes during customer onboarding.
Replace some document-heavy steps with a consent-based wallet presentation of the identity attributes your account-opening flow actually needs.
Manual document capture creates friction and leaves teams handling copies they may not need for every step.
How it works
A simple flow.
A verifiable result.
- 01
Define the purpose and claims
Request only the attributes needed for a specific onboarding or step-up decision.
- 02
Ask the customer to present them
Start a relying-party wallet flow with a link or QR code and let the customer review the request.
- 03
Apply your bank’s checks
Verify the presentation and issuer, then pass the result into your existing onboarding and compliance rules.
Wallet authentication and attribute presentation
- Reduce avoidable document handling
- Keep the bank in control of onboarding decisions
- Use an auditable verification result
Credential availability, assurance requirements, relying-party registration, and any KYC/AML duties depend on the bank, issuer, wallet implementation, and jurisdiction. Wallet verification does not replace the bank’s due diligence.
DLBR EID verifies supported wallet presentations and returns a verification result. Credential issuance, the relying party’s decision, and sector-specific processes stay with the relevant organization.
See the EUDI Wallet Architecture and Reference Framework Opens in a new tabStart with a wallet flow
Explore a verification in your sandbox.
Test the gateway with sample credentials, then confirm issuer and wallet support for your production use case.