What a payout clause commits to
Four parties own the wait, and eleven contracts bind one of them
A payout runs through four hands: the customer's, the operator's queue, the network's and the receiving service's. Of the eleven operators compared here, one publishes a bound on the second — Vave, up to three business days at clause 8.1 — and none publishes anything at all about the third.
A withdrawal is not one event with one duration. It is a hand-off between four parties, and only one of them signs the contract a reader is asked to accept.
The customer holds the first stage, by supplying whatever the operator asks for. The operator holds the second, in its review queue. A public network holds the third, once a transaction has been signed and broadcast. Whatever receives the coins holds the fourth.
Eleven operators are compared on this site. One of them publishes a bound on any of those four stages.
Which stage does the contract actually describe?
The second, and mostly by describing what may interrupt it rather than how long it may last.
This operator's terms were served live on 2 September 2026 and read end to end: 75,770 characters. They set out with some care what has to be true before a payout proceeds and say nothing at all about when. Clause 21.1 permits identity documents to be demanded at the operator's sole discretion, naming government-issued ID and proof of residency, with no amount below which the request stays unmade. Clause 6.19 permits a wagering requirement of at least five times the deposit where the operator suspects the service is being used as a mixer — a floor with no ceiling, applied on suspicion. The payout terms add that the manner in which a withdrawal is processed may be restricted depending on how the deposits were made, and that the operator may conclude a request by an alternative method or process at its discretion.
Four conditions, all of which can extend a wait, and not one attached to a clock.
What the same section is exact about is money. Ten euro is the smallest withdrawal, with the full balance withdrawable on account closure. Clause 6.12 caps withdrawals at 100,000 EUR a week. Above a 400,000 EUR win, the operator reserves the right to divide the payout into monthly instalments of at most 400,000 EUR until the full amount is paid out.
When does an amount turn into a delay?
The moment a balance exceeds it, and the arithmetic is worth running before a deposit rather than after a win.
Take a balance of 1,000,000 EUR. Released at the weekly ceiling of 100,000 EUR, it clears in ten weeks. Released under the instalment rule at 400,000 EUR a month, it clears in three months.
Two sentences in one section, two answers, and no rule for which governs.
For most readers neither figure binds anything: the ceiling is theoretical and the missing processing window is the live problem. The point of running the arithmetic is that a ceiling is a clock in disguise, and a comparison column headed “maximum withdrawal” prints it as though it were a limit on generosity. How those three figures relate to each other, and the clause number carried by each, is set out on the payout terms.
Who publishes anything about the queue?
One row in eleven.
Vave states up to three business days to process in clause 8.1, and for sums above 50,000 USDT payment in instalments over up to thirty days in clause 8.8. Both were read on 25 August 2026.
Every other processing cell in the table is empty. Empty means the document was not read on that point, or was read and says nothing — never that the payout is fast and never that it is slow.
An unpublished window deserves more suspicion than a slow published one. A written figure is a sentence a customer can quote back in a dispute; silence can be applied any way an operator chooses on the day it chooses to apply it. That is an editorial position rather than a finding, and it is offered as one.
It cuts the other way too. A published window covers only the operator's own step. Three business days from approval and three business days from request are different promises, and a clause that starts its clock at approval has moved the slow part outside the measurement.
Why does nobody publish anything about the chain?
Because contracts are written in units of account, not in networks.
Not one document read for this site names a chain: no choice between an ERC-20 and a TRC-20 transfer of the same stablecoin, no minimum confirmation count, no network fee borne by either side. The coin list for this operator is not recorded here at all, because the cashier screen that would carry it needs an account.
So the stage most often blamed for a slow payout is the stage no contract here describes, and the stages the contracts do describe are the ones nobody blames.
Blame follows visibility. A public ledger shows a transaction the moment it is broadcast, with a timestamp anybody can read; a review queue shows nothing until it releases something. A payout approved within the hour and credited two days later is one event described by two people holding different stopwatches, and only one of them has a document to point at.
What can a reader measure without an account?
Three things, and none of them is a payout time.
Whether a processing window is published at all, and if so whether its clock starts at the request or at the approval. Whether a per-period ceiling exists, and over what period, since that is the figure that turns a single payout into a schedule. And whether any deadline in the document points at the operator rather than at the customer — in these terms, none does: fourteen days to report a transfer error under clause 6.18, forty-eight hours before a published result is final under the betting rules, twelve months before a dormant balance is zeroed under clause 5.3.
Everything else needs money in an account, and nobody writing this site has any. What is claimed and what is refused here is set out on the method, and the operators compared on the same rules are on the alternatives page.