Bonus wording, read 2 September 2026
Why a wagering requirement never became one of the seven questions
BitStarz publishes three numbers about what a bonus costs the player — forty times, five euros a bet, seven days — and none about what it owes in return. Two of the three end with the words unless otherwise stated, which is the reason wagering fills no box on this site.
Seven questions are asked of every operator on this site, and a wagering requirement answers none of them. That was a decision, and the material behind it is worth printing, because the number involved is the one most readers are actually looking for.
The three numbers BitStarz does print
The bonus terms, read on 2 September 2026 in the edition dated 25 June 2025, put a figure on each part of what a bonus costs.
Clause 3.4 sets the turnover: a bonus must be wagered forty times before the funds can be withdrawn. For a bonus of a hundred units that is four thousand units of betting, and the multiple attaches to the bonus rather than to the bonus plus the deposit, which is the less punishing of the two ways this is normally drafted.
Clause 3.10 sets the speed limit: while a bonus is live, a single bet is capped at 5 EUR, with the equivalent stated in every supported unit down to 0.00006 BTC, and the cap holds until the playthrough requirement has been met.
Clause 3.7 sets the clock: Welcome Package bonuses last seven days, and every other bonus expires 24 hours after it is issued.
Three clauses, three figures, all of them numbered and quotable. On the face of it this is a well-documented operator, and on the face of it that should fill a box.
What the words after the numbers do
Read the sentences to their ends and two of the three stop being fixed.
Clause 3.4 requires forty times “unless a particular promotion states otherwise”. Clause 3.7 gives its two periods “unless otherwise stated”. So the general document publishes a default, and a supplemental page attached to a specific offer can replace it, at whatever value that page carries on the day.
The third figure is bounded differently. The 5 EUR ceiling in clause 3.10 runs until the playthrough requirement has been met, which ties one clause to another rather than to a date: the ceiling lasts as long as the turnover does, and the turnover is set by a clause that can itself be overridden.
None of that is unusual and none of it is hidden. It is how promotional terms are written across the trade, and the operator has been plain about it in the same sentence as the number.
It is also exactly what a yes-or-no box cannot record.
Why a defeasible figure fails the entrance test
Every one of the seven questions on this site has one property: a stranger can settle it by opening a document and looking, with no judgement in between. A permit number is printed or it is not. A register entry resolves or it does not. A payout ceiling of 5,000 USD a month is stated in clause 11.5 or the clause does not exist.
A multiple of forty that holds unless a particular promotion says otherwise fails that test in a specific way. The document was opened, the figure was read, and the reader still does not know what governs the offer in front of them, because the governing version lives on a page attached to that offer. A box marked yes would carry the same visual weight as the permit box while resting on a default.
The alternative — reading every supplemental promotional page at every operator, dating each one, and re-reading them as they change — is a different project, and an unbounded one.
So the count leaves wagering alone, and this article stands in its place.
Where the precision in this contract sits
Line the figures up by who they bind, and the pattern is the whole point.
| what is stated | figure | where | override in the same clause |
|---|---|---|---|
| turnover the player owes | 40 times | 3.4 | yes |
| ceiling on the player's bet | 5 EUR | 3.10 | tied to 3.4 |
| time the player has | 7 days, or 24 hours | 3.7 | yes |
| sum that triggers document checks | none stated | — | — |
| ceiling on what the operator pays out in a period | none stated | — | — |
Three numbers on one side of the ledger and none on the other. The operator has been precise to five decimal places about the size of a bet and silent about the amount at which it will ask for a passport.
That silence is not rhetoric on this site, it is two of the seven boxes. BitStarz fills five, and the two it leaves open are the two that would have bound the operator rather than the customer. Nineteen operators sit on five boxes and eighteen of them carry that identical pair of blanks, so this is a habit of the trade rather than a quirk of one brand.
The clause with no override in it
Clause 3.26 is the exception that makes the pattern visible. A code entered for a promotion the account is not eligible for costs the bonus behind that code and every other bonus the deposit would have earned. No default, no unless, no supplemental page.
Clause 3.15 is drafted with the same firmness in the other direction: what counts as promotion abuse is left to the operator's sole and complete discretion, together with the right to revoke a promotion and withhold its proceeds. A term defined by one party's judgement is not vague by accident; it is the widest form a clause can take.
Put those two beside the three overridable figures and the document reads consistently. Where the operator gives something, the number is a default. Where the operator takes something back, the wording is unconditional.
What this leaves a reader holding
A checkable arithmetic, valid for the general document and nothing else: forty times a hundred is four thousand units of turnover, produced five euros at a time, inside seven days or one, and the version that governs any particular offer is on that offer's own page.
Read that page before depositing, and read it for the two words rather than for the number. Everything on this site is built on the same distinction between a figure and a commitment, set out at length on the rules of the count. What BitStarz does fill, box by box, is on the hundred, counted, and the reader behind the file is described by the records editor.