Counting the clocks
Sixteen figures carry a unit of time. Three of them measure a payout
Reading the ten sets of terms end to end for anything with a unit of time attached produced sixteen figures, spread across five different units — hours, days, calendar days, business days and weeks. Three of the sixteen measure how long the operator takes to pay. The rest measure something else.
Why does one simple question produce five different units?
Ask how long a payout takes and the honest first step is not to answer but to count. We read the terms of all ten operators in this site's table looking only for figures with a unit of time attached, and stopped counting at sixteen.
Those sixteen are written in hours, in days, in calendar days, in business days and in weeks. Five units for one subject, inside ten documents that are broadly copies of one another in structure.
Three of the sixteen describe how long the operator takes to send money. That ratio is the finding.
Which clauses actually measure a payout?
Vave states in clause 8.1 that a withdrawal is processed within a maximum of three days.
Rocketpot states in clause 11.3 that it will process all requests within 72 hours.
Wild Fortune states in clause 11.10 that all bank transfers are processed within three business days — and that clause is about a bank rail, not about a coin leaving a wallet, so it answers a narrower question than the other two.
Those are the three. Bitcasino.io, DuckDice, Empire.io, Metaspins, Rainbet, Shuffle and Wild.io describe a withdrawal process in full and commit to no period for finishing it. A blank there means the document was read and nothing was found; it is not a judgement about how any of them behaves.
Why are three days and 72 hours not the same statement?
They are the same length. They are not the same statement, and the difference is worth spelling out, because a comparison table that prints “3 days” beside “72 h” has quietly claimed they are interchangeable.
Neither clause names the event that starts the period. A withdrawal request has at least three candidate starting points — the moment the button is pressed, the moment the request clears an internal queue, and the moment a document check ends — and both documents leave the choice to the operator.
Neither clause says whether the period is suspended while identity documents are outstanding. Neither attaches a consequence to overrunning. A period with no start, no pause rule and no penalty is a description of intent, and it is still worth more than nothing, because it can be quoted back.
The unit matters too. Three business days is not three days: a Friday request under Wild Fortune's clause 11.10 and the same request under Vave's clause 8.1 land on different calendar dates without either operator being late.
What are the other thirteen figures measuring?
Mostly the player, and mostly the aftermath.
Rocketpot's clause 12.2 gives the player 30 calendar days to supply requested identity or source-of-funds documents, and reserves the right to freeze the balance until they arrive. Vave's clause 8.7 gives 14 days and states that once the period passes the account is closed and the winnings are forfeited.
Rocketpot's clause 11.9 adds two more: after a password change, 48 hours must pass before a withdrawal is granted, and the player has 48 hours to report that the change was not theirs.
Then the complaints machinery, which is where the documents suddenly become precise. Bitcasino.io's clause 4.2 promises acknowledgement of a complaint no later than one week. Clause 4.4 promises notification of the status within four weeks of receipt and allows that limit to be extended once, in writing, by a further four weeks. A note under the same clause gives responsible-gaming complaints priority, with best efforts inside five business days and any delay capped at two weeks.
Rainbet publishes a complaints procedure with three figures of its own — acknowledgement within two business days, an initial response with proposed steps within ten business days, and up to 30 days for a final determination on an escalated case. That document carries headings rather than numbered clauses, so there is no clause number to cite beside those three, and we say so rather than inventing one.
DuckDice's section 12 supplies the last figure: where a refund is approved after an account review, it is processed within 30 days.
So the operator that publishes no period for paying you publishes three for answering you, and the outer edge of that written procedure is eight weeks from receipt.
What stops a clock that has already started?
Four things in these documents, and Rocketpot carries three of them inside one section.
Clause 11.2 permits a withdrawal only after the deposited amount has been wagered three times. Clause 11.4 reserves a verification check above the equivalent of 0.05 BTC or 2,500 US dollars, and reserves the same check below it. Clause 11.5 caps payment at 5,000 US dollars a month once winnings reach that figure.
None of those three is a delay in the sense a published period is. Each is a condition, and a condition that has not been met means the period has not begun.
The fourth is the one nobody schedules: the document request itself. Seven of the ten reserve a discretion instead of publishing an amount that triggers a check, which is set out on identity verification. A check that can start at any moment cannot be planned around, and the player's own deadline starts there rather than at the request.
How can any of this be measured without an account?
By reading, and by writing down four things about every period found: the number, the unit, the event that starts it, and the rule that suspends it.
On these ten documents that exercise ends with three numbers, three units, no stated start in any of them and no stated suspension in any of them. That is a poor result, and it is the real answer to the question about speed — better than a number of minutes taken from an advertisement, because every part of it can be checked by someone else in the same clause.
The blockchain is not the variable here. A transfer confirms in minutes and a stablecoin on a fast chain in seconds; what that depends on is on networks and fees. The two stages in front of it are the ones with no published number at seven operators in ten.
A correction to our own page
Our page on how long it takes says that one operator of the ten publishes a processing period, and cites Rocketpot's clause 11.4 for the player's 30 calendar days.
Reading section 11 and section 12 of that document in full for this article corrected both points. There are two published processing periods, not one: clause 8.1 at Vave and clause 11.3 at Rocketpot, plus the bank-transfer period in Wild Fortune's clause 11.10. And the 30 calendar days sit in clause 12.2, not 11.4; clause 11.4 is the verification threshold.
Neither error changed a figure in the table, and both are ours. They are written here rather than quietly fixed, for the same reason the licence correction on what a licence number proves carries both of its dates.
What this article does not claim
No withdrawal has been requested from any of these ten operators. No account exists, no deposit was made, and nothing above describes an experience or a measured duration.
Every figure here was read from the operator's own document on the dates recorded against it, with the clause number where the document has one and with a plain statement where it has none. What an operator does in practice is outside what this site can see, and the method that keeps it outside is on how we read the terms.
And the frame around all of it does not move: these are terms written by foreign companies under other jurisdictions' law, and the structure of the Indian Act of 2025 is set out on what the law says.