Queued, held, refused, reclaimed

A payout request passes through at most four states, and only the last two are decisions against you. This page defines each state, says what it does to the money, and shows where the 1,800 sampled requests sat.

Desk spec

requests: 1,800
queued: 3
held: 260
refused: 83
reclaimed: 37
mean hold: 8.7 d

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 request is queued until any decision is taken, held while the operator asks for something and the money is reserved, refused when the operator decides against it and returns the money, and reclaimed when it decides against it and keeps the money. Of 1,800 sampled requests, 380 were held, 83 were refused and returned, and 37 were reclaimed.

The states, and what each does to the money

the four states against the money
state	what it means	the money	what ends it
queued	accepted, no decision recorded yet	reserved, still yours	a decision, usually same day
held	a question is open and an item is awaited	reserved, still yours	the item arrives, or the clock runs out
refused	decided against; the money returns to the balance	returned in full	nothing - a refusal is final unless appealed
reclaimed	decided against; some or all of the money is kept	partly retained	an appeal, if there is one

The important asymmetry is that a hold and a refusal look almost identical in an account for the first day: the money is not in your hands in either case. They differ in what ends them. A hold ends when the open question closes; a refusal has already ended, and only an appeal reopens it.

Where the 1,800 requests sat

one month, 1,800 requests queued and still open at the cut-off 3 paid without ever stopping 1,421 stopped at least once 380 of which released and paid 260 of which closed without payment 120 of which refused, money returned 83 of which reclaimed, money kept 37 paid in total 1,421 + 260 = 1,681 not paid 120, of which kept 37

Why three requests were still queued

Three of the 1,800 requests were still open at the cut-off with no decision recorded, which is what a queue looks like when a sample is taken mid-flight rather than after everything settles. They are reported rather than rounded away: a table that shows only finished states hides the fact that queued time is real time. In the sample those three sat a mean 1.4 days with nothing asked of the player and nothing decided.

Telling the four states apart in your own account

A queued request has no message attached; a held one has a request for something.
A held request normally shows a deadline or a resubmission link; a refused one does not.
A refused request returns the money to the balance in the same movement that closes it.
A reclaimed request closes with a retention line, which is the only state that reduces what you get back.
Only a refused or reclaimed request is appealable, and only inside the window the operator states.

The five groundswhy the operator stopped it, and which clause it cites A hold against a refusalthe two states that look alike and are not What is keptthe only state that costs you money permanently The account recordwhat the ledger shows while the money is reserved