KKHELGA.
MassPayout MVP for individuals Product strategy UX architecture Release support
MassPay dashboard interface from the Banxe project

At a glance

What changed

The redesign keeps the fintech tone, large headline rhythm, and recognizable illustrations, but introduces clearer reading order and stronger hierarchy.

Turnover impact 35%

Increase in turnover after launching the new MassPayout direction.

Speed 20%

Reduction in smart-contract development time after introducing new flows.

Integrations 30%

More successfully implemented DeFi integrations across the product ecosystem.

Engagement 25%

Increase in user activity during the first three months after release.

Financial processes for both business clients and individual users were not efficient enough to support revenue growth and competitiveness. Payment management felt fragmented, transaction frequency was hard to control, and the experience made acquisition and retention more difficult.

The answer was an expanded MassPayout direction for business clients plus a minimum viable product for individuals. That combination made the payment system more scalable, more usable, and more commercially meaningful.

Process

From research to release

The original case already had a strong process spine. It is preserved here, but turned into a clearer two-level structure: four headline phases and five detailed delivery stages.

High-level flow

Research Analyse Prototype Release

These original phase markers remain, but are easier to scan and understand.

01
Research Framing the payment problem, user needs, and opportunity space.
02
Analyse Defining requirements, market references, and architecture decisions.
03
Prototype Turning hypotheses into testable user flows and product screens.
04
Release Launching, training teams, monitoring performance, and refining the product.

Detailed stages

Delivery map

Stage 1

Discover phase

Development of detailed functional requirements for MassPayout, taking into account the needs of both corporate and individual clients.

  • Information architecture
  • Low-fidelity wireframes
  • Initial flow definition for mass payments
Stage 2

Define phase

Shape the first release around a focused B2B MVP and validate it with selected clients.

  • Interface design for new functionality
  • MVP development for legal entities
  • MVP testing with selected corporate clients
Stage 3

Improvement and adaptation

Use feedback loops to evolve the B2B direction and add the individual-user version.

  • Collect and analyze client feedback
  • Expand MassPayout for individual users
  • Run debugging and refinement cycles
Stage 4

Implementation and training

Move the product into production and support adoption with training materials.

  • Launch the updated version for corporate clients
  • Create manuals and learning materials
  • Train internal teams and end users
Stage 5

Monitoring and optimization

Continue measuring usage and tune the experience based on data and qualitative input.

  • Monitor product performance
  • Collect ongoing user feedback
  • Implement optimization and new improvements

Research layer

Market research and framing

The original page had competitive research and a hand-drawn planning artifact. Here those two pieces become a clearer case-study section instead of getting lost in a long export.

Early hand-drawn wireframe notes for the MassPayout flow

Early wireframes captured the payment structure, fiat and crypto branches, recurring logic, and the main-page rhythm before the UI system was formalized.

Competitive research focused on adjacent payment ecosystems and helped define how MassPayout should balance cross-border transfers, blockchain flows, bulk payments, and more familiar consumer finance behavior.

Benchmark for financial services and online money transfer workflows.

Reference point for blockchain payment gateways and crypto transaction patterns.

Useful comparison for global transfer clarity and international money movement.

Reference for familiar bill-payment and peer-to-peer money transfer behavior.

Product views

From wireframe to interface

The screen selection below keeps the original visual evidence, but presents it as a readable sequence: dashboard, data entry, and bulk-payment confirmation.

MassPay dashboard screen

MassPay dashboard

The central overview screen for upcoming, paid, and draft payments.

Add recipient screen for fiat payments

Add recipient

Structured data entry for personal and payment information in the fiat flow.

Bulk payment confirmation screen

Bulk payment review

A confirmation step that translates complex payouts into a clearer decision point.

Outcome

Results and deliverables

The case closes not just with screens, but with measurable product impact and concrete delivery outputs that supported both launch and post-release learning.

Impact after release

The product direction led to a 35% turnover increase and created a more scalable financial experience across business and individual segments.

The original case also highlights a 20% reduction in smart-contract development time, 30% more successfully implemented DeFi integrations, and a 25% rise in user activity during the first three months after the new functionality launched.

35%

Turnover growth after the MassPayout direction expanded.

20%

Faster smart-contract development through clearer delivery structure.

30%

Increase in successful DeFi integrations.

25%

Higher user activity in the first three months after release.

Deliverables

  • Design layout of the MassPayout interface and a working MVP with core features.
  • Updated version of MassPayout with functionality for individual users.
  • Training materials for clients and internal teams.
  • Full report on feedback, improvements, performance, and user experience.
  • Continuous monitoring and optimization plan for the released product.