Home › One-Tap Deposit Repeat Presses Fall 38% With a 5-Second Hold

One-Tap Deposit Repeat Presses Fall 38% With a 5-Second Hold

One-Tap Deposit Repeat Presses Fall 38% With a 5-Second Hold

A five-second press-and-hold on the deposit confirmation button cut repeat deposit attempts by 38% across a 14-week trial covering 61,400 cashier sessions at three licensed operators, according to figures circulated to participating compliance teams in March. The finding matters less for the headline number than for what it implies: a friction cost of roughly five seconds per deposit appears sufficient to interrupt the reflexive second and third press that follows a slow-loading payment page. The trial, run between November 2024 and February 2025, compared a standard one-tap confirmation against a hold-to-confirm variant served to a randomly assigned half of the sample.

What the trial actually measured

The primary endpoint was not deposit volume but repeat presses within 90 seconds of an initial confirmed deposit — the behaviour pattern where a player, unsure whether the first transaction registered, taps again and either double-funds the account or triggers a duplicate pending transaction. In the control arm, 9.1% of sessions produced at least one repeat press inside that window; in the hold-to-confirm arm, 5.6%.

Two details matter for interpreting the 38% figure. First, it is a relative reduction, not an absolute one — the absolute drop is 3.5 percentage points. Second, the effect was concentrated almost entirely in sessions where the payment provider's response exceeded 2.5 seconds. In fast-response sessions the two arms behaved almost identically (2.2% versus 2.0%), which suggests the hold is not suppressing deposits generally but specifically absorbing the ambiguity window that slow responses create.

Metric One-tap (control) 5-second hold Change
Sessions with repeat press ≤90s 9.1% 5.6% −38.5% relative
Median time to confirmed deposit 6.4s 11.1s +4.7s
Deposit abandonment at cashier 11.8% 13.9% +2.1pp
Support tickets citing "deposit not received" 0.71% of sessions 0.44% −38%

The abandonment trade-off

The 2.1-percentage-point rise in cashier abandonment is the number operators will argue about. A 4.7-second increase in median time-to-deposit is a real cost, and at the upper end of the funnel it will show up in conversion dashboards as lost revenue. Whether that cost is worth paying depends on what the repeat presses were actually doing — and here the trial data is less complete than the headline suggests.

Why the second press happens at all

Cashier interfaces have a well-documented ambiguity problem. When a player taps confirm and the screen does not immediately change state, the reasonable inference is that the tap did not register. The interface has given no signal either way. A second tap is not impulsive behaviour in the way a slot spin is; it is a rational response to missing feedback.

This is why the hold works, and why its mechanism is worth stating precisely. The hold does not add a confirmation dialog, which players dismiss reflexively. It occupies the finger for the duration of the ambiguity window, and it provides continuous visual feedback (a progress ring) that the input has been received. The player is doing something while waiting rather than waiting to do something.

Operators who have tested similar interventions report the same pattern. A 2023 study of 22,000 cashier sessions at a single sportsbook found that adding a spinner animation to the confirm button — no hold, just visible feedback — reduced repeat presses by 19%. The hold outperforms it, but the two mechanisms are not independent: part of the hold's effect is likely the feedback it provides, not the friction itself.

Where the effect does not appear

The trial found no meaningful reduction in repeat presses among players using stored payment methods with instant provider confirmation, and no reduction among players depositing under €20. Both subgroups already had low baseline repeat-press rates (1.4% and 2.9% respectively), leaving little room for improvement. The intervention's value is concentrated in mid-value deposits (€50–€250) on slower payment rails — bank transfers and some local wallet methods — where the ambiguity window is longest.

The regulatory reading

Several jurisdictions have begun treating interface friction as a harm-reduction tool rather than a conversion obstacle. The UK Gambling Commission's 2024 consultation on remote customer interaction stopped short of mandating specific cashier mechanics, but its language on "inadvertent" transactions — deposits a player did not intend to make — maps closely onto the repeat-press problem. A duplicate deposit caused by interface ambiguity is, in the Commission's framing, not a deliberate transaction at all.

That framing has commercial consequences. If a repeat press is classified as inadvertent, the deposit it produces may be subject to reversal or refund obligations that operators have not historically budgeted for. The trial's 38% reduction in "deposit not received" support tickets — from 0.71% to 0.44% of sessions — is the operationally interesting figure here, because support tickets are where inadvertent deposits surface as cost.

There is also a responsible-gambling angle that the trial did not measure directly but that deserves scrutiny. A five-second hold is a modest speed bump. It will not stop a determined player mid-session, and it should not be presented as though it does. What it may do is interrupt the specific micro-pattern — tap, uncertainty, tap again — that precedes some rapid multi-deposit sequences. Whether that interruption has any downstream effect on session length or loss chasing is an open empirical question, and one that a 14-week trial with deposit-press as its endpoint was not designed to answer.

What operators will do with this

The commercial logic cuts both ways. A 38% reduction in duplicate deposits removes a support cost and a regulatory exposure, but it also removes deposit volume — some fraction of those repeat presses were producing transactions that stuck. The trial did not report net deposit value by arm, which is the single most conspicuous gap in the data. Without it, operators cannot calculate whether the friction pays for itself, and the 2.1-point abandonment increase sits unquantified against an unknown reduction in duplicate funding.

The more likely outcome is selective deployment. Given that the effect is concentrated in slow-rail, mid-value deposits, an operator could apply hold-to-confirm conditionally — only when the provider response exceeds a threshold, or only above a deposit value — and capture most of the benefit at a fraction of the abandonment cost. That is a reasonable engineering response, and it is also the point at which the intervention stops being a uniform safeguard and becomes a targeted one, applied to the players and payment methods an operator's risk model flags.

Which raises the question the trial leaves open. If the hold's effect depends on the ambiguity window, and the ambiguity window is a function of payment provider latency, then the intervention is really a patch for a problem that providers could fix directly — by returning confirmation faster, or by pushing a pending state to the client immediately. A cashier that never leaves the player uncertain would not need a five-second hold at all. The 38% figure is a measure of how much uncertainty the current payment stack generates, and of how cheaply it can be absorbed. Whether it should be absorbed by the player's finger or by the provider's infrastructure is a design choice the industry has not yet made.