A hold against a refusal

The two states look the same for a day and are opposites underneath. This page separates them by what ends each one, what each does to the balance, and what the player can do about it.

Desk spec

held: 260
refused: 83
reclaimed: 37
hold ends: item or clock
refusal ends: appeal only
reversed: 22

the stateWhat the request is doing. Of 1,800 sampled requests, 1,421 were paid without ever stopping, 380 were held at least once, 260 of those were released and 120 were closed without payment.

the groundThe recorded reason a payment stopped. Across the 380 stops: a document gap 148, a source-of-funds query 96, a rail or name mismatch 61, an alleged term breach 49 and a dependency not settled 26.

the retentionThe one outcome that costs money permanently. Of 742,500.00 requested, 693,412.50 was paid, 41,147.30 returned to balances and 7,940.20 retained, at a mean 214.60 per reclaimed request.

Direct answer

A hold is a stop with an open question and a route out: supplying the item or letting the clock close it ends the stop, and 260 of 380 sampled stops ended that way. A refusal is a closed decision with one route back, an appeal, and 120 sampled requests ended that way, of which 83 returned the money and 37 kept it.

What ends each one

held against refused
	held	refused
what the operator did	deferred the decision	took the decision
what is open	a question you can answer	a decision you can only appeal
the balance	reserved, still yours	returned, or partly kept
what ends it	the item, or the clock	an appeal, or nothing
sample count	260	120
mean days	8.7	4.9 after the decision

the same request under each state a 412.60 request held: reserved 412.60, available balance falls to 0.00 the question is answered on day 6 released 412.60, available balance back to 412.60 outcome: paid, 6 days late refused: reserved 412.60, available balance falls to 0.00 decided against on day 2 returned 364.40, retained 48.20 appealed on day 4, reversed on day 7 paid 412.60 outcome: paid, 7 days late, one appeal used

Why the operator prefers a hold

A hold keeps the decision open, which is why it is the state in which most stops sit: 260 of 380 stopped requests were held rather than closed. A hold also costs the operator nothing if the question is answered, because the money was reserved and never left. A refusal costs something either way - it either returns money the operator had already decided not to pay, or it keeps money and invites an appeal - so it is used about a third as often.

The one state that is not a decision

A dependency not settled is not really a hold in the operator sense: 26 stops were recorded that way because a bet was still running or a deposit had not cleared, and those requests would have resolved themselves with nothing asked of the player. It is reported as its own ground because the message a player receives looks like a hold even though no question is open.

Working out which state you are in

If there is a request for an item, it is a hold and the clock only runs while the item is outstanding.
If there is no request and no decision, it is still queued, which in the sample meant a mean 1.4 days.
If the balance changed by the full amount, the request was refused or reclaimed, not held.
If only part of the money came back, the rest was retained and the request is appealable.
If a bet or deposit is still open, the stop is a dependency and will clear itself.

What is keptwhat the operator keeps when a request is reclaimed The appealthe one route back from a closed request The recordthe pending line, the debit and the return The groundswhy the decision was deferred or taken