Overview
Designed a payout experience that helps merchants understand how much they’ll receive, when they’ll receive it, and why payouts differ from sales.
The project focused on reducing ambiguity around money movement by making payout states, deductions, and settlement timelines more visible and easier to follow.
Role: Product Designer
Focus Areas: Financial UX · System Clarity · Operational Transparency · Trust Design
Key Contributions
Reframed the problem as a visibility and trust gap rather than a reporting issue
Designed state-based payout visibility across processing, available, in transit, and on hold states
Introduced a payout lifecycle system to explain how money moves from sales to settlement
Structured the experience using progressive disclosure from overview → payout → transaction level
The Trust Gap
Unlike traditional payment processors like Stripe or Razorpay, a Merchant of Record (MoR) platform handles taxes, refunds, compliance, and settlement before transferring the final payout to merchants.
This additional operational layer creates a visibility gap between what merchants earn and what they finally receive, making payouts feel difficult to track and trust.
The issue was not inaccurate payouts. It was the lack of visibility into how money moved through the system.
Key Insight
Merchants do not just need a final payout amount. They need visibility into how sales transform into net payouts across every stage of settlement.
The experience was designed to expose payout states, timelines, and money movement in a way that feels understandable and predictable instead of operationally invisible.
Designing Financial Visibility
The overview experience was designed to answer three important questions upfront:
Where is my money right now?
What payout am I receiving next?
What happened in previous payouts?
Instead of relying on a single payout number, the system breaks settlement visibility into multiple layers that help merchants understand money movement more clearly.
Where Your Money Is
Your Next Payout
The section highlights the exact payout amount expected in the next settlement cycle along with the expected payout date, included transaction count, and payout period.
This helps merchants understand what contributes to the next payout before the transfer is initiated instead of waiting for the final settlement amount to appear unexpectedly.
Tracking Recent Payouts
A structured payout history table gives merchants quick visibility into previous settlements, deductions, payout status, currencies, and transferred amounts.
Users can also drill deeper into individual payouts for reconciliation and transaction-level verification when needed.
Bringing Everything Together
The final overview combines payout states, upcoming settlements, and payout history into a single operational dashboard that helps merchants quickly understand both their current financial position and payout activity over time.
Understanding Individual Payouts
The payout detail experience connects every payout back to the transactions, deductions, refunds, taxes, and reserves that contributed to it.
Instead of presenting a final payout amount without context, the system provides a transparent breakdown of how money transforms across each stage before settlement.
Payment & Notification Settings
Payout settings were designed to remain simple despite the operational complexity underneath. Users can manage payout schedules, thresholds, bank accounts, currencies, and notification preferences through a structured and easy-to-follow configuration flow.
Instead of exposing dense financial settings all at once, configuration options are grouped contextually so merchants can quickly understand what they are changing and how it affects future payouts.
What I’d Do Differently
Multi-Currency Settlement Flows:
Explore how exchange rates, conversion timing, and regional banking differences affect payout visibility and reconciliation across international merchants.Failed Payout Recovery:
Design clearer recovery flows for failed transfers, invalid bank details, and retry scenarios to reduce operational confusion during payout failures.Reserve & Hold Transparency:
Provide better visibility into rolling reserves, payout holds, and compliance-related delays so merchants can understand why funds are temporarily blocked.Merchant-Scale Adaptability:
Adapt the experience based on merchant size and operational complexity. Solo founders and finance teams often require very different levels of detail and reconciliation support.Advanced Reconciliation Workflows:
Expand transaction traceability with accounting-focused tools like exports, filtering, bulk actions, and deeper payout auditing capabilities.
Reflection
This project reinforced that designing financial systems is less about exposing more data and more about helping users understand how money moves.
The most important shift in thinking came from treating payouts not as isolated transactions, but as a connected operational system with states, timelines, and trust dependencies.
Working within a short assignment timeline also pushed me to prioritize clarity of reasoning and system structure over surface-level polish.
