Gigapay for receiver
Gigapay is an invoice consolidation provider that allows companies to send payments to very small suppliers like influencers. I focussed on improving our account creation process in order to become DAC7 compliant.
- 4 months
- Single designer working with engineering lead
- Requirements from the compliance team
Business case
In the previous system, the minimum amount of information required by the payment provider was asked of the receiver without any kind of verification. Gigapay was in need to step up its compliance together with expanding to new countries in the world. But how to ask for compliance information without causing frustrations?
Initial work
We gathered all the requirements between payment information and legal reporting obligations with the legal team. I drafted an alternative of how the information could be asked and noted down several remarks as to what the system needed to do in order to be compliant.
The challenge
The first challenge in the projects was to collect and understand where the exact compliance question that needed to be exposed during account creation. But once that was done we quickly realised from people that some of the questions where too complex and difficult to answer.
Approach
I introduced several layers of contextual help within the product. Answering all the common questions someone can face.
Introducing a design system
This project was built in 2 phases. First, we used the available components available to us and our goal was to make our tool DAC7 compliant and improve our UX. In the second phase, our goal was to improve user inputs, and accessibility as well as modernising our visual identity. In parallel with phase one implementation, I started a project to build a design system.
Solution
An account creation flow that breaks downs the question into cognitively understood sections such as name, contact, address, and working status. Each page is supported by contextual help and complicated questions are answered directly within the UI. Each input is now fully accessible and the error state is documented with friendly messages.
Learning
Requirements will always be dynamic and projects are always going to be subject to further enhancements. One mistake we did is that after getting a green light from legal and early wireframe testing we went on to build a robust compliance backend. But as we moved forward we had new requirements and new feedback which required us to completely redraw our account creation process together with our data infrastructure. Knowing this I would always advocate for project flexibility.
See also
Other projects
Let's meet
I’m curious to hear about your projects & challenges