Use a round identifier to make a precise query
A screenshot can show an appearance; a round identifier helps the operator locate the corresponding event in its records.
The distinction that matters
Keep the game name, time, timezone, round ID and observed issue in a private note. Do not assume that a session ID, support ticket and round ID are interchangeable. If the game does not display a round identifier, ask where its history can be found rather than inventing one from the time.
A worked example
A query saying 'the game paid incorrectly yesterday' leaves many possibilities. A query that names the game, identifies the round and explains which rule appears inconsistent gives support a defined event to investigate. Sensitive account data should still stay in the operator's authorised channel.
Your next steps
- Record the identifier type and exact value privately.
- Note the observed stake and payout without changing the record.
- Attach the applicable rule reference.
- Ask for the operator's explanation of that round.
Where this answer stops
Northline does not receive round records or adjudicate outcomes. A round identifier makes a query more specific; it does not prove that an error occurred or guarantee a particular resolution.
Sources & reading
Original Northline explanation. Worked examples use stated assumptions; they do not establish an operator’s policy or predict personal results. Read how we handle evidence.
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction