Transaction history is one of the most visited sections of the financial service
Users regularly log in to it to:
check charges
find the required transaction
track regular payments
download or check transfer details
monitor personal expenses
Despite its high frequency of use, the current interface caused difficulties when searching for transactions and analyzing expenses. The project aimed to redesign the transaction history workflow for web and mobile platforms.
Role
Was responsible for the full cycle of redesigning the transaction history scenario: analyzing user behavior, formulating hypotheses, designing the solution, and interface design.
UX audit of the current solution;
conducting discovery
analysis of user scenarios
designing the new section structure
creating user flows
designing desktop and mobile interfaces
developing design system components
Area of responsibility:
Product problem
The transaction history was one of the most frequently used screens in the product, but users regularly faced difficulties:
it was difficult to quickly find the required transaction
filtering was overloaded and barely noticeable
users lost context when viewing a long list of operations
the interface scaled poorly for different scenarios
the mobile version did not allow for effective work with filters and operation details
This affected not only the user experience but also the perception
of the transparency of the financial service
Project goals
1. Business Goals
2. Product goals
3. UX Goals
reduce the number of support requests related to searching for transactions
improve the convenience of financial control
increase user trust in the service
improve the usability of one of the most visited sections of the product
reduce transaction search time
simplify the filtering scenario
improve the readability of the transaction history
make the scenario unified for web and mobile
reduce cognitive load
increase the speed of key actions
improve visual hierarchy
make the interface more predictable
_________________________________________________________________________________________________________________________
_________________________________________________________________________________________________________________________
Research
/ UX Audit:
Allowed to identify problems in navigation, visual hierarchy, and interface structure
/ User scenario analysis:
Helped define the main actions within the transaction history section
/ Competitive research:
Solutions of banking and fintech products were studied to compare approaches
to filtering, searching, and displaying transactions
/ Interviews and feedback:
Recurring user issues
and behavior patterns were analyzed
What was important to understand
Before starting the design, it was important to determine:
which scenarios are most important to users
what problems occur most frequently
what actions users perform regularly
where exactly users lose time
which parts of the interface create overload
Main user pain points
1. It's difficult to find the needed operation
2. The filters were overloaded
A large number of parameters complicated the interaction
and created a feeling of overload
__________________________________________________________________________________________________________
3. There was a lack of visual structure
4. Mobile scenario was inconvenient
With a large number of transactions, users spent too
much time searching for the right payment
The list of operations was perceived as a monotonous data stream
without accents or priorities
On mobile devices, users had to perform
too many actions to filter and view transaction details
___________________________________________________________________________________________________________
__________________________________________________________________________________________________________
JTBD
When
I want to quickly filter and recognize the required transaction
I want to see a clear structure of operations
I want to perform key actions with one hand and without complex navigation
When I analyze expenses
When I use the mobile application
To control your finances without unnecessary stress
To quickly understand where the money is going
So as not to waste extra time
I need to quickly check or find a specific transaction
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
Hypotheses
Hypothesis 1
Hypothesis 2
Hypothesis 3
Why we calculated it this way:
If you simplify the filtering system, users will be able to
find the necessary operations faster
Why we calculated it this way:
filters were visually overloaded
users rarely used advanced parameters
key scenarios required too many actions
transactions looked identical
important data lacked visual priority
users spent more time scanning the list
the current mobile flow contained extra steps
interaction with filters took too much time
If you improve the visual hierarchy of the list, users will scan the information faster
Why we calculated it this way:
If you adapt the mobile scenario for quick actions, users will be able to
work more efficiently with the transaction history on the go
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
Trades off
During the design process, it was important to maintain a balance between:
execution speed of core scenarios
filtering flexibility
interface scalability
Initially, the option of displaying all filters
simultaneously was considered. However, this approach overloaded the interface and complicated
quick user scenarios
As a result, the filtering was split into quick filters and advanced parameters.
This made it possible to preserve the functionality without overloading the interface.
Information architecture
The section structure has been rebuilt:
filters have received a more logical grouping
core actions became more prominent
transaction details were moved to a separate, clear scenario
the transaction list became easier to scan
User flow
The user opens the transaction history and:
views the transaction list
uses quick filters
finds the required operation
opens transaction details
The goal was to reduce unnecessary steps and make the scenario
as straightforward as possible
Iterations
First concept
What the review showed
In the final decision
In the initial version, the filters occupied a separate large area of the interface
and contained a large number of parameters at the same time. This approach made
the interface functional, but visually heavy
During the analysis, it became clear that users spend too much time interacting with the filters. The interface looked more complicated than it actually was
main filters have become more compact
secondary parameters were separated
visual hierarchy was strengthened
the list of transactions became easier for scanability
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
UX solutions
1. Simplifying the filtration
3. Mobile UX optimization
2. Improving the visual hierarchy
reduce interface clutter
speed up core scenarios
maintain flexibility for advanced users
unnecessary actions were reduced
improved work with bottom sheet
simplified access to filters
improved readability of the list
typography
information priorities
spacing
element states
operation type
amount
status
date
category
Filters were divided into quick and advanced. This allowed:
In the mobile version:
For the list of operations, the following have been redesigned:
Now users can distinguish faster:
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
Desktop and mobile adaptation
1. Desktop
Mobile
improved table structure
simplified navigation
added quick filters
improved display of operation details
enhanced readability of large data volumes
redesigned the transaction viewing scenario
simplified access to filtering
improved one-handed interaction
adapted the visual hierarchy for small screens
___________________________________________________________________________________________________________
Efficiency assessment
After the redesign, the main focus was on:
The key performance indicators were:
After the redesign, the scenario became:
execution speed of key scenarios
ease of finding operations
reduction in number of errors
reduction of support load
reduction in inquiries regarding transaction searches
decrease in disputed claims
increase in user engagement
reduction in action completion time
faster
visually simpler
more predictable
more convenient for mobile usage
scalable for future changes
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
Results
−18% in support inquiries regarding transactions and charges
−13% in repeated returns to the transaction history section
+18% increase in the speed of finding the required transaction (by scenario execution time)
+22% increase in the share of self-resolved tasks without contacting support
+15% reduction in cases of doubt regarding the correctness of the displayed data (based on inquiries for clarification)
The use case has become more linear: scan → if necessary
filter → details
Review
This project helped me work more deeply with:
data-heavy interfaces
fintech UX
system design
mobile/desktop consistency
scalable solutions
The main result for me was creating an interface that not only looks cleaner visually but also truly helps users solve their tasks faster