Back to portfolioCase study

04 — Rupay · April 2025 – Jan 2026

Rupay
Money Transfer Platform

Rupay is a platform that acts as an intermediary for customer transactions. The platform requires an internal ecosystem to accurately monitor and manage fund flows, especially since transactions involve multiple roles with distinct responsibilities.

My Role
UI/UX Designer
Duration
10 Months
Platform
Website
Team Size
7 People

Overview

The problem
and my role.

The challenge

The platform had to do more than show transaction data. Cashiers, Operations, Finance, Admins, Executives, and Compliance each need visibility into statuses, validations, approvals, and the handoffs between their responsibilities.

My contribution

Designing a user-friendly transfer platform customized for stakeholder requirements. Includes a journal export feature to provide complete visibility into transfer records.

01 — Discover

Stakeholder research

Rupay: Stakeholder research

02 — Define

Transfer journey

Rupay: Transfer journey

02 — Define

Validation and approval flow

Rupay: Validation and approval flow

03 — Design

Design process

Rupay: Design process

03 — Design

Design system

Rupay: Design system

03 — Design

High-fidelity interface

Rupay: High-fidelity interface

Product screens

Website screens

Rupay: Website screens

Product screens

Website details

Rupay: Website details

Process

Design journey

01 — Discover

Research & Empathy

The original project was delivered through stakeholder discussions, requirement analysis, design exploration, and engineering collaboration.

Deliverables

  • PERSONA DEFINITIONS
  • USER INTERVIEW REPORTS
  • COMPETITIVE ANALYSIS

02 — Define

Problem Framing

Here the problem framing was delivered through stakeholder discussions. The transaction-success flow shows the relationship between data input, system validation, compliance review, and operational decision making.

Deliverables

  • PROBLEM STATEMENTS
  • USER FLOW MAPS

03 — Design

Design Process

The design process started with stakeholder requirement analysis, followed by role mapping, user-flow definition, low fidelity, and handoff preparation. The goal was to make the internal platform understandable before moving deeper into detailed UI production.

Deliverables

  • FIGMA DESIGN SYSTEM
  • LO-FI PROTOTYPES
  • HI-FI PROTOTYPES

04 — Deliver

Testing & Handoff

The prototype was reviewed to identify usability issues, unclear information, and unnecessary friction across the main user journey. Based on the feedback, I refined the hierarchy, wording, interaction states, and transaction feedback to make the experience easier to understand. For developer handoff, I prepared detailed designs covering component behavior, different UI states, spacing, interaction rules, and edge cases.

Deliverables

  • USABILITY TEST REPORTS
  • DEV HANDOFF SPECS

Reflections

What I learned.

The importance of documenting operational logic

The current design documentation gives Rupay a clearer foundation for an internal role-based transaction platform. The portfolio evidence shows how the product moves from business needs into role mapping, flow definition, screen planning, and handoff structure. My key learning from this project is the importance of documenting operational logic before polishing the interface. For a financial platform, the value of design is not only visual clarity, but also how well the interface supports accuracy, role responsibility, validation, and auditability.