Stripe Merchant Dashboard

Business impact

The redesigned Merchant Dashboard drove a 40% improvement in task completion rates and a 35% reduction in navigation-related support tickets. Merchant satisfaction rose from 71% to 92%. The design system was adopted across 12 product teams, cutting design-to-dev handoff time by 50%. New merchant activation improved by 28% in the first quarter after launch.

Rethinking the merchant experience

Stripe's Merchant Dashboard is the primary interface for millions of businesses to manage payments, analyze revenue, and understand their financial health. Over five years of organic growth, different teams had built their own UI patterns independently, and the result felt like multiple products stitched together rather than one cohesive tool.

Navigation was fragmented, new merchants faced a steep learning curve, and support tickets about basic navigation had increased 60% year-over-year. New merchant activation was trending downward because people simply couldn't find what they needed.

I led a 9-month initiative spanning multiple product teams to redesign the entire dashboard. This wasn't about visual polish — it was about rethinking how merchants interact with their financial data at every level of complexity.

Context

We conducted 40+ merchant interviews across segments, from solo founders processing their first transactions to enterprise finance teams managing complex multi-currency operations. Three themes surfaced in nearly every conversation.

First, information overload. Merchants told us they only cared about 3–4 metrics daily, but the dashboard presented 20+ with no clear hierarchy. Second, the navigation didn't match how merchants actually think. Revenue, payouts, and disputes lived in separate sections despite being part of the same mental workflow. Third, there was no progressive disclosure — new merchants saw the exact same interface as power users, which meant neither group was well-served.

Exploring progressive disclosure

The core insight was that merchants at different stages need fundamentally different experiences, but splitting them into separate products would fragment Stripe's ecosystem. I explored several directions: role-based dashboards that adapted to business type, customizable widget grids that let merchants build their own view, and an AI-driven layout that surfaced relevant data automatically.

We landed on a progressive disclosure model. New merchants see a simplified view focused on their first payout and recent transactions. As their business grows, the dashboard gradually introduces more sophisticated tools — revenue analytics, dispute management, multi-currency controls. The interface grows with the merchant rather than overwhelming them on day one.

Building the design system

Supporting the redesign at scale required a component library that could enforce consistency across 12 product teams while still giving each team room to address their specific use cases. I built 120+ components with full documentation and usage guidelines.

The hardest decisions were around data visualization. I designed composable chart components with shared interaction patterns and a unified color system for data visualization across all product areas. Every component was built accessibility-first, meeting WCAG 2.1 AA compliance. The responsive primitives work across desktop, mobile, and embedded contexts. Critical because so many merchants check their dashboard on the go.

Final design

The final dashboard centers on contextual actions that appear based on merchant state. If a payout fails, the resolution flow surfaces inline rather than hiding in settings. The adaptive layout learns from merchant behavior, promoting the tools and data each merchant uses most while keeping everything else accessible through consistent navigation. The result is an interface that feels personal without requiring any manual configuration.