High Five Studio

November 2026

Cash-Out Queue Hides Behind 3 Tabs, 36% of Croats Time Out

A 2025 usability review of 42 Croatian casino interfaces found cash-out buried behind three tabs, with 36% of players timing out before finding it

Cash-Out Queue Hides Behind 3 Tabs, 36% of Croats Time Out

In 2025, a review of 42 Croatian-facing online casino and sportsbook interfaces found that the cash-out function was, on average, buried two clicks deep and behind three separate navigation tabs before a logged-in user could reach it. In a timed usability test with 180 Croatian players aged 24 to 61, 36% failed to locate the cash-out option within a 90-second window and abandoned the session — a failure rate that maps almost exactly onto the share of live-chat complaints about "missing withdrawals" logged by two Zagreb-based support desks in the same quarter.

That number is the point of this article, not a decoration. The cash-out queue — the path between a player deciding to withdraw and the request actually entering the operator's processing pipeline — is one of the least examined and most consequential pieces of interface design in the Croatian market. It sits at the junction of UX, licensing compliance, and the practical reality that a withdrawal the player cannot find is functionally a withdrawal the player does not make. What follows examines where the queue hides, why it hides there, what the Croatian regulatory and market context does to that design, and what the 36% figure actually tells us about how players behave when friction is placed in front of their own money.

The anatomy of a hidden cash-out

The three-tab structure is not accidental. Across the 42 interfaces reviewed, the most common pattern placed the cash-out control inside a "Wallet" or "Balance" tab, which itself sat inside an account hub, which was reached through a hamburger menu that on mobile opened a full-screen overlay. Reaching the cash-out screen from the lobby required, in the median case, four interactions: menu, account, wallet, withdraw. On desktop the count dropped to three. On mobile — where the majority of Croatian sessions now originate — the count rose to five on nine of the reviewed sites because the account hub opened as a nested drawer that had to be scrolled.

The 90-second window in the usability test was chosen deliberately. It is roughly the point at which a player who has just won, or who has decided to stop, is still in the decision. Past that window, behaviour changes: in the test, players who had not located cash-out by 90 seconds either returned to the lobby (61% of failures) or opened live chat (22%). Only 17% persisted in navigating. The return-to-lobby group is the interesting one, because returning to the lobby is, in behavioural terms, a re-entry into play. A player who came to withdraw and instead finds themselves looking at the game grid is a player the interface has quietly redirected.

Why "three tabs" is the wrong unit of measurement

Three tabs sounds trivial. It is not, because tabs are not the real cost. The real cost is the uncertainty each tab introduces. A player who knows exactly where cash-out lives will click through three tabs in under ten seconds. A player who does not know — and the majority of occasional players do not — has to read each screen to confirm they are on the right path. Each tab is a decision point, and decision points are where abandonment happens. The usability test measured time-to-locate, not click count, for this reason. The median successful time was 34 seconds; the median failure was not a slow success but a complete loss of the path.

This matters for how operators think about the problem. Moving cash-out from four clicks to two clicks helps, but only if the two clicks are unambiguous. Several of the reviewed interfaces had a two-click path that was worse than a four-click path because the second click landed on a page with three competing "withdraw" and "deposit" buttons of near-identical visual weight. The player's problem was not distance. It was signal.

What the Croatian market does to the queue

Croatia's online gambling framework, administered under the 2019 Law on Games of Chance and its subsequent amendments, requires licensed operators to maintain clear procedures for player withdrawals and to process them within defined timeframes — in practice, most licensed operators commit to 24 to 72 hours for e-wallet and card withdrawals respectively, with bank transfers running longer. The law does not prescribe interface design. It prescribes outcomes. That gap is where the cash-out queue lives.

The practical consequence is that an operator can be fully compliant on processing time — paying every withdrawal within the stated window — while still presiding over a 36% abandonment rate at the point of request. Compliance measures the operator's behaviour after the request is made. It does not measure whether the request is made at all. A player who never finds the button never triggers the clock, and from the operator's reporting perspective, that player simply did not withdraw. The queue is invisible in the compliance data because the queue is upstream of it.

The KYC layer compounds the friction

Croatian operators are required to complete identity verification before a first withdrawal, and the verification step is frequently bundled into the withdrawal flow rather than handled at registration. This is defensible on fraud-prevention grounds, but it has a predictable effect on the queue: a player who finally locates cash-out after 40 seconds of navigation is then asked to upload a document, wait for review, and return. In the usability test, players who hit the KYC wall mid-flow were not counted as cash-out failures, but the live-chat data suggests many of them never returned to complete the request. The withdrawal sat in a pending-verification state until the player's intent decayed.

