Scaling consistent payment systems

Redesigned and scaled Efí Bank’s Payment Link experience, improving visual consistency, usability, and cross-platform performance across web, mobile, and tablet.

Year

2024

Duration

12 weeks

Role

UI designer

Overview

Efí Bank (formerly Gerencianet) is a Brazilian digital bank and financial technology (Fintech).

Problem statement

Efí Bank recently upgraded to version 7, but key features were still on the outdated v6, causing inconsistencies and technical debt.

Principal results

Principal results

13

flows (web, tablet and mobile) were designed and delivered

+

Visual update of all Payment Link product emails.



Visual update of all Payment Link product emails.



3

Products were convered in this batch of updates

 

Main goals

Main goals

Flows and e-mails

Update the payments link and your e-mails to v.7 (visual standards, components, interactions, colors, information architecture, etc).



New components

Build the entire flow and new components in Figma for alignment purposes and ease of access for the design team.



Build the entire flow and new components in Figma for alignment purposes and ease of access for the design team.



Web and mobile

Create flows and components in web and mobile versions (v.6 was web only).



Create flows and components in web and mobile versions (v.6 was web only).



Handoff process

In handoff process, ensure quality of implementation, considering Pixel perfect of the designed layout.


In handoff process, ensure quality of implementation, considering Pixel perfect of the designed layout.


UX process

I followed a non-linear process, so I had the flexibility to work on several phases simultaneously. We had some surprises during the ideation phase, which I will explain below.

Ideation process

I was tasked with designing and prototyping based on the current payment link content. I analyzed our e-mails, payment link flows, and competitor flows, while also mapping the system-generated e-mails.









I held several meetings with stakeholders, PMs, tech leads and CX to validate the ideal flow.




New layout (email and flows)

Now understanding the flow to be updated and the complexity of the work, I started hi-fi prototyping to save time for delivery. This was the first proposal presented:

Email redesign

As expected, the redesign extended to the Payment Link emails. Several presenting sessions involving design, CX and PM teams were held to validate the final proposal.

Flow evolution

Naturally, new screens were added to the flow (payment confirmed, denied, canceled, etc).

Deliverables (web, tablet and mobile)

Handoff

The third month was specifically about meetings with the development team. After the implementation, I finalized my process by applying 2 stages of Design review to analyze whether there were points that needed adjustments, ensuring Pixel perfect delivery.

Key Learnings & Insights

Keeping alignment with PMs and devs was essential to adapt to scope changes and handle surprises like the tablet version efficiently.

Starting with process and organization first, using component-based flows, helped scale and reuse designs across multiple features.

Design review remained essential, even under tight deadlines, ensuring quality despite new products being added during the process.

Learning about the e-commerce payment model clarified key concepts, and early delivery respected dev team workflows and timelines.


Let's transform ideas into real solutions?

Let's transform ideas into real solutions?

Let's transform ideas into real solutions?

Create a free website with Framer, the website builder loved by startups, designers and agencies.