Re-designing payment
gateway platform

13000+users
3platforms
10+brands
420+hrs
Start

Intro

Overview of the existing payment gateway platform — a sprawling map of 450+ screens

Redesigning a platform with over 450 screens was a significant challenge. Breaking down major tasks into smaller, manageable sub-tasks and creating detailed to-do lists was essential for clear communication with internal stakeholders and maintaining an organized workflow.

Users were unhappy with the experience

PMs got called directly by customers to ask about where a specific feature was, or certain things could be done.

Non-scalable platform

the existing platform wasn't scalable. Additional features were all added into a top navigation bar where a "more" icon would reveal all sub-menu items.

The platform needed new foundations for IA, UX, UI, and design library that is scalable, flexible, simple, clear, and most of all, understandable.

step 1 of 10

The plan

Weekly roadmap board with detailed UX tasks and to-do lists

Need

Capture all major and minor UX tasks to document progress.

Action

Created a roadmap for every week and added detailed tasks to track the progress + define all steps needed.

Result

Transparent communication with the internal stakeholders

A solid foundation for long-term UX and UI task management within the team.

step 2 of 10

Stakeholder interviews

Need

Getting more information about everything. (needs, short term and long term plans, team dynamics, customer feedback)

Action

16+ hours of calls with the internal team (PM, PO, Dev). Identified user types, account types, and actions taken by each.

Result

A comprehensive documentation of existing flows, with additional notes, flowcharts, and details. This became the foundation for the entire project moving forward.

More on step 2

Understanding user profiles / personas

User profiles and personas mapped with their actions and requirements

Need

Listing actions and requirements for each user profile / persona.

Action

Aligning with the PMs, understanding the scope of actions

Result

Inventory of actions in order of user profile hierarchy

step 3 of 10

Competitor analysis

Competitor analysis board comparing flows, screens, features and patterns

Need

Understanding the common patterns, industry best practices, primary competitors, UX & UI decisions.

Action

Comprehensive competitor analysis of flows, screens, features, patterns.

Result

A comprehensive report of competitors, capturing their strengths, weaknesses, user flows, interactions which later informed improvements areas.

step 4 of 10

Benchmark report

Benchmark report summarising flows with pros and cons

Need

The board of benchmark flows was too big and too difficult to follow. I needed a clean, neat summary.

Action

Created a report summarising flows, assessing pros and cons, to summarise all of the findings.

Result

It saved us a lot of time and i was able to use this report as a reference point for certain decisions - going back and forth between pros and cons of every option i iterated.

step 5 of 10

Content audit

Content audit board covering the full platform inventory
Content audit — screens grouped by colour-coded categories
Content audit — detailed screen-by-screen inventory
410+screens

Need

The board of benchmark flows was too big and too difficult to follow. I needed a clean, neat summary.

Action

Created a report summarising flows, assessing pros and cons, to summarise all of the findings.

Result

It saved us a lot of time and i was able to use this report as a reference point for certain decisions - going back and forth between pros and cons of every option i iterated.

step 6 of 10

Deconstructing the existing platform

Deconstructed merchant details screen broken into content blocks
Inventory list of must-haves for the most important screens

Problem

The main problem was the hierarchy of content and confusing information architecture.

Action

Deconstructed the most important screens (such as the merchant details screen)

Created an inventory list of must-haves for the most important screens.

Result

This exercise set the tone for the upcoming tasks and revealed that the entire platform could be streamlined into two interchangeable templates. I identified that only two templates were needed to support the primary user actions and the most common interactions:

  • A summarized view for content categories (e.g., transactions, merchants, customers).
  • A detailed view for individual content items within a category (e.g., a single transaction, merchant, or customer).
step 7 of 10

Rebuilding the IA

Screens grouped into colour-coded categories to rebuild the information architecture
Written descriptions compiled for each colour-grouped screen cluster

Problem

The main problem was the hierarchy of content and confusing information architecture.

Action

Deconstructed the most important screens (such as the merchant details screen)

Created an inventory list of must-haves for the most important screens.

Result

This exercise set the tone for the upcoming tasks and revealed that the entire platform could be streamlined into two interchangeable templates. I identified that only two templates were needed to support the primary user actions and the most common interactions:

  • A summarized view for content categories (e.g., transactions, merchants, customers).
  • A detailed view for individual content items within a category (e.g., a single transaction, merchant, or customer).
step 8 of 10

User testing / card sorting

Card sorting session results — groupings mapped against team mental models

Problem

Having compiled descriptions for the colour-grouped screens, i had to find a way to asses the effectiveness and intuitiveness of the groupings.

Action

Facilitated card sorting sessions with the internal team to assess how well the groupings align with their mental models.

Result

Identified Common Themes and discrepancies in groupings.

Improved Labeling

Gathered insights for navigation improvements.

step 9 of 10

The IA

The new information architecture — left panel navigation divided into three sections

Problem

The existing navigation

  • Grouped all content categories in a single location,
  • lacked a clear structure,
  • Did not adhere to a proper UX structure.

Action

Organized menu items based on relevance, user profiles, and insights from card sorting results.

Result

Enhanced content discovery: By dividing the left panel into three sections, I developed a scalable solution. The top section is visible to all users, the second section is designated for administrative accounts, and the final section is reserved for platform-related actions, which is aimed to reduce the cognitive load.

step 10 of 10

UX Anatomy

Table view

UX anatomy — the table view template

Preview

UX anatomy — the preview panel template

Detail view

UX anatomy — the detail view template

In terms of UX, these 3 screens cover %80 of the platform requirements. As previously mentioned, the need was to have

  • A summarized view for content categories (e.g., transactions, merchants, customers).
  • A detailed view for individual content items within a category (e.g., a single transaction, merchant, or customer).
UX

Anatomy in action

UI

The look & feel

Styleguide

Colours

Styleguide — the colour palette

Typography

Styleguide — the typography scale

Iconography

Styleguide — the icon set
Design system

Navigation components

Design system — navigation component variants and states Design system — compact navigation variant
Before / after
Main dashboard before the redesign Main dashboard after the redesign
Detail dashboard before the redesign Detail dashboard after the redesign