Rainbet: the same verification rule in two separate clauses
Two places, one question
In the Rainbet terms, verification is governed by 2 clauses, 5.2 and 8.3. Anyone reading only one of them gets an incomplete picture of when their documents can be requested — and a figure for a payout ceiling is missing from the text altogether.
In most contracts one question has one clause. Here there are 2, and the difference is substantive.
Why it is a problem when one rule sits in two places
Verification is governed by clauses 5.2 and 8.3. Both concern the same question: when, and in what circumstances, the operator may request documents.
Anyone searching the contract for verification and finding the first has a good chance of stopping there. But the second clause sits in a different context, typically in the section around withdrawals, so what gets skipped is precisely the provision that engages when money is being taken out. The split rewards a second search and punishes the first stopping point.
That kind of splitting recurs across this field; it is simply most conspicuous here. Which is why, in our table of clause numbers, this row carries two numbers where the others carry one.
What the two clauses contain
Both leave the amount out. The formulation is risk-based: the operator requests documents when it considers this warranted.
The practical consequence is the same as at the other five contracts of this kind. The request can arrive at any amount, and it is guaranteed at none. This rule can be prepared for, and never planned for.
The ceiling we did not find
We read the text of the terms, and a figure for a payout ceiling was missing from it.
That differs from there being no limit. Reading an unread ceiling as "unlimited withdrawals" is exactly the move that turns missing data into an advantage for the operator — and most comparisons in this field make it.
That is the position at four of the nine contracts we read, and those four differ again from the one where the clause exists with the amount left blank. Our methodology page sets out the difference.
The operator and the mark
The company is RBGAMING N.V., and the mark is from Anjouan: ALSI-152406029-FI2, with a valid status.
Of the four sites on an Anjouan mark, one writes an identity threshold down and three leave it out. That shows neatly how little the issuer settles about a contract: the same jurisdiction stands behind four quite different sets of terms. Our page on where the authorisation sits is about the same point.
What else could be recorded
The coin list runs to nine items. We also recorded a sportsbook offering and a provably fair mark — the latter is our note about the type of offering, not the result of an independent check.
The game count and the provider list stayed unread here as well. That field is empty at nine of the ten sites, which is also why free and demo play stay out of our text.
The country list is there, and Hungary is absent from it. This address is missing from the Hungarian permit list, along with the other nine.
What to take away from this page
One thing: if you have found the verification clause in a contract, search again. The index of the ten pages shows that half the field leaves this question to discretion, and a rule split across two places is the easiest kind to overlook.