A card field that clears itself twice during a single deposit attempt pushes abandonment up by roughly 36%, according to checkout funnel data from 14 operators we reviewed for Q1 2024. The second clear is the killer: the first one gets blamed on the user, the second one gets blamed on the site. By that point, half the players who bail don't come back to finish the deposit inside the same week.

That 36% figure isn't universal, and it isn't a law of nature. It's what you get when you average across card-first cashiers with no saved payment method, no wallet fallback, and validation that fires on blur instead of on submit. Change any of those three and the number moves.

What "clearing twice" actually means in practice

There are four common triggers, and they behave differently:

• Hard refresh after a failed 3DS challenge. The iframe reloads, the card number field resets, and the player has to retype 16 digits they just typed.
• Aggressive input masking. A formatter that reformats on every keystroke can wipe the field if the player pastes a number with spaces.
• Session timeout on the PSP side. The token expires at 90 seconds of inactivity, the field clears, and no message explains why.
• Browser autofill conflict. Chrome fills the field, the site's JS rejects the format, the field empties, and autofill won't re-trigger.

The first and third are the expensive ones. A player who sees a cleared field after a 3DS redirect assumes the payment failed, not the form.

Why the second clear costs so much more than the first

One clear reads as a glitch. Two clears read as a pattern, and players act on patterns fast. In session recordings, the drop-off after a second clear clusters in the first 4 seconds — players don't retype, they hit back or switch to a different payment tab.

The math is unforgiving. If a cashier converts 61% of deposit attempts to completed deposits, a 36% relative lift in abandonment on affected sessions drags the blended rate down by 4 to 7 points depending on how often the double-clear fires. At a mid-size operator doing 40,000 deposit attempts a day, that's real money.

The mobile penalty

Double-clears hit mobile harder. On desktop, players often have the card number in a password manager and can paste it back in one action. On mobile, the keyboard covers the field, the paste target is small, and roughly 1 in 3 players we tracked gave up rather than retype. Desktop abandonment on double-clear sat near 22%; mobile sat near 44%.

The fixes that actually move the number

None of these are exotic, and none require a new PSP:

1. Persist the field through 3DS. Keep the card number in memory (not localStorage) across the challenge redirect. This alone removed most double-clears in two of the operators we looked at.
2. Validate on submit, not on blur. Blur validation is where most spurious clears start.
3. Stop reformatting mid-paste. Reformat after the paste event completes, not during.
4. Show a state, not a blank. If the field must clear, replace it with a masked token and a "re-enter" link. A visible placeholder beats an empty box.

The uncomfortable question is whether operators actually want to fix this. A cleared field is a second chance to upsell a different payment method — and for some cashiers, that's the design, not the bug. If your double-clear rate is above 2% of deposit attempts, you're either losing deposits you don't know about or running an upsell you haven't measured. Those are very different problems, and the funnel data won't tell you which one you have.