Guide · Safer gambling
Limits are enforced before launch, not inside each game
A deposit limit the slot remembers and the sportsbook ignores is not a limit. The player account is the only place that can see every product. Studios see rounds.
7 min readUpdated By the Turnkeyxgaming team
Refuse the launch, don't hope the game cooperates
When a player hits a limit you set, stop the next debit at the wallet and stop the next launch in the lobby. A game that is already open may still send a debit. The wallet refusal is the backstop. A polite message in the lobby is the experience. Relying on a studio setting means the one studio that does not implement it becomes the hole.
Time-outs and self-exclusion are the same pattern. They are account states. They should close open game sessions, not only hide the cashier. A player who cannot deposit but can still stake their remaining balance may be inside your rules. A player who is excluded and can still open a game is not. Know which state you implemented.
Apply the check in the player-account service every product already calls, including sport. A slot wrapper that remembers a deposit cap, while the sportsbook reads a different field, is two limits. Cooling-off on an increase belongs in that same service: the higher cap does not take effect until the wait you configured has finished, and no studio setting can shorten it. Decreases apply immediately, including to a game that is already open, by refusing the next debit.
Which account state stops which action
Studios see rounds. The only place that can see every product is the player account. Enforce the state there, and let the wallet be the backstop.
| State | New launch | Debit already in flight | Cashier |
|---|---|---|---|
| Deposit limit reached | Existing balance may still stake, if that is the rule you wrote. | Allowed until a different limit, such as loss, says otherwise. | Further deposits refused. |
| Loss or stake limit reached | Refuse. Do not open another game on the remaining balance. | The wallet declines the debit with a clear error. | Unrelated, unless your policy links them. |
| Time-out | Refuse. | Decline, and close the open session rather than waiting for the player to leave. | Hidden or refused, matching the time-out you actually implemented. |
| Self-exclusion | Refuse. | Decline, and end open sessions when the exclusion starts. | Refused. This is not a deposit-only switch. |
Put the control where every product passes
- 01
Wallet refusal
Decline debits that would break a loss or stake limit, with a clear error.
- 02
Lobby refusal
Do not launch a new game when the account is excluded or timed out.
- 03
Close sessions
End open sessions when exclusion starts, rather than waiting for the player to leave.
One studio without the setting becomes the hole
A limit that lives in a game client's preferences works only for that client. The sportsbook, the live table and the next slot never see it. Refuse the launch in the lobby and the debit in the wallet, or you do not have a limit.
Worked example
A limit change while the player is in a session
A player asks to raise a €100 monthly deposit limit to €300 on the 10th, having already deposited €80. The higher limit does not take effect until the cooling-off period you published has passed. Until then, the €100 limit still applies, and the player can deposit €20 more. The platform shows the pending change and the date it starts, so support is not guessing.
A decrease is different. If the same player lowers the limit to €50, apply it immediately and enforce it on the next deposit and on the next debit that the new loss or stake rule covers. Do not wait for a cooling-off period that only exists to slow increases. The account state, the cashier and the wallet all read the same limit record; a cached copy in a game client is not a limit.
Increase and decrease follow different clocks
| Change | When it applies | What the player sees |
|---|---|---|
| Increase | After the published cooling-off period | The pending amount and the date it starts |
| Decrease | Immediately | The new limit and the next deposit it affects |
| Time-out | Immediately, and it closes open sessions | The end date and what is unavailable |
| Self-exclusion | Immediately, across products | The exclusion period and the support route |
FAQ
Questions operators ask
Can a studio raise a player's deposit limit?
No. Studios do not hold the player account. Any limit change happens in your platform, under your policy and any cooling-off rule that applies.
Can a player raise their own deposit limit by asking in game chat?
No. Studios do not hold the account. A change happens in your platform, under your cooling-off rule. Chat cannot shorten that wait, and a dealer cannot confirm a higher cap.
Does a deposit limit stop stakes automatically?
Only if you wrote it that way. A deposit limit stops deposits. A loss limit stops stakes. Implementing the first and describing it as the second leaves the remaining balance playable, which may be correct and must be the rule you meant.
Should a pending increase be visible in the cashier?
Yes. Show the current limit and the pending one with its start date. A player who cannot see why a deposit was refused will assume the platform is broken, and support will have to explain a rule the interface hid.
Keep reading
Related pages
- Solution · PlatformCasino platformPlayer accounts, a back office, a bonus engine and multi-brand support, wired to the game aggregator and the shared wallet.Read
- Guide · Safer gamblingReality checksSession length and net result belong to the operator's clock. The studio only sees the rounds it dealt, never the whole session.Read
- Product · PaymentsPaymentsDeposits and withdrawals stay with your payment firms. The aggregator never moves SEPA, cards or USDT and never holds player funds.Read
- Guide · AccountsWho owns the playerThe operator keeps identity, KYC, limits and the balance. Studios receive a player id, never the passport scan behind it.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.