Key takeaways
- Eligibility should be a rule the trader can see, not a judgement made at request time.
- Every payout decision — approved or denied — should leave a record sufficient to explain it a year later.
- Fraud review belongs before approval, with human decision at the end, not automated denial.
Make eligibility legible before it is requested
Most payout friction comes from a trader believing they were eligible and discovering otherwise at the moment of request. If the dashboard shows eligibility against the actual rule set continuously, the disagreement happens early, in a low-stakes context.
It also reduces support volume substantially, because most payout tickets are eligibility questions rather than complaints.
The review queue
- 01
Automated eligibility check
Evaluate the request against the rules that apply to that account, reading the risk engine's authoritative state rather than recomputing.
- 02
Fraud and identity screening
Surface identity, trading and financial risk signals with evidence attached. See fraud prevention.
- 03
Human review
An operator reviews the request with the account state, signals and history visible, and decides with attribution.
- 04
Decision and record
Record the outcome, who decided, what they saw and why — sufficient to answer a challenge months later.
- 05
Payment execution
Move the money, reconcile against financial records and update the trader through the same event stream that drives their dashboard.
Denials deserve more rigour than approvals
An approval that was wrong costs money. A denial that was wrong costs reputation, and in this industry reputation compounds faster than either.
Denials should require the strongest evidence, a named decision-maker and a defined appeal path. A firm that cannot explain a denial precisely will be assumed to be acting in bad faith, whether or not it is.