The one documented segment is not the fast one

The wait, broken into segments

A withdrawal that a reader experiences as one number is three things in sequence, and it helps to know which of the three anyone has actually written down.

The first segment is the operator's own processing: the interval between a request being submitted and a payment being released. This is what a published window would describe, and for Stake.com there is no such window in the document read here.

The second is the network. Once a payment is broadcast, arrival depends on the chain, its fees at that moment, and how many confirmations the operator waits for. Nothing about confirmations or supported networks has been read for any row on this site, because that information lives on a cashier screen and no cashier screen has been opened.

The third is verification, and it is the only segment with a clause number attached. Clause 4.8 makes it a condition rather than a delay: payment may be restricted until identity is sufficiently determined, and sufficiently is the operator's judgement. It has no published deadline either, so a wait of that kind is bounded by the operator's own pace.

Two of three segments blank and one documented is a thin answer, and it is the whole of what the reading supports.

Pending covers at least three different states

The word people type is pending, and it hides the distinction that matters.

It can mean the request is sitting in the operator's queue awaiting release — the first segment, undocumented here.

It can mean the payment has left and the network has not yet confirmed it — the second segment, also undocumented, and outside the operator's control once broadcast.

Or it can mean the account is under a verification hold, which is the state clause 4.8 describes in as many words. That third case behaves differently from the other two, because it does not resolve with time. It resolves when documents are supplied and accepted, and the clause reserves the right to ask for more.

Which of the three a given status represents is not something this site can tell a reader, and neither can any page that has not read the account. The clause numbers are the only part of this that is checkable, and the identity side of them is set out on Stake KYC levels.

Unsettled bets on a shared balance

Where a casino and a sportsbook run on a single balance, an open bet is money that is neither lost nor won, and how the cashier treats it decides whether a withdrawal is possible at all. It is a fair question to bring to this page.

No document read for this site answers it. There is no clause in this reading describing what happens to a withdrawal request while a bet remains unsettled, for Stake.com or for any of the eleven other rows.

So the entry is unknown. This page does not assert that such a clause exists, does not assert that it is absent, and does not describe a mechanism it has not read. Should the clause be opened later, it goes here with its number and its date, which is how every other figure on this site arrived.

The same fields across the other rows

Set the four fields side by side across the twelve rows and the table is mostly empty, which is the honest picture of what has been read.

Processing window: one row of twelve publishes one. Vave, which holds the paid placement here and takes no score and no ranking position, states three business days in clause 8.1. The other eleven publish nothing in anything opened for this site.

Transaction ceiling: two rows. Bets.io sets 10,000 US dollars per transaction in clause 10. The paid row splits payment into instalments above 50,000 USDT under clause 8.8. The remaining ten are blank.

Verification condition: five rows. Stake.com at 4.8, Shuffle at 4.1, Bets.io at clause 5 with 30 calendar days to supply documents, Cloudbet at 18.1.1, and the paid row at 8.7 with fourteen days. Seven rows have a verification clause nobody here has opened.

Unsettled-bet handling: zero rows. Nobody here has read one.

The comparison that a reader wanting speed is really after is laid out with the same blanks on fastest payouts like Stake, and the verification question that dominates all of it on sites like Stake with no KYC.

A window is a declaration, not a promise

One point about the single figure that does exist here, because it is the point most pages skip.

Three business days in clause 8.1 is a window the operator announces for its own processing, in a document it wrote and may amend. It covers the operator's segment and nothing else — not the network, not a verification hold, not the instalment rule in the neighbouring clause. It is better evidence than an unsourced claim, because a reader can open the same clause. It remains a statement of intent.

That is the strongest thing any payout figure on this site can be. Nobody here holds an account with any operator named on this page, has deposited, or has watched a payout arrive; every figure above came out of a document, and the ones that were not in a document are printed as gaps.

Which Stake this page reads

Clause 4.8 and every blank above belong to Stake.com, the operator whose licence entry names Medium Rare N.V. and whose territorial clause runs to a single country.

Stake.us is a separate product with its own documents, and none of them was opened for this page. Nothing above describes its cashier, its limits or its timings. The two are told apart on Stake.com vs Stake.us.

Whether an operator will deal with a reader at all is a separate reading again, taken from the territorial lists: the United Kingdom, Japan and Spain each carry their own count, and the twelve compared rows sit on the front page.