Your provider in email marketing

A 30-second hold on the first deposit, and 43% close the app

· 2 min read
A 30-second hold on the first deposit, and 43% close the app

A 30-second hold on the first deposit screen pushed 43% of new users to close the app before the hold cleared. That figure comes from a 2024 checkout-friction study covering 2.1 million first-deposit attempts across 14 operators, and it reframes something the industry usually treats as a compliance checkbox: the pause between "Pay" and "Approved" is a product decision with a measurable body count.

Where the drop-off actually happens

The 30 seconds in question isn't the payment processor's fault, mostly. In the studied flows, the hold was a pre-authorization step layered on top of the processor call — an internal fraud screen, a KYC soft check, or a manual review trigger that fired on a fraction of users but stalled the whole queue.

Break the 43% down and it's less uniform than it sounds:

  • 0–10 seconds: roughly 4% abandon. This is normal payment anxiety, and most of those users come back.
  • 10–30 seconds: the curve steepens hard. Another 22% leave in this window.
  • Beyond 30 seconds: abandonment climbs toward 60% by the 90-second mark, and the users who leave here rarely retry the same session.

The 10-to-30-second band is the expensive one. It's long enough for doubt to set in, short enough that the user hasn't committed to waiting.

Why players bail at the half-minute mark

A first deposit is the highest-trust moment in the customer lifecycle. The user has already cleared registration, probably verified an email, and talked themselves into spending money at a site they've known for maybe six minutes. A spinner with no explanation reads as one of three things: the site is broken, the payment failed, or something is being checked that they'd rather not have checked.

Operators who instrument this see it in session recordings. Users tap the screen, back out to check their banking app, and don't return. On mobile — where the majority of first deposits now happen — the app-switch is the kill shot. The browser tab or app gets backgrounded, and the return rate inside 60 seconds sits under 15% in most of the datasets I've seen.

The KYC timing problem

Part of the friction is structural. Regulators in several markets now expect identity checks before or during the first deposit, and those checks take time. The mistake is running them synchronously in the payment flow rather than in parallel. Operators that pre-screen at registration, or that fire the check alongside the processor call instead of after it, cut the visible hold to single digits in seconds without weakening the control.

What the 43% number doesn't tell you

Abandonment isn't the same as lost revenue. Some of those 43% complete a deposit later — the study put 24-hour recovery at about 38% of abandoners, which leaves roughly 27% of the original cohort gone for good. That's still a large number of first-time depositors lost to a UI decision, and the recovery rate worsens the longer the hold runs.

There's also a selection effect worth flagging: users who abandon at 30 seconds skew toward lower deposit amounts and, in some operators' data, higher later lifetime value than the users who sail through. The friction may be filtering out exactly the wrong people.

The open question

If a 30-second hold costs you a quarter of your first-time depositors permanently, what's the actual cost of the fraud and chargeback exposure that hold is preventing? Most operators can quote the first number. Very few can quote the second with any confidence — which means the hold length is usually set by risk teams optimizing for a loss they can see, against a loss nobody's measuring. Until someone puts both numbers on the same dashboard, the 30 seconds stays.