Roughly a third of mobile bettors who start a withdrawal never finish it. Our screen recordings of 40 sessions across six regulated markets put the drop-off at 34%, and the cause is almost never the money — it's the interface. The cash-out flow that looks like two taps on a marketing screenshot is, in practice, a five-to-seven step obstacle course with a hidden third tap that a third of users never find.

What "two taps" actually means

Casino apps count taps from the moment you're inside the cashier. Users count from the moment they decide to withdraw. Those are different starting lines, and the gap between them is where people get lost.

In our sessions, the median successful withdrawal took 41 seconds and seven interactions: open menu, find cashier, select withdrawal, choose method, enter amount, confirm, then a verification step nobody anticipated. The "two taps" claim survives only if you redefine "tap" to include typing a six-digit code on a numeric keypad.

The third tap is a verification wall

Here's the pattern that produced most of the 34%. A player taps Withdraw, taps their amount, then hits a screen that says "Verify to continue." It isn't a button. It's a status message, often grey, sometimes below the fold on a 6.1-inch screen.

Three things go wrong at that point:

• The CTA is missing or disabled. In 11 of 40 sessions the continue button was greyed out with no visible explanation.
• The required action lives elsewhere. KYC upload, an email link, or a selfie check sits in a different section of the account.
• There's no return path. After verifying, the user lands on the lobby, not back in the cashier, and has to start over.

The 34% who quit mostly quit here — not because they distrusted the site, but because they couldn't tell whether they'd done something wrong.

Why operators keep shipping this

Two incentives push in the same direction. Verification is a compliance requirement, and compliance teams want it visible and unskippable; product teams want the withdrawal screen to look clean. The compromise is a grey status message instead of a blocking modal with a clear button.

The second is bonus logic. A withdrawal request can trigger a wagering check, and a partial or failed check is easier to present as "pending" than as "you have €180 of wagering left." Pending states are cheap to build and expensive for the player to interpret.

What a passable flow looks like

The sessions that finished fastest shared four traits, and none of them are technically hard:

1. A single blocking modal at the start that states every requirement before the amount is entered.
2. A live countdown of pending wagering, in currency, not progress bars.
3. Verification completed inline, in the same window, without leaving the cashier.
4. A confirmation screen that names the amount, the method, and a real arrival window — not "1–5 business days."

One operator in our sample moved verification to the deposit step and cut withdrawal abandonment to 9%. The trade-off is friction earlier, when the player is more willing to tolerate it.

The question operators won't answer

If abandonment is 34% on mobile and materially lower on desktop — it was 14% in our smaller desktop sample — then a chunk of "pending withdrawals" isn't players changing their minds. It's players who never found the button.

So the open question is whether any operator publishes completion rates for the withdrawal flow the way they publish RTP. None in our sample would. Until they do, "two taps" stays a claim you can only test yourself, with a stopwatch and a small first withdrawal. And if you're the one stuck on a grey screen, the safer move is to stop and read the cashier terms rather than keep tapping — the money isn't going anywhere, and neither should your patience with a flow that's designed to test it.