The fix here is not to remove KYC — that is not on the table under Croatian rules — but to front-load it. Operators that prompt verification at registration, or at first deposit above a threshold, report materially lower abandonment at the withdrawal stage. The 36% figure in the title is a cash-out discovery failure, but discovery failures and verification failures compound. A player who cannot find the button and a player who finds it and then gives up at the document upload are, from the operator's revenue perspective, the same player.

The 36% is not a UX statistic, it is a retention statistic

It is tempting to file the 36% under interface design and move on. That would be a mistake, because the number correlates with something operators care about more than clicks: whether players come back.

In the usability test cohort, players who failed to locate cash-out within 90 seconds were tracked for 30 days afterward. Their return rate to the same operator was 41% lower than the successful group. This is counterintuitive if you assume players withdraw because they are leaving. In fact, the opposite is closer to the truth: a player who withdraws successfully and quickly has had a good experience with the operator's money-handling, and good money-handling is the single strongest predictor of return in a market where trust in online payment is still being built. A player who cannot find the cash-out button has had the opposite experience. They have been made to feel that the operator is reluctant to pay them, whether or not that is true.

This is the part of the cash-out problem that gets lost in the UX-versus-compliance framing. The hidden queue is not neutral friction. It reads, to the player, as intent. And in Croatia specifically, where the licensed market is relatively young and where a meaningful share of players have prior experience with unlicensed or grey-market sites, the read is sharper. Players who have been burned before are primed to interpret a buried withdrawal button as a warning sign. The 36% who time out are not just failing a navigation task. A portion of them are drawing a conclusion about the operator.

The asymmetry operators underweight

Deposit flows are, almost universally across the 42 reviewed interfaces, one or two clicks from the lobby, often with a persistent deposit button in the header. Withdrawal flows are three to five clicks deep. No operator would defend this as a deliberate strategy, but the asymmetry is consistent enough to be structural rather than accidental. It reflects a design process that optimises for the deposit funnel — the revenue event — and treats the withdrawal funnel as a compliance obligation to be satisfied rather than a user journey to be designed.

The cost of that asymmetry is not visible on a monthly P&L, which is precisely why it persists. Abandoned withdrawals do not appear as a line item. They appear as slightly higher than expected player balances, slightly lower than expected withdrawal volumes, and slightly worse retention than the operator can explain. The 36% is a way of making the invisible visible. It is a rough number from a 180-person test, not a market-wide measurement, but the direction is consistent with the live-chat data and with the retention gap. The precise figure will vary by operator and by device mix. The phenomenon will not.

What actually moves the number

The interventions that reduced time-to-locate in follow-up testing were not exotic. They were, in order of effect size: a persistent cash-out control in the header alongside the deposit button (median time-to-locate fell from 34 seconds to 11); a single-screen withdrawal flow that did not route through a wallet tab at all (failure rate fell from 36% to 14%); and pre-populated withdrawal methods that defaulted to the player's last-used deposit method (a smaller effect on discovery but a large effect on completion once the player arrived).

None of these require regulatory change. None require new licensing. They require an operator to decide that the withdrawal journey deserves the same design attention as the deposit journey, which is a decision about priorities rather than about compliance. The operators that have made it report the retention benefit within a quarter.

The harder question is whether the market will make that decision on its own. There is no competitive pressure to surface cash-out prominently, because a player cannot compare withdrawal flows across operators before signing up — the flow is behind a login. The 36% who time out do not know that a competitor would have taken them to cash-out in eleven seconds. They only know that this operator made it hard. And the operator, looking at the data, sees a player who did not withdraw rather than a player who tried and failed.

That is the open question this article leaves hanging. If the cash-out queue is invisible to compliance, invisible to the P&L, and invisible to the player's ability to comparison-shop, what force is supposed to fix it? Responsible-gambling advocates will argue — correctly — that easy withdrawals are a player-protection measure, and that burying cash-out behind three tabs is a soft nudge toward continued play that no licensed operator should be designing into its product. Operators will argue — also correctly — that they process every withdrawal they receive within the stated window, and that the law asks nothing more. Both are right, and the 36% sits in the space between them. Until someone measures the queue as a player-protection metric rather than a UX curiosity, the number will keep showing up in tests like this one, and the players behind it will keep quietly going back to the lobby.