Welcome to the Kredential Case Study
Holder & Enterprise wallets designed for the EBSI blockchain
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 & Timeline
Collaborators
Matjaž Tercelj (Solution Delivery Lead)
Marinka Krel (Lead UI/UX Designer)
Project Duration
December 2023 – September 2024
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
After the workshop, we started researching, we looked closely at platforms like Accredible, SmartCertificate, and TrueLayer to understand how they approached issuance, verification, and user experience. What worked well? What didn’t? Where were the gaps?
We also went through EBSI’s technical documentation, DID methods, verifiable credentials, trust registries - everything we needed, in order to make sure what we’d design would actually work in a real environment.
This gave us the clarity (and constraints) we needed to move forward with more confidence.
Scenarios
The Approach
There was a lot to uncover, so I started sketching out scenarios in FigJam not just system diagrams, but more like, “If I’m a student and I click here… what would I expect to see?”
I focused on translating requirements into human-centered stories and use cases. This led to four key scenarios:
• Logging in with an existing DID
• Identity verification for first-time users
• Credential issuance after course completion
• Verification requests from employers or institutions
These flows helped clarify what each user needed to do and why which gave us a solid foundation for designing every interaction that followed.
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
To get there, I worked through spreadsheets, stakeholder notes, EBSI documentation, and a growing list of compliance requirements.
We tagged and categorised every feature from DID support and signature types to revocation logic and access control and aligned them with both user goals and technical realities. This gave us a clear roadmap to work from, and helped keep the design phase focused.
UI Design & Visual System
Bringing clarity, trust, and a human touch to a blockchain-backed platform.
The Approach
I worked as part of the UI UX design team that designed the interface across both platforms, the Holder Wallet and the Enterprise Wallet.
While maintaining user intuitive accessibility and visual hierarchy.
I also created the mascot and icons to give the product a more human, welcoming feel.
Users can view all of their issued credentials in one place, diplomas, transcripts, microcredentials, and more. They can use filter tags to quickly sort by credential type.
Students fill in this form to request a new credential. They provide personal data and select the type of credential they’re requesting (like a diploma or certificate), as well as the institution and country.
Once a credential is issued, users can share it directly via email. They simply fill out recipient details and hit send making it easy to share credentials with employers or universities.
For fast verification, users can scan a QR code. This instantly confirms the credential’s authenticity and redirects them to a verification page.
Meet the Mascot!
Giving a friendly face to decentralized tech.
To make the Holder Wallet feel a little more human, I designed a custom mascot in Adobe Illustrator. A simple, expressive character wearing a graduation cap. The idea was to add warmth and relatability to something that could otherwise feel technical or cold, especially for students who may be new to terms like “verifiable credentials” or “DIDs.”
I didn’t want it to feel childish, but I did want it to feel approachable and goofy. The cap gave it that immediate association with trust and education, while the friendly face made it feel like there was someone on your side as you explored the app. You’ll see the mascot throughout the onboarding screens welcoming users, guiding them, and making the whole experience a little bit more personal.
Manual QA
Making sure what we built actually felt like what we designed.
Once development was underway, my assignment was to do a manual QA. I tested both the Holder Wallet and the Enterprise Wallet to make sure the final product matched what we had designed in Figma.
Most of my time went into QA, where I tested every part of the platform and monitored the performance consistency using the browser’s inspect tool. I paid close attention to detail like font weights, spacing, button styles, background colors, and whether each component responded the way it should.
I tested the limits of the platform. I triggered edge cases, interrupted flows, entered incorrect data form, anything that might lead to inconsistency in the system. If something broke (or just felt off), I reported the bugs in Jira, together with screenshots and reproduction steps.
This phase helped ensure what we designed didn’t just look great, but actually worked the way it was supposed to.
View More of My Work
White Label Marketplace
Scalable and flexible white-label NFT marketplace that any team can launch fast and customize easily.
