◢The Payment On Hold payment on hold Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A page about a payment an operator held or refused should not leave its own funding unsaid: one link funds the site, no operator is named, rated or recommended anywhere on it, and no operator is described by any figure on it.
The Payment On Hold / request
what the operator asks for

The items that close a stop

A hold ends when the operator has what it asked for. This page lists the items most often requested, how many items a released request needed, and the small number of stops that closed with nothing supplied at all.

Desk spec
released
260
mean items
1.8
one item
118
closed by item
244
closed by clock
16
four or more
15
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 released payout needed a mean 1.8 items. Of 260 released requests, 118 needed one item, 83 needed two, 44 needed three and 15 needed four or more, and 244 of the 260 were closed by the player supplying something while 16 closed because the clock ran out.

The items, by how often they were asked for

items requested across 260 released requests
itemtimes askedwhat it satisfies
a photo identity document122the name on the account
a proof of address96where the holder lives
a source-of-funds document88where the money came from
a bank statement74the destination the payment will travel to
a liveness or selfie check61that the document and the person agree
a written explanation39an alleged breach, in the holder own words

The counts exceed 260 because a request can need more than one item; the mean is 1.8, so the table is best read as a set of frequencies rather than a split of the 260.

items per released request, and the mean one item 118 two items 83 three items 44 four or more 15 released total 260 (118 x 1) + (83 x 2) + (44 x 3) + (15 x 4) = 118 + 166 + 132 + 60 = 476 items 476 / 260 = 1.8 items per released request

Everything is not evidence

An item closes a stop only if the operator reads it as answering the question that was asked. In the sample 118 requests released after one item and 15 needed four or more, which is a five-fold spread on a single nominal step. The practical consequence is that a resubmission costs time even when it is not a new question: what restarts is the reading, not the asking.

Sixteen stops closed with nothing supplied

Of the 260 released requests, 16 closed without the player providing anything. That number matters because it shows that a hold is not always a demand: a dependency settled itself, a document already in the operator file was matched, or the clock on an unanswered query expired and the request was paid anyway. Those 16 are the sample evidence that a hold carries no presumption that the money will not come.

Answering a request efficiently
  • Supply exactly what was asked for, because an unrelated document restarts the reading time.
  • Read the deadline attached to the request, because 16 of 260 stops closed on the clock rather than on an item.
  • Keep one set of documents current, because the same items are asked for across grounds: identity 122 times, address 96.
  • Answer the source-of-funds question with a document that names the money, not a general statement.
  • If a written explanation is asked for, answer the specific allegation rather than restating the account history.