Evidence DeskIndependent Australian consumer reference
Check Rainbet Aviator representations
Aviator is commonly described as a crash-style game in which a rising display ends at an event and a decision must be accepted beforehand. This page explains the evidence needed to verify a Rainbet-related claim; it does not confirm current availability, launch access or a specific configuration.
Research checkpoint:
| Claim | Record to retain | Boundary |
|---|---|---|
| Product identity | Session title, provider, game code and rules. | Aircraft artwork alone is insufficient. |
| Decision timing | Continuous sequence, status, round ID, clocks and ledger. | A tap does not prove server acceptance. |
| Round history | Full history panel matched to round detail. | History does not prove outcome generation. |
| Verification method | Instructions, committed input, disclosed input and mapping. | It supports only the documented method. |
| Availability | Dated hostname and observed listing, launch or session stage. | One observation is not continuing universal access. |
Evidence step 01
Confirm the product and rules shown
Do not identify the product from an aircraft graphic alone. Save the in-session title, provider attribution, game or version identifier and complete rules. Check how a stake is accepted, when a round opens and closes, what action requests settlement, and how the rules define a successful decision. Similar crash-style products can use different interfaces, histories and verification systems.
Record whether automated actions, multiple stake panels or connection-loss rules are described, but do not assume those controls exist until the actual rules show them. If a catalogue tile opens another product or a generic category page, document the mismatch. A search result or archived image can support a historical naming claim only, not current supply by Rainbet.
Evidence step 02
Distinguish a click from an accepted decision
A screen tap, server acceptance and balance update are separate events. When a dispute concerns timing, preserve a continuous recording if possible, the device clock, round identifier, visible status messages and ledger entry. Note network interruptions without claiming they caused the result. Support or provider logs are needed to establish server receipt and processing order.
Read the rule covering late requests, suspended rounds, reconnects and interface errors. A still image taken after the event cannot show when a request was sent or accepted. Do not keep staking to reproduce a timing problem. Stop after preserving the affected round, because additional rounds can obscure the chronology and increase loss without improving the original evidence.
Evidence step 03
Treat history panels as secondary records
A visible list of earlier results can help locate a round, but it does not by itself prove how outcomes were generated or that the list is complete. Capture the history with its labels, time and product identifier. Match a disputed entry to the personal ledger and any downloadable round detail rather than relying on colour, animation or a cropped multiplier display.
If the product presents a verification method, record the full instructions and inputs before attempting to interpret it. Determine which value was committed before the round, which value was later disclosed, and how the named round maps to those records. A verification interface supports only the method it actually documents. It does not establish operator identity, Australian legality or present availability.
Evidence step 04
Verify provider and configuration claims
Match provider wording inside the session with an accountable developer record. Preserve any game code, rules version, certification reference and jurisdiction scope. A logo on a lobby card can be copied, while a developer page describing Aviator generally cannot prove which build was delivered in a particular session. Conflicting provider labels should remain visible in the evidence file.
Do not publish a numeric return, maximum result or probability from memory, another affiliate page or a short result history. Such statements can vary by configuration or be misunderstood. The defensible approach is to quote no unsupported figure, retain the exact rules presented, and ask the provider or testing body to identify the release and scope covered by any technical representation.
Evidence step 05
Frame availability and dispute findings narrowly
This guide makes no present supply claim for Aviator at Rainbet. A dated lobby capture may show a listing to one observer; a successful rules load may show more; a completed round record may establish that a session occurred at that time. Each finding has a different scope. State the hostname, date, account context and stage observed, and avoid converting it into a universal access claim.
For an unresolved round, preserve stake acceptance, all decision messages, balances, round ID, timestamps, rules and correspondence. Ask for the server-side event chronology and the clause used for settlement. Share redacted copies and never provide a password, one-time code or wallet secret. If essential identifiers cannot be obtained, state that the timing or configuration claim remains unresolved.
Questions
Questions for this evidence task
Is present Aviator access established here?
No. This guide provides a verification method and makes no claim about current listing or launch access.
What proves that a cash-out style request was accepted?
The strongest evidence combines the round ID, status message, timestamps, ledger movement and provider or server event record.
Does a result history prove fairness?
No. It can help identify rounds, but it does not establish the outcome process or completeness of the history.
Should I repeat a disputed timing action?
No. Preserve the affected round and stop. Further stakes add risk and do not establish what the server received earlier.