BerryBuck: Revolutionizing Banking-as-a-serivce
BerryBuck is a single platform for businesses to accept online payments effortlessly, manage transactions and run their business smoothly.

Take a quick look at the solution designed

Tools used:
Figma, Whimsical, Google meet
Deliverables:
Web interfaces, Information architecture, Prototype
PROJECT OVERVIEW
Introduction
In the ever-evolving landscape of financial technology, the need for seamless, user-friendly banking solutions has never been greater. Recognizing this demand, I embarked on a journey to design a groundbreaking Banking as a Service (BaaS) web application.
This case study delves into the meticulous process of studying the market, identifying essential features, and crafting an intuitive user experience that sets our platform apart.
MY ROLE
What I did
Being the only designer, I was pretty much responsible for everything: research, prototyping, visual designing, and usability testing.
DESIGN PROCESS
Let's dive into how this solution was achieved
UNDERSTANDING WHAT & WHO WE WANT TO BUILD FOR
Market & User Research
Before diving into design, thorough market research was conducted to gain insights into existing BaaS platforms and discern user expectations. Analysis of competitors such as Adyen and Square provided valuable benchmarks, while user surveys and feedback highlighted pain points and desired functionalities.
Why the need to analyse our competitors?
Answer is simple! We needed to understand what experiences people were used to already in the market.
Carrying out user interview
8 participants were recruited for this exercise including Online vendors, Freelancers and store owners. Questions were asked around;
Business overview
Current banking practices
Financial needs & goals
Integration & workflow
User experience and security

Insights gotten from the research
Users expressed strong preference for integrating tools like invoicing to enable them experience collection even better and improve business performance
Users also expressed concerns for security
Some user expressed the need for flexible APIs to create wallet integration for their financial solution
Users expressed keen interest in customizing payment experience for their customers.
Some users also desired a flexible way to perform transaction out of their account.
INFORMATION ARCHITECTURE
Identifying Essential Features
Armed with market insights, the next crucial step was identifying the core features essential for our BaaS platform.
Through collaborative brainstorming sessions and stakeholder consultations, a comprehensive feature set was outlined, prioritizing functionality, security, and user experience.
The essential features are listed below along with the pain points they help to solve. In respect to business objectives, the features were divided into two categories;
Very important to have
Payment link: Enable customized payment experience for customers
Invoice: Gives invoicing functionality without 3rd-party integration
Sub-accounts: For wallet creation for other fintechs
Payout: Enable businesses withdraw money to their settlement account
Transfer: Provide flexibility to transfer money to preferred accounts
Transaction: Get collection and payout history
Analytics
2-factor authentication: Solves for better security
Nice to have
Product page
Terminals

Feature designs
With a clear understanding of user needs and market trends, feature design commenced. Each feature was meticulously crafted with a user-centric approach, focusing on simplicity, accessibility, and efficiency. The design process involved iterative prototyping, user testing, and feedback integration to refine and optimize each element.
Each feature flow was carefully designed over sprints. meaning I designed one feature per 2 weeks sprint conceptualizing and iterating on design decisions.
Payment link
This enable business owners and vendors to customize payment experience for their customers.
Invoice
In-built invoicing feature built to help businesses get paid faster.
Payout
This solution will enable businesses transfer money to their settlement account.
Analytics
Businesses can get an overview into how they are doing.

Security
To ensure a high level of safety for businesses, the implementation of 2-factor authentication was explored.
Key learnings on this project
Prototype: Designing a detailed interface flow is essential but creating a working prototype will go a long way in enabling your developers know more about the functionality and interactions.
Engineering Collaboration: Early developer involvement ensured designs were implementation-friendly, minimizing delays and accelerating time-to-market.