A payout, made visible
Choose a moment ↘
A merchant asks to withdraw.
The request becomes visible to operations.
The worker picks up the request.
The transfer is sent to the bank.
An interaction explaining the designed flow. No live transfers.
The story behind the play Read the thinking ↗
The hook
A worker takes a queue of withdrawal requests and sends them to the bank. The operations team no longer has to shepherd every payout by hand.
Context
Every payment product needs an internal system that can manage merchants, transactions, risk, reconciliation, and settlement. For Paykit, payout activity also had to connect to the ERP and the bank without obscuring the status of real money.
The move
I made payout an explicit pipeline instead of an admin task: withdrawal request, automatic processing queue, worker, then bank transfer. Each stage has a state the operations team can inspect.
What shipped
I designed the Operation Center for merchant, transaction, and risk management, alongside ERP-supported reconciliation and settlement. A merchant adds a bank account and requests a withdrawal; the request enters the queue; the worker selects it and sends the transfer to the bank.
Outcome
The back office made an invisible process legible. Operations could see where a payout was in the flow while the repeatable transfer work could run as a system.