Deposit Limit Presets Start at kn 200, 46% Never Edit Down

Croatian licensed operators have to offer a deposit limit that starts at kn 200 — roughly €26.54 — and the data that has leaked out of player-protection dashboards since the 2022 Gambling Act came into force suggests a stubborn pattern: about 46% of players who set a limit never touch it again. Not a single downward revision, not a pause, not a switch from monthly to weekly. They set the floor and walk away from the setting entirely. That number matters less as a curiosity about user behaviour and more as a quiet indictment of how limits are framed, timed, and defaulted at registration.

The kn 200 floor is a regulatory minimum, not a recommendation

Under the Zakon o igrama na sreću, operators holding a Hrvatska lutrija-adjacent or Ministry of Finance-issued licence must let players cap deposits at a level no higher than kn 200 per day, week, or month. The law sets a ceiling on what the operator can force as a minimum — meaning no casino can tell you "our lowest limit is kn 500, take it or leave it." That is the actual function of the number. It is a floor for consumer protection, not a target.

The confusion is understandable. When a registration flow presents "kn 200" as the first option in a dropdown, pre-selected, next to "kn 500," "kn 1,000," "kn 2,000," and "No limit," a meaningful slice of players read it as the house recommendation. It sits at the top of the list. It is the smallest number. It feels responsible. So they pick it, confirm, and move on — and the screen never asks them again.

Compare that to how the same operators handle, say, a welcome bonus. A €200 match plus 100 free spins triggers three emails, a push notification, and a pop-up on next login. A deposit limit set once at registration triggers nothing. The asymmetry is not accidental. Limits are a compliance checkbox; bonuses are revenue. Nobody's KPI depends on whether you revisit your cap.

Why the 46% figure is a floor, not a ceiling

The 46% "never edited" number almost certainly understates the problem. It counts only players who set a limit at all. Croatia's broader player base includes a large cohort who never engage with the tool — they click past the responsible gambling page, accept the default "no limit," and only encounter a cap if they self-exclude or a payment processor forces one. Among players who do set a limit, 46% never revisit it. Among all players, the share who actively manage their deposit exposure is smaller still.

There is also a definitional trap. "Never edited down" and "never edited" are different things. Some of that 46% may have raised their limit — which under the law requires a cooling-off period (typically 24 hours to 7 days, depending on the operator and the size of the increase). A player who sets kn 200, then raises to kn 1,000 after the mandatory delay, has edited the limit. They are not in the 46%. The 46% are the ones who set it and left it, in either direction. Given that raising a limit is friction-heavy and lowering it is instant, the near-total absence of edits suggests most of these players simply forgot the setting exists.

What "set once, never touched" actually tells us

A deposit limit that never changes is not necessarily a healthy limit. It is a limit that has been decoupled from the player's actual financial life.

Consider the timeline. A player registers in March, sets kn 200 per week, and deposits kn 200 that Friday. By June, their circumstances have shifted — a raise, a new rent, a holiday, a bad month. The limit is still kn 200 per week. If their income went up, the limit is now less protective than they intended. If their income went down, the limit is now more permissive than they can afford. Either way, the number no longer reflects the decision it was meant to encode.

This is the core failure of the "set and forget" model. Limits are treated as a one-time consent event rather than an ongoing calibration. Regulators in Croatia, following the broader EU pattern, have focused on availability of limits — can a player set one, is the minimum low enough, is the cooling-off period long enough. They have paid far less attention to maintenance — does the player ever review the number, does the operator ever prompt a review, is there any mechanism that surfaces the limit at a moment when the player might want to change it.

The 46% figure is the symptom. The disease is that a deposit limit is presented as a setting rather than a practice.

The cooling-off asymmetry

One structural reason players do not edit limits downward is that they rarely need to. Lowering a limit is instant and painless — you tap a button, it applies immediately, and you can go lower any time. Raising a limit is deliberately slow. Croatian operators typically enforce a 24-hour delay for modest increases and up to seven days for large ones, with the request often requiring a support ticket or a written confirmation rather than a self-service click.

That asymmetry is correct on paper. It stops a player in a losing session from lifting their own cap in the moment. But it creates a friction gradient: the easy direction is down, the hard direction is up, and the default direction is nothing. When the path of least resistance is to leave the setting alone, most people leave the setting alone. The 46% are not making a choice to keep kn 200. They are declining to make a choice at all.

The kn 200 limit in context: is it the right floor?

kn 200 per day is a strange unit if you think about it. Croatia's average net monthly salary has hovered around kn 7,800–8,200 in recent years — call it roughly €1,050–1,090. A kn 200 daily cap, sustained every day, is kn 6,000 a month. That is 73–77% of a median net salary going to a single casino. As a weekly cap, kn 200 is far more conservative — about kn 870 a month, or roughly 11% of median net pay.

The law lets the operator and player choose the period. Daily, weekly, monthly. Same number, radically different exposure. A player who selects "kn 200" without registering whether the dropdown says daily or weekly has set two completely different limits depending on a field they may not have read. And since 46% never edit, that ambiguity is locked in.

This is not an argument for raising or lowering the floor. It is an argument that the floor is doing less work than it appears to. kn 200 reads as a small, safe number — small enough that players accept it without scrutiny. That is precisely why it gets accepted without scrutiny, and why so many of those acceptances are never revisited.

What a better default would look like

Three changes would move the 46% without touching the kn 200 minimum:

Period-first selection. Ask the player to choose daily, weekly, or monthly before showing any numbers. The number means nothing without the period, and forcing the period first makes the player think about the shape of their spending, not just its size.

A scheduled review prompt. At 30, 90, and 180 days after a limit is set, surface a neutral prompt: "Your limit is kn 200 per week. Is that still right?" Not a nudge to raise it, not a warning, not a bonus offer — a plain question with "keep" and "change" as equals. Operators already have the data to trigger this. They do not do it because there is no commercial upside and a small retention risk.

Percentage-of-income framing. Instead of a flat kn figure, offer an optional anchor: "kn 200 per week is about 11% of the Croatian median net monthly salary." Players who see the ratio make better decisions than players who see a bare number. This is standard practice in consumer finance for loan affordability; there is no structural reason it cannot appear in a deposit-limit screen.

None of these require new legislation. All three are within an operator's power today. The reason they are rare is the same reason the 46% exists: nothing about the current setup rewards the operator for improving it.

Where the operator's interest and the player's interest actually diverge

It is tempting to read the 46% as evidence that limits work — players set them and stick to them. That reading is backwards. A limit that is never reviewed is a limit that is never tested against the player's real life. It is compliance, not protection.

The operator's incentive is to make the limit-setting step as quick and frictionless as possible at registration, because every extra field is a drop-off risk. The player's interest is to set a limit that reflects their actual disposable income and gets revisited when that income changes. Those two interests align at the moment of setting and diverge immediately afterward.

Croatia's regulatory framework has, to its credit, made the floor low and the cooling-off real. What it has not done is build in any mechanism for the limit to stay alive. The 46% is what you get when a protective tool is designed as a one-time form field. The number is not a behavioural mystery. It is a design outcome.

The open question is whether it takes another regulatory nudge — a mandated review prompt, a period-first flow, a transparency requirement on how limits are presented — or whether any operator will move first and treat an actively maintained limit as a retention feature rather than a compliance cost. Given that the players most likely to review their limits are also the ones least likely to churn after a bad month, there is a commercial case sitting there unclaimed. Whether anyone in Zagreb or the licensed operator base picks it up is the part the data cannot yet tell us.