Paynet Dashboard.
Making complex payment operations manageable.
We redesigned the dashboard for Paynet’s payment system serving businesses and dealer networks. Turnover tracking, taking payments, recurring instructions, cancellation and refund requests come together in a clear, consistent interface for daily use.
Dashboard
Need.
Paynet began as a system managing collections between Arena Bilgisayar and its customers. As it became an independent fintech company, the product expanded and the team continued developing collection models beyond conventional payment methods.
The ideas were strong, but the existing interface did not make them understandable. Transactions, states, requests and reports were spread across disconnected screens, limiting the value of the product through a difficult user experience.
Recurring payment request
Payment request
Design approach.
We rebuilt the dashboard around core tasks rather than simply refreshing its appearance. Turnover, transaction activity and quick payment collection share an overview, helping users assess the day and begin important tasks directly.
We divided one-off and recurring payment instructions into clear steps for customer, amount, validity and frequency. Filters, status labels and structured tables organise reports, cancellation and refund requests, and notifications.
Colour communicates transaction states and priorities, not just visual distinctions. Shared typography, tables, forms and status components create a consistent product language that can accommodate new functions.
Transaction list
Cancellation and refund requests
Notifications
The work.
The B2B experience turns unfamiliar payment methods and extensive financial operations into clear workflows. Users can move from summaries to detailed transactions, and from requests to outcomes, within one interface logic.
The dashboard was central to our six-to-seven-year direct design collaboration with Paynet. We supported its development over that period with new UX and UI solutions as needs changed.
