The payout queue at King
Reducing repeated withdrawal handling from three clicks to one while keeping review before send.
- Context
- Gaming platform / payout operations
- Role
- Product Owner
- Date
- August 2016
The short version
- The problem
- 300 to 500 withdrawals a day, each needing three repeated actions after the safety checks were done.
- What I did
- Redesigned the payout flow so approved withdrawals land in a batch list, one action each.
- What it was worth
- Roughly 600 to 1,000 clicks a day removed. The checking and the final payment control stayed.
- The call
- Touch nothing before the decision, remove everything after it.
What changed
Between 300 and 500 withdrawals a day, each checked in its own tab, and that was necessary work. Paying one out then took three repeated actions. Submit, approve the confirmation, send.
One action per approved withdrawal sends it to a batch list instead. The checking stayed exactly as it was, and the final payment control stayed where it was.
Problem
In the real-money skill gaming platform, every approved withdrawal required three repeated actions. Submit, approve the confirmation, send. Across 300 to 500 withdrawals a day, that became a lot of manual work for something that mostly needed control and attention rather than fresh judgement each time.
Approach
I redesigned the payout flow so approved withdrawals first landed in a batch list. That reduced the interaction to one repeated action per withdrawal, while keeping the final payment control before funds were sent.
The new flow kept the control step, but made the interaction simpler. Each approved item could be handled with one action, and the reviewed list could then be sent in a batch.
Outcome
Going from three repeated actions to one removed roughly 66% of the repetition. At 300 to 500 withdrawals a day, that is somewhere between 600 and 1,000 clicks a day that no longer had to happen.
For whoever was clearing payouts that day, usually one or two people, it meant far fewer clicks on approvals that had already passed every safety check. The final payment control stayed exactly where it was.