Most merchants came simply to withdraw funds—but even that basic task was confusing. The dashboard had grown fast, feature by feature, without a clear structure. New users felt overwhelmed. Existing users struggled to find what they needed. And internally, it was becoming harder and harder to scale. As one developer put it:
“We’ve reached the point where every change breaks something.”
At the same time, new regulations like MiCA were approaching fast. We needed to rethink onboarding, verification, and compliance without slowing down the product.
We needed to redesign the dashboard to be:
As Senior UX Designer, I led the dashboard redesign. My responsibilities included:
I also worked closely with the Head of Product to shape priorities and advocate for long-term improvements, not just quick fixes.
The old onboarding flow was dense and discouraging. Users were asked to make complex choices without guidance. We simplified the entire experience:
But we also uncovered a major flaw: verification wasn’t skippable.
If a user lacked one document (like a company structure), they’d leave to find it. When they came back days later, they'd discover more documents were needed. That process could take 30+ days.
So we restructured the flow to:
We had a motto: “Skip is good. Pre-fill is god.” We meant it.
With MiCA regulations incoming, we redesigned verification to:
Compliance wasn’t just about meeting the standard—it was about making the process understandable and survivablefor merchants.
Previously, developers were stuck waiting for business owners to complete long verification flows. So we redesigned the onboarding structure:
This change allowed technical and business teams to work in parallel, helping merchants go live faster and reducing internal bottlenecks.
We realized most users only came to withdraw. So we asked: what if we gave them more ways to use their crypto?
We introduced:
These tools helped turn idle balances into active value.
One of the most loved changes was simply making the dashboard feel more human.
Old logic: everything was driven by IDs—wallet hashes, order numbers, references.
New logic: names, emails, and real-world context came first.
You could now:
It felt less like querying a database, more like helping a real person.
As we redesigned the dashboard, we documented repeatable patterns, rules, and components. This became the seed of the CoinGate design system—a shared visual and interaction language used across:
This system improved consistency, reduced design/dev time, and helped unify the entire product ecosystem.
This wasn’t about making the dashboard prettier.
It was about making it clearer, faster, and more respectful of the people who rely on it every day.
We didn’t just fix usability issues—we helped CoinGate scale.
The new dashboard empowered teams, sped up integration, and gave merchants reasons to stick around.
It became a product we could finally grow on top of—and a system we could trust going forward.