Netevia
Designing money movement worth trusting
Product designer in a team: two years across the whole Netevia Business platform. This case focuses on my four most recent flows, from discovery to release.
- Role
- Product Designer (Team)
- Timeline
- Sep 2022 – May 2024
Context & Problem
Netevia Business was already a live, trusted payments platform, so this wasn’t a blank canvas. I added AI-assisted actions, bulk payments and stronger dispute handling without breaking patterns customers relied on. Each feature started at the platform level, then narrowed to exact screens, states and edge cases, so it felt native, not bolted on.
This case covers four flows: Netevia AI, Batch Transfer, Security/2FA, and Dispute.
Results
Many flows,
one consistent experience
A deep dive into four flagship flows inside Netevia's B2B payments platform — the AI assistant, bulk payments, two-factor security, and dispute resolution — and the UX decisions that made a complex financial product feel simple and safe.
1 card, 0 security shortcuts
Netevia AI transfers end at the same confirmation card and 2FA as manual ones.
20 payments, 1 flow
Batch transfers by manual entry or CSV upload, with inline validation and review.
2 factors, 0 dead ends
2FA by SMS or authenticator app, with recovery paths.
4 statuses, 1 glance
Status counts and a timeline show where every dispute stands.
Flows
Flow 01 — Netevia AI
- Flow 01 — Netevia AI
- Flow 02 — Batch Transfer
- Flow 03 — Security / 2FA
- Flow 04 — Dispute
Netevia
Many flows,
one consistent experience
Context & Problem
Netevia Business was already a live, trusted payments platform — this wasn't a blank canvas. The work was about introducing new flows and features on top of an existing system: extending it with AI-assisted actions, bulk payments, and stronger dispute handling, without breaking the patterns customers already relied on.
Each addition started broad — what does this feature need to do at the platform level — and only then narrowed down to the specific flow: the exact screens, states, and edge cases that made it feel like a native part of Netevia rather than a bolt-on. This case study walks through that process for four flagship flows: Netevia AI, Batch Transfer, Security/2FA, and Dispute. The sections below follow that path for each flow, from platform-level need to the final screen.
Netevia
Key Pain Points
No safety net for AI-initiated actions
Netevia AI could execute real transfers from a chat prompt, but there was no step between intent and execution — every fast path was one misfire away from breaking trust.
One-at-a-time flows that don't scale
Batch payouts had no dedicated flow, so every payroll run or vendor cycle scaled linearly with the number of recipients.
Dead ends instead of a way forward
A code that never arrived, a session that expired mid-verification, or a dispute frozen at “Under Review” all read the same way to a user: their money is stuck, with no next step in sight.
User flow
How money moves across
the core payment flows
- Decision (code validity)
- Screen / page
- User action (button / click)
- Confirmation / system state
- Completed / success state
Every flow in this diagram starts from the same place — Payments — because that consistency is the point: whether someone opens Netevia AI, uploads a batch of vendor payments, or gets stopped for a 2FA check, the pattern for confirming, reviewing, and recovering from errors stays the same. Netevia's job doesn't end at initiating a transfer — it ends when the money has actually, safely arrived. Disputes follow their own lifecycle and are covered separately below.
Flow 01 — Netevia AI
AI that acts —
without skipping security
Problem
Users needed a faster way to move money than clicking through multi-step forms — but a chat interface that can execute real transfers is a UX minefield. Every action it takes needs to be reversible, confirmable, and auditable, or trust breaks immediately.
UX approach
- Every AI-initiated transfer stops at a confirmation card that restates amount, recipient, and account in plain language before anything executes.
- Money-moving actions route through the same 2FA step as manual transfers, so the assistant is never a shortcut around security.
- Each AI action is logged with the original prompt and its result, so any transfer can be traced back to the request that started it.
Flow 02 — Batch Transfer
Paying twenty vendors
shouldn't take twenty clicks
Problem
Business customers paying multiple vendors, contractors, or employees were forced through the single-recipient transfer flow one payment at a time — slow, error-prone, and painful at any real scale.
Flow 03 — Security/2FA
A second factor
that never dead-ends
Problem
Shown at mobile width — all states fit in one row for easy comparison.
Two-factor authentication is where good products lose users. When verification fails and the only response is a plain error message, a security check turns into a support ticket.
- SMS codes get their own dedicated confirmation screen with clear resend and time-remaining affordances, so a slow code is a known wait, not a dead end.
- Failure and expiry states are written and designed as recoverable, not punitive — the retry path is always one tap away, never a redirect back to square one.
- The same 2FA pattern is reused everywhere money moves — manual transfers, AI-initiated ones, batch payments — so trust in the pattern compounds instead of resetting per flow.
Flow 04 — Dispute
Making ‘where's my money’
A timeline, not a mystery
Context & Problem
A disputed charge is one of the more anxiety-inducing moments in a business owner's day — money is frozen, the reason was filed by someone else, and the real question ("what happens now?") has historically lived behind a single static label like "Under Review." The dispute list already tracked status (Open / Under Review / Resolved / Rejected), but a flat table row didn't answer the two things a merchant actually needs day to day: which disputes need attention right now, and exactly where each one sits in its lifecycle.
- Status-first triage, not a flat list.
- Filters shaped by how disputes get chased down.
- A status pill backed by a real, timestamped timeline.
Solution
- Status-first triage, not a flat list. The list opens with four count cards — Open / Under Review / Resolved / Rejected — before a single row is visible, so a merchant reads the state of the whole queue in one glance instead of reconstructing it row by row.
- Filtering built around how disputes get chased down. The Filters panel is structured around the three axes merchants actually search by — created date, financial account, and dispute status — plus a persistent card-last-4 search for when the transaction is already in hand.
Netevia
Where
the flows landed
Guardrails built into every AI action
Every transfer Netevia AI initiates is now confirmed before it executes and logged for audit after — speed without skipping the checks a real transfer needs.
Batch payments in one flow, not many
Multiple vendors, contractors, or employees can now be paid from one upload, reviewed as a batch, and confirmed once.
A way forward at every failure point
A missed SMS code falls back to an authenticator instead of a dead end, and a disputed charge now shows a live, timestamped timeline — so “stuck” became “here's what happens next.”
Netevia
My role
and impact
4 flows, discovery to release
Designed four flagship Payments flows across web, mobile web and the mobile app, from discovery to post-release iteration. Netevia is a closed banking platform, so this case shows a selection.
Complex rules, simple flows
Turned business, banking and compliance requirements into low-friction flows, guided by analysts’ behaviour insights.
Edge cases before UI
Mapped flows, edge cases and error states before the UI stage to reduce rework, then supported engineers through specs and design QA.
One shared MUI system
Contributed to a shared MUI-based design system for a consistent UI across the product.
eWallet
