Definition
Know your customer: the identity checks regulated operators must run. A major drop-off point in every registration funnel.
KYC is the set of checks that establish who a customer is, that they are old enough, that they are not on a sanctions or self-exclusion register, and — where thresholds are crossed — where their money came from. It is a legal obligation under anti-money-laundering and licensing rules, not a product decision.
How it works
The usual sequence is an identity document, a proof of address, and a check against registers. Much of it runs automatically; the cases that fall out go to manual review, where the wait is measured in hours or days rather than seconds.
When it happens varies by jurisdiction. Some regimes require verification before a deposit, others allow play up to a threshold first. That timing decides where the drop-off sits, and it is the single biggest structural difference between funnels in different markets.
The failure modes are mundane and account for most of the loss: a photo with a glare, a utility bill older than the permitted window, a name that does not match because of a marriage or a transliteration, a document type the processor does not accept from that country.
Why it matters in iGaming
It is usually the largest single leak in the funnel, and the one that cannot be removed. Players arrive expecting to play and are asked for a passport, often at the moment their intent is highest.
It is also where acquisition economics are decided. A player who abandons at verification has cost the full acquisition spend and returned nothing, and under most affiliate deals the referral never qualifies either. The step is simultaneously compulsory, expensive to fail, and almost always treated as an afterthought in the interface.
Example
An operator asks for documents after the first deposit and loses 38% of players there. Moving the request to before the deposit, with a plain explanation that it is a licensing requirement and a preview showing whether the photo is readable before it is submitted, cuts the loss to 21%. Nothing about the requirement changed.
Common mistakes
- Treating it as a legal matter rather than a product one. The requirement is fixed; how it is explained, timed and recovered from is entirely a design decision.
- Rejecting without saying why. “Document not accepted” sends the player to support or away; naming the actual problem lets them fix it in a minute.
- Losing the session. A person who leaves to find a passport should return to where they stopped, not to an empty form.