A withdrawal fee that only becomes visible on the fourth screen of a cash-out flow is not a minor UX quirk. It's the point where nearly half of players walk away: in a review of cash-out sessions across 12 operators, 47% of users who reached a fee disclosure at step 4 abandoned the withdrawal entirely. The money stayed in the account, and in most cases it went back into play.

That number comes from funnel data covering roughly 310,000 withdrawal attempts over six months in 2024. It's the kind of figure that should make anyone running a payments stack uncomfortable, because it says the fee isn't being absorbed as a cost of doing business — it's being routed back into the deposit column.

Where the fee actually lives

Most operators will tell you their withdrawal fee is disclosed. Technically, they're right. It sits in the banking terms, usually a sub-clause under "processing times and charges," and it appears in the cash-out flow itself — just late.

The sequencing problem is structural. Step 1 selects the method. Step 2 confirms the amount. Step 3 asks for verification if the account isn't fully KYC'd. Step 4 shows the summary: amount requested, processing time, and then the fee. By the time a player sees it, they've committed four taps and a security code to a number they thought was final.

Across the sample, the median fee was 2.4% of the withdrawal, capped at €5 on e-wallets and uncapped on bank transfers at three of the twelve operators. On a €40 cash-out, that's a rounding error. On a €900 cash-out via bank transfer at an uncapped operator, it's the difference between a good session and a complaint to support.

The step-3 verification squeeze

Worth separating two effects that get bundled together. Some abandonment at step 4 isn't really about the fee — it's KYC fatigue. Players who hit a document upload at step 3 are measurably more likely to bail at step 4 regardless of what the fee says. In the sample, sessions with a mid-flow verification request abandoned at 61%, against 38% for sessions where KYC was already complete. The fee is the visible trigger; the friction underneath it is doing half the work.

Why operators keep the fee late

Two reasons, and neither is incompetence.

First, fee revenue on withdrawals is small. Most of the 12 operators cleared under 0.3% of gross gaming revenue from withdrawal charges. It's not a profit centre — it's a cost-recovery line for payment providers who charge per payout, especially on bank rails and card reversals.

Second, and less comfortably: late disclosure keeps the fee out of the decision to deposit. A player comparing two casinos sees the welcome bonus and the wagering, not the cash-out charge. Moving the fee to the front of the flow makes the comparison honest, and honest comparisons cost conversions.

That trade-off is real, and it's the reason the 47% figure keeps getting filed under "known issue" rather than "fixed."

What front-loading actually costs

The counter-evidence is thin but consistent. Two of the twelve operators in the sample disclosed withdrawal fees on the deposit page and again at step 1. Their step-4 abandonment ran at 19% and 22% — less than half the sample average. Their deposit conversion was 4 to 6 percentage points lower than the group median.

So the question isn't whether late fees suppress withdrawals. They clearly do. It's whether the deposits those fees protect are worth more than the trust they spend. A player who cancels a €900 cash-out at step 4 and loses it back over the following week is a good quarter for the operator and a bad year for the relationship — and the ones who notice tend to notice permanently.

The uncomfortable part for the industry is that nobody has clean data on the second-order effect: how many of those 47% never deposit again. That's the number worth measuring, and as far as the sample goes, nobody is.