<aside> 📌 Disclaimer: All WabiPay assets used for this project are purely for illustrative purposes only and do not reflect the intentions of WabiPay or any of its affiliates.

</aside>

Why WabiPay Platform?

WabiPay is the tool that is incorporated into Wabi (read case study) to facilitate and accelerate payment systems within the ecosystem.

method.png

My Role

I was part of the team focused on this project and as the only UX/UI designer I defined user task flows, created wireframes, prototypes and mockups.

We worked based on a CUBI scheme that allowed us to have different contexts and perspectives mapped.

The result of this project was the successful exit of WabiPay as a payment and collection tool.

<aside> 🤝 Team
1 UX/UI designers | 3 Devs | 1 PO / 1 BA

</aside>

<aside> 🛠 Tools
Sketch | Zeplin | Lottie

</aside>

<aside> 📆 Duration 10 sprints

</aside>

The Task

Wabi had started the expansion process throughout Argentina, incorporating a platform for payment systems from an external provider, however, this dependency meant that in case of system failures, resorting to documentation and / or waiting for support help would delay the Checkout of the entire purchase in Wabi, causing a high rate of frustration and abandonment of tasks by users.

🎯 The purpose was to carry out the development of a virtual wallet that would be part of the ecosystem in Wabi.

According to this purpose, the following functions were distinguished:

Payment. Which could be divided into paying a friend or a merchant.

Charge. Designed for merchants and bottlers.

Withdraw. Designed so that merchants could get their money for the sales made.

splash.png

The preconditions that I had to take into account were: