NovaPay was developed to bridge the gap between fragmented banking data and actionable financial oversight. For global teams, managing multiple accounts across different regions often leads to manual errors and "blind spots" in spending. This project focused on creating a unified API-driven dashboard that provides a single source of truth for all corporate assets.
My role
Frontend Lead
Led the development of NovaPay’s web platform from concept to launch, focusing on scalable architecture, performance, and seamless user experience.
Project duration
8 months
Working team
2 frontend developers
1 backend engineer
1 product manager
1 designer
2 content designers
*close collaboration with payments, compliance, and customer support teams
Project highlights
0%
0%
Lower overhead
0%
0%
Faster reconciliation
0k
0k
Pilot asset volume
Security Certified
The Problem
Finance directors at mid-sized tech firms were drowning in "spreadsheet debt." Because their capital was spread across various international accounts and digital wallets, getting a simple total of their current liquidity required hours of manual logins and data exports.
This fragmentation caused more than just headaches; it led to missed investment windows and delayed payroll approvals. Without a real-time view of their cash flow, leadership was forced to make high-stakes decisions based on data that was often several days out of date.
The goal was to build an automated aggregator that didn't just display numbers, but translated complex global banking data into a clear, visual narrative for non-technical stakeholders.
The Solution
We developed the "Command Center," a central hub that utilizes secure webhooks to pull live data from over 50 global financial institutions. This allowed us to present a consolidated view of company health in a single, high-fidelity interface.
The system was built with a "layered" approach: a top-level summary for executives and a deep-dive granular view for accountants. This ensured that whether a user was looking for a broad trend or a specific transaction, the answer was only two clicks away.
The Vision
The long-term vision for NovaPay was to move from a descriptive tool to a predictive one. We wanted to create an environment where the software could flag potential cash-flow shortages weeks in advance, allowing teams to adjust their spending strategies proactively.
By standardizing data formats across different currencies and jurisdictions, we aimed to make global finance feel as localized and simple as a personal checking account. We envisioned a world where "closing the books" became a background process rather than a monthly crisis.
Phase 1: Research & Discovery
I interviewed 12 Fintech operations leads to map out their "manual hell." The research revealed that the biggest pain point wasn't the data itself, but the lack of consistent formatting between different banks. This led us to prioritize a universal data normalization layer.
Phase 2: Execution & Prototyping
During this phase, we iterated on the "Global View" dashboard. We moved away from dense tables and toward high-level visual "cards" that allowed users to drill down into specific accounts. I built high-fidelity prototypes in Framer to test the transition between the global summary and individual transaction logs.
Project Outcomes
0%
0%
Lower overhead
0%
0%
Faster reconciliation
0k
0k
Pilot asset volume
Security Certified
My Impact
As the Lead Product Designer, I was responsible for the end-to-end user experience, from initial stakeholder interviews to the final handoff of the React-based design system. I specifically focused on the "Automated Trigger" UI, ensuring that setting up complex API rules felt accessible even to non-technical users.
Learnings and challenges
What did we learn?
Data consistency is the foundation of trust
High-level automation only works if the underlying data is clean. Standardizing bank feeds increased user confidence in the dashboard's accuracy.
Visual simplicity drives frequent engagement
Users interacted with the platform more often when complex financial data was presented through digestible cards rather than dense spreadsheets.
Challenges we faced
Legacy API limitations forced creative architectural workarounds
Many international banks utilize outdated systems with high latency. We had to implement complex caching layers to ensure the UI remained snappy and responsive for the end user.
Balancing granular detail with executive-level oversight
It was difficult to design a single interface that served both the "deep-dive" needs of an accountant and the "quick-glance" requirements of a CEO without creating visual clutter.
Conclusion
NovaPay taught me that the most powerful "feature" you can give a user is time. By automating the mundane, we didn't just build a dashboard; we gave financial leads two full workdays back every month to focus on growth.
