Welcome to the Kredential Case Study
Holder & Enterprise wallets designed for the EBSI blockchain
My Role
UI/UX Designer
Timeline
2023 - 2024
What is Kredential?
Kredential is a credentialing platform that helps students and universities issue, manage, and verify verifiable credentials (VCs) in a secure, decentralized way, built entirely from scratch for the EBSI framework. The platform runs on two sides: Holder Wallet and Enterprise Wallet both working independently and together, cross-platform.
Holder Wallet
The Holder Wallet is the student-facing experience. It allows students to securely store, request, and manage their credentials all in one place. They can easily share credentials via email or QR code, and verify them instantly. The design is mobile-first and approachable, built to feel secure without overwhelming users with technical language.
Enterprise Wallet
The Enterprise Wallet is used by universities and credential-issuing institutions. Through this interface, admins can issue new credentials, review and approve student requests, or revoke them when needed. It’s designed for clarity and scale, helping institutions manage credentials efficiently while staying fully compliant with EBSI standards.
Team
Collaborators
Matjaž Tercelj (Solution Delivery Lead)
Marinka Krel (Lead UI/UX Designer)
Žan Kovačič (Blockchain Developer)
Tadej Polajnar (Front-End Developer)
Design Impact
Key metrics that show how our design evolved over time.
Simplified user activation with visual and structural enhancements
We redesigned the onboarding flow to be more welcoming and user-friendly by adding a friendly mascot and clear visual examples. This helped users better grasp complex terms like credentials and presentations, making each screen cleaner and more engaging.
This update led to:
25% faster onboarding walkthroughs during user testing
20% fewer user questions during internal demo sessions
Version 1
Version 2
Improved Edge Case handling across platforms
We revisited edge case handling in both the Holder Wallet and Enterprise Wallet. Early testing revealed unclear UI communication, causing 30% more confusion during QA and extra user steps.
By mapping high-risk edge cases in FigJam and collaborating closely with developers, we:
Added empty-state screens and clearer error messages for onboarding and scanning on the Holder side
Refined credential status flows (revoked, pending) to eliminate dead ends on the Enterprise side
These improvements reduced QA issues by 25%, minimized handoff friction, and enhanced app resilience for real-world use.
The Process
From EU regulations to real screens, this is how we designed Kredential.
Kicking things off at University of Maribor (FERI)
Before jumping into designing, we joined a workshop at the Faculty of Electrical Engineering and Computer Science, to gather first hand knowledge on the project. We participated in a full-day focused on decentralized identities.
We discussed decentralized identity flows and real academic credentialing use cases with domain experts. This helped us refine both the Holder and Enterprise wallet features and get a better perspective on how real universities manage credentials.
Foundational Research & Competitor Analysis
We researched issuance, verification, and user experience on platforms like Accredible, SmartCertificate, and TrueLayer. Identified what worked, what didn’t, and key gaps.
Reviewed EBSI documentation, DID methods, verifiable credentials, and trust registries to ensure our design fits real-world usage.
This gave us clarity and the constraints needed to move forward with confidence.
Scenarios
The Approach
Mapped out scenarios and user flows in FigJam to translate requirements into human-centered use cases:
Login with existing DID
Identity verification for first-time users
Credential issuance after course completion
Verification requests from employers/institutions
These flows clarified what users need and why—building a solid foundation for our UX design.
This is where requirements turned into flows, personas, and use cases.
I took the research and started mapping out user stories, not just the technical flows, but how actual people would move through the product.
How does a student log in with a DID? What happens when someone gets rejected? What does a verifier actually need to see to trust a credential?
These flows helped the entire team spot edge cases and approval steps early, and they made dev handoff way smoother down the road.
User Flows & Journeys
Designing cross-platform paths for students and institutions.
The Goal
Mapping the full experience of how users interact with digital credentials across both platforms. We wanted to understand what it really looks like for students and institutions to use this system from start to finish. That meant analysing every step: from requesting a credential, to logging in with a decentralized ID, all the way to verifying a diploma through a QR code.
The solution was to create flows for both sides of the platform:
- Holder Wallet (for students)
- Enterprise Wallet (for institutions and verifiers)
Feature Breakdown
The Approach
Worked through spreadsheets, stakeholder notes, EBSI documentation, and a growing list of compliance requirements.
Tagged every feature—DID support, revocation logic, access control, signature types—and aligned them with both user goals and technical realities.
This created a clear roadmap and kept the design phase focused.
UI Design & Visual System
Bringing clarity, trust, and a human touch to a blockchain-backed platform.
The Approach
Worked on a cross-platform UI/UX design team for both the Holder Wallet and Enterprise Wallet. Ensured accessibility, strong visual hierarchy, and designed a welcoming mascot and iconography for a more human product.
Users can manage all verifiable credentials—diplomas, transcripts, microcredentials—in one secure location, with quick filters for easy access.
The request credential form lets students submit required details and pick credential type, institution, and country for streamlined issuance.
Issued credentials can be shared securely via email; users just fill in recipient info and send with one tap.
For instant verification, scanning a QR code confirms credential authenticity and directs users to a verification page.
Meet the Mascot!
Giving a friendly face to decentralized tech.
To make the Holder Wallet more human and approachable, I designed a custom mascot—a friendly, expressive character with a graduation cap. This added warmth and relatability to decentralized tech, supporting new users exploring concepts like verifiable credentials and DIDs.
The mascot, visible throughout onboarding, builds trust, aids user guidance, and makes the experience more personal—all key to a user-friendly product.
Manual QA
Making sure what we built actually felt like what we designed.
Performed thorough manual QA on both Holder Wallet and Enterprise Wallet to ensure the final product matched our Figma designs.
Focused on performance consistency, details like font weights, spacing, button styles, and component behavior.
Tested edge cases, interrupted flows, and reported issues in Jira with screenshots and reproduction steps.
This process guaranteed our design looked great and worked as intended for real users.
View More of My Work
White Label Marketplace
Scalable and flexible white-label NFT marketplace that any team can launch fast and customize easily.
