GodisaGeek AU · Account and offer guide
Pokie RTP versions
A published return percentage belongs to a mathematical configuration, not merely a game name. Use the active game’s help information when comparing the version offered through an account.
View partner site ↗Four fields to keep together
| Required detail | Action | What the record should establish |
|---|---|---|
| Value shown in current help | Identify the starting record | Keep the original label and its amount, currency or event identifier. A rewritten summary can omit the unit that makes the value comparable. |
| Exact title and configuration | Apply the actual condition | Use the condition attached to this specific transaction or offer. Record the calculation basis and the point at which the condition is evaluated. |
| Whether optional modes use another specification | Compare the matching result | Compare the outcome with the same category in the account record. A pending entry and a settled entry may describe different stages of one event. |
| Separate volatility and maximum-win fields | Keep the unresolved item precise | If this field is absent, ask for it directly and retain the answer with the corresponding reference. This makes the next comparison reproducible. |
These fields form one compact comparison record. Keep them together with the date and the relevant transaction, offer or case reference. That prevents a condition from one version being attached to a result from another. When a service changes its wording, the saved record also shows which condition was visible for the event being discussed.
The detail that changes the comparison
A developer page may publish one specification while an operator integration offers another permitted configuration. Record the exact value and its source rather than assuming every instance of the title uses the first percentage found in a review.
RTP is a long-run model property, not a cash refund or a forecast for one session. A useful comparison keeps it separate from volatility, feature frequency and the maximum win. A higher maximum win does not establish a higher RTP.
A worked comparison
Example conditions
If two hypothetical configurations list 96% and 94%, their model difference is two percentage points. It does not mean the first will return exactly A$96 from a particular A$100 session.
Use the same assumptions on both sides of the comparison. If one proposal uses a different currency, period or balance category, translate that difference explicitly before comparing its result. A numerical example answers the arithmetic question; the written terms answer whether those inputs apply to the account.
For an actual record, keep the original amount and the calculation alongside the result. Rounding can be applied at different stages, particularly with percentage charges, exchange quotes and reward points. When a small difference remains, the rounding rule is a more useful next question than replacing the source figure with an estimate.
Keep the edition and configuration together
Record the full game title, provider and the help-screen value being compared. A family name can cover several releases, and a release can have more than one mathematical configuration. The exact combination is the useful comparison key.
Separate published facts from observations. A provider specification supports the listed feature, while an account screen establishes the version actually offered there. A review should not silently import a maximum, return percentage or optional mode from a related title simply because its artwork looks similar.
Connect the interface to the record
Identify what the user sees, which action it describes and where the result is recorded. A game screen, promotion panel and cashier can display related but different information. The most useful interface explanation follows one action across those screens instead of judging a layout only by its appearance.
For an unresolved result, preserve the exact title, relevant timestamp and identifier. A cropped image can help locate a control, but a complete record explains the amount and status. Keep those evidence types together when comparing the experience or asking the account service for clarification.
Practical questions
Can a short demo session verify RTP?
A small observed sample cannot establish the game’s long-run theoretical percentage.
What information makes this comparison usable?
Keep value shown in current help, exact title and configuration, whether optional modes use another specification, and separate volatility and maximum-win fields in the same record. Those fields connect the headline condition to an identifiable account event.
Does an example establish the current account terms?
The examples explain a calculation or decision with stated assumptions. The current offer, cashier quote or account response supplies the applicable figures. Keep that source with the date and reference used for the comparison.
Related decisions
Use the comparison above to read the current account details and available options on the partner site.
Open partner site ↗Reference for this decision
This guide explains account terminology and hypothetical calculations. No operator-specific processing time, supported payment route or live reward is inferred from the example.
Editorial method · All account and offer guides · VIP proposal comparison