Evidence DeskIndependent Australian consumer reference
Check Rainbet roulette representations
Roulette is defined by its wheel layout, betting map and settlement rules, not by a generic table image. This guide explains how to verify a Rainbet-related representation without asserting that any roulette table is currently listed or accessible.
Research checkpoint:
| Question | Record | Common mistake |
|---|---|---|
| Which wheel? | Full pocket layout and table rules. | Identifying it from theme or colour. |
| Was the bet accepted? | Accepted positions, stake and closing status. | Treating a placed chip as confirmed. |
| What was the result? | Spin ID, official pocket, event time and history match. | Relying on a cropped animation. |
| How was it settled? | Rule, bet history and ledger before and after. | Using result history without the wager. |
| Who delivered it? | Provider plus table, studio or game code. | Assuming a dealer image proves live delivery. |
Evidence step 01
Identify the wheel and table
Capture the table name, provider, table or game identifier and complete wheel layout. The presence and arrangement of zero pockets distinguish major wheel families and affect the betting map. Do not identify a variant from colour or a cropped wheel image. Save the rules panel that names the layout and any special treatment of even-money bets.
Record whether the product is software-rendered, video-streamed with a physical wheel, or described another way. A dealer photograph does not prove live delivery. For streamed tables, retain the studio or table label and event reference. For software products, retain the game code and round ID. These identifiers determine which provider record could answer a dispute.
Evidence step 02
Read betting and acceptance rules
Save the betting limits, chip values, closing indicator and rule for rejected or late bets. A chip placed on the layout may still be pending until the interface confirms acceptance. Capture the accepted-bet summary before the result where possible. Do not use later balance movement alone to infer every position accepted for the spin.
Check how neighbours, sectors, call bets or saved bet patterns are defined if the interface offers them. Labels can hide several underlying chip placements. For any special zero rule, record the exact wording and conditions rather than assuming a familiar table convention. The governing text for the actual table is stronger than a generic roulette explainer.
Evidence step 03
Preserve the complete result sequence
For a questioned spin, retain the event time, round or spin identifier, accepted positions, stake total, result pocket, settlement message and balance before and after. With a streamed wheel, a continuous recording can preserve the ball and wheel sequence, but the provider event record is still needed to establish the official result if the view freezes or skips.
A history panel is useful for locating a spin but does not prove it is complete or explain settlement. Match its entry to personal bet history and the ledger. Do not continue betting to test whether a display fault recurs. Stop after preserving the affected event and request the official table record and rule used for settlement.
Evidence step 04
Assess provider and fairness wording
Match the session attribution to an accountable provider source. If a physical wheel or dealer stream is claimed, seek table and studio identifiers. If software randomness or testing is claimed, seek a record naming the release, method, jurisdiction and date. A generic certification logo cannot prove coverage of every table carrying the same brand.
This page publishes no return, house-edge or probability figure because it does not verify a current wheel configuration. Those values depend on the precise layout and rules. Do not derive them from a short history. First establish the wheel, special rules and accepted bet, then limit any analysis to that documented configuration.
Evidence step 05
Date access observations
This guide makes no present Rainbet supply claim for roulette. A listing image, table load and completed spin are different observations. State which occurred, on what hostname and date, under what known account conditions. A maintenance error or missing table on one device does not establish universal absence, while an old screenshot does not establish present access. Keep the source capture beside the written finding so its date and limited scope remain clear to any later reader.
For a dispute, ask support to identify the table, provider, official result and server acceptance record. Preserve the answer with the rules and ledger. Redact unrelated personal details and never share credentials. If the table identifier or accepted-bet record is missing, explain that gap; do not estimate the result from a visual fragment or memory.
Questions
Questions for this evidence task
Why does the zero layout matter?
It distinguishes wheel families and determines which betting and settlement rules need to be checked.
Does placing a chip prove the bet was accepted?
No. Preserve the accepted-bet summary and server or table record, especially when betting closed near the action.
Can the recent-results panel settle a dispute?
Not alone. Match it with the spin ID, personal bet history, official result and ledger movement.
Is roulette currently available at Rainbet?
This page does not make that claim. It explains how to document a dated listing, load or session observation.