The payout the operator holds, refuses or reclaims
A withdrawal request is a payment decision, and a payment decision can go three ways that are not "paid": the operator can hold it while it asks something of you, refuse it and return the money to your balance, or refuse it and keep the money. This desk sets out the states, the grounds, the clock, the documents, the retention, the appeal and the record, and reduces each one to numbers.
- desk
- 79
- requests sampled
- 1,800
- stopped
- 380
- mean stop
- 8.7 days
- retained
- 7,940.20
- reversed on appeal
- 22
A payout that does not arrive has usually not been refused. Of 1,800 invented requests, 380 were stopped at least once: 260 were released and paid, 120 were closed without payment, and only 37 of those were retained. Each stop records a deciding ground, the days it adds are measurable, and an appeal reverses about one closed request in five.
two requests in ten stop, and one stop in three is closed: only the closed ones cost time or money.
two thirds of all stops are the verification clause, so a document gap and a source-of-funds query explain 64.2% of them.
1,800 payout requests in a month: 1,421 paid without a stop, 380 stopped at least once, of which 260 were released and 120 closed without payment.
- requests
- 1,800
- paid, no stop
- 1,421
- stopped
- 380
- released
- 260
- closed unpaid
- 120
- reclaimed
- 37
The 380 stops, by the ground recorded as deciding them: a document gap 148, a source-of-funds query 96, a rail or name mismatch 61, an alleged term breach 49, a dependency not settled 26.
- document gap
- 148
- source of funds
- 96
- rail or name
- 61
- alleged breach
- 49
- unsettled
- 26
- total
- 380
Days a stop lasts, by ground: a document gap 4.2, a source-of-funds query 11.6, a rail or name mismatch 6.8, an alleged term breach 22.4, a dependency 2.1; weighted, 8.7 days.
- document gap
- 4.2 d
- source of funds
- 11.6 d
- rail or name
- 6.8 d
- alleged breach
- 22.4 d
- unsettled
- 2.1 d
- weighted mean
- 8.7 d
Of the 260 released requests, the items the operator asked for: one 118, two 83, three 44, four or more 15, a mean of 1.8 items per request.
- one item
- 118
- two
- 83
- three
- 44
- four or more
- 15
- mean items
- 1.8
- released
- 260
Mean request 412.50 over 1,800 requests: 693,412.50 paid, 41,147.30 returned to balances, 7,940.20 retained, so the mean paid request is 412.50 and the mean retained one is 214.60.
- mean request
- 412.50
- requested
- 742,500.00
- paid
- 693,412.50
- returned
- 41,147.30
- retained
- 7,940.20
- mean retained
- 214.60
What the 7,940.20 retained is made of: 3,559.40 from bonus-derived money whose conditions were not met and 4,380.80 from real money, so 44.8% of every retained pound is bonus.
- retained
- 7,940.20
- bonus-derived
- 3,559.40
- real money
- 4,380.80
- bonus share
- 44.8%
- cases
- 37
- mean
- 214.60
Of the 120 requests closed without payment, 76 were appealed, 22 were reversed and paid, 54 were upheld and 44 were never appealed; a reversal takes a mean 3.1 days from the appeal.
- closed unpaid
- 120
- appealed
- 76
- reversed
- 22
- upheld
- 54
- not appealed
- 44
- mean to reverse
- 3.1 d
Who records the 380 stops: an automated rule 231, a payments analyst 96, a compliance review 53; and the clause cited is the verification clause 244, the payment-name clause 61, the bonus clause 49, the settlement clause 26.
- automated rule
- 231
- payments analyst
- 96
- compliance review
- 53
- verification clause
- 244
- payment-name clause
- 61
- bonus clause
- 49
1,421 requests paid the same day, the 260 released ones at a median of 6 days, nine requests in ten paid or closed within 34 days, and 14 sitting past 90 days.
- same day
- 1,421
- released median
- 6 d
- nine in ten
- 34 d
- past 90 days
- 14
- stopped
- 380
- reversed
- 22
What the account shows: 380 pending lines, 260 of which became a debit and 120 a return, with the balance reserved at the moment of the request so available and total differ by the pending amount.
- pending lines
- 380
- became a debit
- 260
- became a return
- 120
- reserved
- 380
- median pending
- 6 d
- past 90 days
- 14
The two components above are the whole desk at a glance: the ladder is where a payment stops moving, and the board is why. Everything below is the arithmetic behind them, one sample at a time.
The four things a request can be doing
A request is not simply pending or done. It is queued while nothing has been decided; held while the operator asks for something and the money is reserved but not moved; refused when the operator decides against it and returns the money to the balance; and reclaimed when it decides against it and keeps the money. The distinction between the last two is the one that costs a reader money, so it has its own page.
Why the desk stops at the decision
Four neighbouring questions belong to other pages and are deliberately not repeated here. The withdrawal path - which rails exist and how money travels once a payment is approved - is a different question from whether the payment is approved. The payment chain of custody - which incoming deposit a given outgoing payment must be paired to - is a rule that decides where a payment travels, not whether it stops. A chargeback is money that moved and then moved back; this desk is money that never moved. And the commercial ceiling an operator puts on your staking is a decision about your betting, not about a payment already requested.
One request, two numbers
- Check whether the request is held or refused: a held request has an open question and a refusal has a closed one.
- Find the deciding ground in the account, because the clock it adds is different for each ground.
- Read the clause the operator cites against the request itself, not against your account.
- Check the balance twice, because a pending request reserves money that the total balance still shows.
- If it was closed, note the appeal window before it expires, because 44 of 120 closed requests in the sample were never appealed.