Evidence DeskIndependent Australian consumer reference
Navigate Rainbet game claims by category
This hub explains how to classify a game claim before checking it. It does not state that Rainbet currently supplies any named category or title. Category labels are navigation aids, not proof of a provider, configuration, lawful access or working session.
Research checkpoint:
| Format | Mechanic to confirm | Useful identifiers |
|---|---|---|
| Pokies | Symbol evaluation, paylines or ways, cascades and features. | Provider, game code, rules version, round ID. |
| Crash style | End event, decision acceptance and settlement timing. | Product version, round ID, timestamps, ledger entry. |
| Table game | Equipment or software model and table-specific rules. | Provider, table, shoe or hand ID, event time. |
| Peer poker | Human opponent model, action order and pot settlement. | Table or tournament ID and hand history. |
| Bingo | Card pattern, called values and draw completion. | Provider, room, card and draw ID. |
Evidence step 01
Classify the product before collecting evidence
Begin with what the user actually interacts with. A pokie resolves symbol patterns; a crash-style product asks for a decision before an increasing display ends; roulette resolves a numbered wheel outcome; blackjack compares hands under table rules; poker can describe peer competition, a dealer table or a machine game; bingo marks drawn values against a card. The evidence needed for one format cannot automatically answer questions about another.
Record the category label as an observation, then open the rules or information panel to confirm the mechanics. Marketing menus can group products for convenience or place the same title in several collections. If the label and rules disagree, describe both and rely on the product mechanics for classification. Do not infer a live dealer merely from photographic artwork or peer opponents merely from the word poker.
Evidence step 02
Separate discovery, launch and session claims
A search result may reveal an indexed page. A catalogue tile may show a listing. A loading screen may show an attempted launch. A rules panel and round record describe a session. Preserve the stage relevant to the claim. Evidence from an earlier stage cannot establish a later one, so a tile does not prove launch access and a historical round does not prove current availability.
Date every observation and note the hostname, device, language and account context where those facts are known. Availability may differ across those conditions or change without notice. This guide does not attempt to maintain a live inventory. Its purpose is to help a reader state a limited finding that another person could test, including a clear note when login or access restrictions prevented inspection.
Evidence step 03
Use category-specific identifiers
For software games, retain the provider attribution, game code, rules version and round identifier. For live tables, capture the studio or table label, table rules, shoe or hand reference and event time. For peer formats, preserve table or tournament ID, action history and opponent model described in the rules. For scheduled draws, keep the draw identifier, card definition, called values and result notice.
Names and artwork are easy to reuse, translate or alter. Stable identifiers allow a provider or support team to locate the relevant record and distinguish related releases. If an identifier is not exposed, save the complete screen sequence and request it in writing. Avoid inventing a provider relationship from an image filename, page slug or third-party commentary that cannot establish what actually loaded.
Evidence step 04
Assess rules and outcome representations
Read the rules that govern the decision point: symbol evaluation for pokies, end-event and cash-out treatment for crash-style games, betting limits and wheel form for roulette, dealer and split rules for blackjack, opponent and pot rules for poker, or card and draw conditions for bingo. Save the version before play or immediately when an issue appears. Rules copied from another site may describe a different product.
An outcome history, animation or label such as random does not establish the underlying method. A meaningful technical claim identifies the responsible provider, covered release, process and any testing scope. Never calculate or publish a return figure from promotional wording or a short sample. If displayed rules and ledger movement conflict, stop, preserve event identifiers and seek an explanation tied to the exact session.
Evidence step 05
Route the question to the focused guide
Use the pokies page for catalogue and provider attribution, Aviator for crash-style timing and history claims, the three named title pages for their distinct feature systems, and the roulette, blackjack, poker or bingo pages for table and draw mechanics. These pages explain how to verify a representation; none should be read as confirmation that Rainbet offers the product now.
Finish by writing what the evidence proves and its boundary. For example, a dated rules screen can establish the rules shown for a session, but not continued availability. List missing records and the source that could supply them. Keep credentials, recovery secrets and unrelated personal data out of evidence requests. A precise unresolved conclusion is preferable to a broad category claim built from incompatible records.
Questions
Questions for this evidence task
Does a Games menu prove every category is available?
No. A menu is a navigation observation. Verify the listing, launch and session stages separately and date each finding.
Why do category labels need checking?
Menus may group products for marketing. The actual rules reveal whether play uses reels, a timed decision, a table, opponents or a scheduled draw.
Which identifier is most useful in a dispute?
Use the provider and product code plus the round, hand, table, tournament or draw identifier appropriate to the format.
Do these guides publish game return figures?
No. Configurations can differ, and this guide does not assert numeric returns or derive them from short sessions or promotional copy.