Rayan Aleisa
Dispute Management
A product designer focused on translating ideas into practical and beautiful designs that solve real-world problems.
The Tablet version is coming soon. You can view the website on a desktop or mobile. I apologize for this inconvenience.
Digital Wallet & Payout System
Planned and launched a structured in-app wallet with withdrawals, receipt uploads, and transaction tracking.
Worked closely with the Finance and Data teams, and prepared the internal dashboard and future automation roadmap.
Planned and launched a structured in-app wallet with withdrawals, receipt uploads, and transaction tracking.
Worked closely with the Finance and Data teams, and prepared the internal dashboard and future automation roadmap.
My role
My role
Product designer
Product designer
Team
Team
Product designer
Finance team
Data team
Product designer
Finance team
Data team
Timeline
Timeline
29 Sep - Ongoing
29 Sep - Ongoing
The Problem
When we started, the wallet in the app was just a static number — users could see their balance, but:
There was no way to withdraw funds
The only top-up options were Apple Pay and credit/debit cards
Bank transfers weren’t supported, despite being the preferred method for most companies
There was no ability to upload or verify transfer receipts
There was no visible transaction history — especially for withdrawals or top-ups via bank transfers
Users had no visibility into what was pending, completed, or failed
These limitations caused major friction for both users and internal teams, leading to confusion, support tickets, and limited trust in the system.
The Goal
To turn the wallet from a passive number into a fully functioning payment center within the app — giving users full control and visibility over their wallet activity.
To handle this effectively, we split the work into two main phases:
Phase 1 – A fast-launch, semi-automated system
Phase 2 – A long-term, fully automated system using Virtual IBANs
Phase 1
Semi-Automated System
Due to tight timelines and urgent product needs, we focused on launching something that works now, even if the backend wasn’t fully automated.
The goal was to unblock users and start building user trust, while preparing for full backend automation.
In this phase:
Users can request withdrawals directly from within the app
They can upload bank transfer receipts
They receive status updates and alerts (e.g. “Pending”, “Under Review”, “Completed”)
Internally, our team handles transfers and verification manually but in a structured way
From the user’s perspective — it feels automated
From the backend — it’s still manual, but trackable, documented, and aligned across teams
Phase 2
Full Automation with Virtual IBANs (Planned)
We’re preparing to fully automate wallet operations using Virtual IBANs per user, which will enable:
Wallet top-ups via direct bank transfers
Automated transfer recognition and matching
Faster processing and error reduction
Real-time transaction sync
Zero manual intervention
This future state will provide a seamless and scalable experience for both users and internal teams.
Cross-Team Collaboration
This project required heavy coordination with:
Finance Team – to define the manual payout workflow, IBAN validation logic, and approval steps
Data Team – to structure transaction history, define status fields, and build backend audit trails
We held regular syncs to align logic, use consistent language across systems, and ensure the end-to-end experience made sense from both user and operations perspectives.
Wallet Operations Dashboard – Planning & Enablement
Before this project, there was no internal dashboard for managing wallet activity — all workflows were fragmented and handled manually via spreadsheets or DMs.
As part of this initiative:
I led the planning, structuring, and requirements gathering for a new Wallet Operations Dashboard
Worked closely with Finance, Data, and Engineering teams to define:
What the dashboard should show (transactions, statuses, filters, actions)
How statuses should behave (e.g. “Pending Verification”, “Transfer Failed”, etc.)
What tools the team needs to approve, reject, or flag issues
This dashboard became essential for our internal team to handle Phase 1 smoothly and lays the foundation for full automation.
My Role
Defined the entire wallet flow, from user withdrawals to internal processing
Planned and mapped out all UI states, user journeys, toast messages, error states, and pop-ups
Acted as the bridge between Product, Design, Engineering, Finance, and Data
Wrote functional requirements and logic for both the user-facing features and the internal dashboard
Ensured consistency across systems in language, statuses, and experience
Balanced short-term urgency with long-term scalability
Results
Enabled 100% of users to initiate and track wallet actions in-app
Supported internal teams with a clear, centralized system for processing payouts
Reduced manual communication and errors
Increased trust and confidence among users
Created the structure needed to move toward full automation