A zero Free Spins counter does not by itself prove settlement
Published — UTC
A counter reaching zero can mean no spins remain. It does not necessarily establish that the final award has been calculated and credited. Counter state and monetary settlement need separate fields.
Three checkpoints after the last spin
This is an invented event sequence, not a claim about a tested supplier interface.
| Checkpoint | Spins remaining | Award state |
|---|---|---|
| A | 0 | Final calculation pending |
| B | 0 | Summary calculated |
| C | 0 | Credit confirmed in history |
The counter is identical at all three checkpoints. Only C confirms a credited amount in this model. A screenshot of zero therefore cannot choose between these states.
Preserve the round boundary
Record the feature ID and its last accepted round. A pending summary should not be counted as another spin, and refreshing a page should not generate a second return row for the same confirmed credit.
The British interrupted-gambling reference discusses handling incomplete games in its scope. It does not promise recovery, timing or refunds from a local game.
Report what is confirmed
If only the zero counter is visible, record “no spins remaining; settlement not confirmed.” Keep the summary amount separate until its monetary status is clear. Do not start another paid round to test whether a credit arrives.
A wallet example across the three checkpoints
Assume the wallet holds 100 units before the final award and there are no other transactions. At A, the award is not yet known. At B, the summary reports 12, but the ledger has not confirmed a credit; record a 12-unit summary and leave its credit status pending. At C, a linked credit of 12 appears and the wallet reconciles to 112.
Adding 12 at B and another 12 at C would invent a 124-unit wallet. The summary and its matching credit are two representations of one return in this model. A different product might record components or earlier partial credits, so identify what the summary includes before applying the same arithmetic.
Counter scope matters after the final spin
A counter may describe spins remaining while an animation or cascade from the final spin is still completing. Conversely, a stale display can show a value from an earlier checkpoint. Neither possibility can be resolved from the numeral alone. Compare the feature ID, final-round ID, record timestamp and status; a fresh page load is not itself settlement evidence.
A correction is not another feature
If the confirmed 12-unit credit is later corrected to a final total of 10, distinguish a replacement-total record of 10 from a linked adjustment of −2. With a 100-unit starting wallet and no other activity, both valid representations lead to 110. Subtracting 2 and then replacing the 12 with 10 would apply the same correction twice.
If the ledger provides neither a matching credit nor a clear failure status, keep the outcome unresolved. Preserve the feature and transaction identifiers needed to investigate it. The counter, the displayed summary and the posted money should remain separate fields until their relationship is evidenced.