Skill Gaming Launch Footprint Scorecard

When both contestants fund the prize and the operator deducts a percentage of the pooled entries, several states read the operator's role as raking wagers, selling pools, or acting as a paid custodian of stakes, and those offenses do not care that the underlying game is pure skill. A separately stated, fixed, outcome-independent per-player fee, with the winner receiving 100 percent of the combined entries, is the structure that keeps the operator outside the bet.

The classic rule (Las Vegas Hacienda v. Gibson and its progeny) is that an entry fee paid unconditionally to an operator who does not compete for the prize is not a bet. But that doctrine has a catch founders almost never see: it works cleanly when the operator funds the purse. When two players fund the prize with their own equal stakes, some states recharacterize the match as wagering between the players, no matter how skillful the game. Whether a state has an express exception for prizes to the actual contestants (22 jurisdictions have some version of one on my current record) is often the whole ballgame.

The least intuitive result in this field: statutes that never mention the players can still criminalize the platform. Pool-selling and bookmaking definitions with no chance element, paid custodian-of-stakes provisions, and internet-gambling statutes that expressly cover games of skill can each reach the operator's business model directly. On my current record, materially adverse operator-side structures drive most of the 20 excluded jurisdictions, and 27 jurisdictions have some form of staking-on-skill-contest prohibition that must be analyzed against the contestants' own entry fees.

If player deposits settle into the operator's own account with an internal ledger, two independent problems appear: custodian-of-stakes offenses in the gambling codes, and state money-transmitter licensing for holding and transmitting third-party funds. Custody with a licensed provider or sponsor bank, with the platform transmitting only objectively determined result instructions, mitigates both and is what processor underwriting teams increasingly expect to see documented.

A footprint is only as good as its enforcement. Underwriting-grade programs use an affirmative server-side whitelist (everything blocked by default), a device-level geolocation check immediately before every paid contest for every participant, VPN and spoofing detection, and logging. A billing address or a checkbox is not geolocation. And one more trap: geoblocking customers does not solve the operator's own home-state exposure, which is a separate analysis.