Concept project · Internal Tool · SaaS B2B · Fintech
Payment Operations Console
A B2B tool for payment operations teams to manage failed transactions, prioritise issues and decide quickly what to do next.
Role
Product Designer
Year
2026
Overview
Payment Operations Console is a tool for payments operations teams who deal with problematic transactions every day. It helps them move from spotting an issue to taking action and tracking the result, in a structured and calm way.
Problem
When a payment fails, teams need to understand what happened, decide what to do, act quickly and follow the outcome. In most tools this process is fragmented. The data is there, but nothing is prioritised, actions are not guided and the next step is unclear. The result is slower resolution and lost revenue.
Design approach
Instead of designing another dashboard, I designed a decision flow. The interface follows the way people actually work: Detect, Investigate, Decide, Resolve, Track. Every screen exists to reduce uncertainty and point the user to the next action.
Core structure
Issues queue
Prioritisation first. Users see high impact issues immediately and can filter by urgency.
Investigation panel
Fast decisions without switching context. The relevant transaction data lives in a single panel.
Case detail
A dedicated space for complex cases that need deeper analysis before deciding.
Key design decisions
From data to decisions
The interface guides actions instead of only displaying information.
The action panel at the centre
Decisions happen in one place, always supported by context.
Prioritisation in the queue
High impact issues stand out at a glance.
Two levels of navigation
A side panel for speed, a detail page for depth.
A simple action system
Primary actions are always visible, secondary ones are grouped.
Outcome
The result turns raw failed transaction data into a clear next step: priorities surface by impact, each decision is guided and every outcome can be traced. It reads as a tool for deciding, not a screen full of numbers.
How I'd measure success
If this shipped, I'd look at time to resolution per failed transaction, the share of high priority issues handled from the queue, how often decisions get reversed and how much revenue is recovered. I'd start with a usability test on the Detect to Resolve path, to see whether the prioritisation really changes what teams handle first.
Learnings
Operational tools need a different mindset than dashboards. The challenge is not showing more data but helping people understand what to do next. Clear actions and visible state changes are what make the design support real work.