One balance across two products, and that is a condition

A condition written for one product, spent on the other

Only one row on this site has had its promotional terms read, and it is the sponsored one, so it is used here as an illustration and nothing else.

Vave publishes a four-deposit package — 150 per cent, then 100, then 50, then 25 — capped at 4 BTC plus 100 free spins, captured from the casino tab of its promotions page on 24 August 2026. What that capture does not carry is a wagering multiple: the figure that says how many times the money must be staked before it can leave is not published on the page that was read. Without it, nothing can be said about which surface clears the condition, or whether a wager placed on the sportsbook counts towards it at all.

That gap is the ordinary case rather than the exception, and it is exactly where a shared wallet costs somebody money. An offer is filed under a casino tab, the balance it produces is spendable on a sportsbook, and the document that would say how those two facts interact was not published in the place the offer was published. The remaining eleven rows have no promotional terms opened here at all.

Whether a sportsbook exists at all, on this reading

One field in this table records a sportsbook: the sponsored row, checked 25 August 2026, marked as a paid placement wherever it appears.

For the other eleven operators, no product page has been opened for this index. That means this site asserts nothing about which of them runs a sportsbook, how many disciplines it carries, or which markets it offers. Those cells are blank. A blank records the state of this reading and enters no total. Copying a market list from another review would put a claim on this page that nobody here has checked, and the reading rules behind every figure rule that out ahead of time.

This matters more here than on a casino page, because a sportsbook is the surface where a brand's own product ends and a supplier's begins. Whatever a games lobby is stocked with, an odds feed, a set of markets and a grading procedure sit behind separate arrangements, and none of those arrangements has been examined for eleven of these twelve names. Anyone reading a sports menu off this site would be reading something nobody here checked.

The honest shape of this page follows from that. It compares what the documents say about money leaving, which has been read in part, rather than what the menus say about sport, which has not.

The only payout ceiling printed across twelve operators

Somebody asking about a maximum payout is asking the question that the terms answer most rarely and most expensively.

Across the twelve rows, exactly one ceiling is printed: Bets.io limits a single transaction to 10,000 USD under clause 10, read on 26 August 2026. That is the whole of the ceiling data on this site.

Eleven blank cells beside it are not eleven operators without a limit. They are eleven documents that stayed shut. A ceiling that appears for the first time on a withdrawal screen, after a win, converts a single payout into a queue of payouts, and no amount of reading a games lobby will surface it. Where a ceiling is unread, the reader is the one carrying the uncertainty, and this page would rather name that than paper it over.

How a large win actually leaves, when the terms bother to say

The sponsored row publishes the mechanics in full, and they are set out here because they show the shape a payout clause takes rather than because the row is being recommended.

Vave gives itself up to three days to process a withdrawal under clause 8.1, and pays anything above 50,000 USDT in instalments under clause 8.8. Read together, those two clauses describe a payout that is neither instant nor necessarily whole on the first transfer, and the person most likely to meet the second one is a bettor with a single large win rather than a casino player grinding small ones.

Nothing equivalent has been read for the other eleven. Where a payout window matters most, the payout clauses across this table carry the same figures in more detail.

Verification stands over both surfaces at once

A shared wallet has one more consequence that the marketing never mentions: verification is not per product. It sits above the account.

Five of the twelve rows carry a numbered clause on the point: 4.8, 4.1, 18.1.1, 5 and 8.7, belonging respectively to Stake.com, Shuffle, Cloudbet, Bets.io and the sponsored row. Two of them attach a deadline to the demand — thirty calendar days at Bets.io, fourteen days at the sponsored row — and the rest attach none. Seven rows print nothing in that column, the document behind them never having been opened here.

Where such a clause bites, it bites on the balance and not on the surface the balance was won on. A win from the sportsbook and a win from the casino leave through one gate, and one document decides when the gate opens. A bettor who has never touched a slot is governed by a clause that makes no distinction between the two.

The territorial clause is read before any of this matters

None of the above applies to somebody whose country is already written into the clause above the cashier, which is why the count comes first on this site.

Stake.com's own territorial clause runs to one country, the United States, read from stake.com/licenses on 26 August 2026. The other three read schedules in this table run to two at Cloudbet, fifteen at Shuffle and forty-two at Bets.io, and eight rows keep a document that stayed shut. Country by country the totals diverge sharply: thirteen of the thirty-eight read schedules print Australia, while Canada is named by none of them. Same documents, same date, opposite answers.

The ceiling, the verification clauses and every schedule length quoted above sit in the table on the index behind these pages, and the regulatory side of the same twelve names is read at the permit-by-permit reading.