Geofencing
Geofencing is the technical enforcement of a geographic boundary — allowing or blocking play based on the player's verified physical location, using multiple signals rather than IP address alone.
What it means
Geofencing enforces a geographic boundary in software: the platform verifies where the player physically is and allows or blocks play accordingly. Serious implementations fuse multiple signals — IP address, Wi-Fi triangulation, GPS, cell-tower data, device integrity checks — because any single signal is spoofable. It's worth separating from geo-blocking, which is usually a crude IP-based deny list: geo-blocking keeps a region out, while geofencing proves a player is inside a permitted one. Regulated US markets demand the latter, typically through certified geolocation providers whose job is confirming presence to state-line precision.
Why it matters for operators
Location enforcement is a licence condition, not a UX feature. US states and Ontario require certified geolocation before a bet is accepted, precise enough to hold at state and provincial borders; European regimes require operators to confine service to their licensed territory. Weak geofencing is how an operator ends up demonstrably serving a market it isn't licensed for — and unlike most compliance failures, this one leaves a perfect audit trail of timestamped bets attached to locations.
The adversary keeps improving. VPNs are table stakes; residential proxies, GPS spoofing apps and rooted or emulated devices are the current front, which is why modern stacks pair location signals with device fingerprinting and integrity attestation, and why location gets rechecked during sessions rather than only at login. There's a tension to manage deliberately: checks aggressive enough to stop spoofers will sometimes fail honest players on flaky connections near a border, and how the product handles that failure — silent bet rejection versus a clear recheck prompt — shows up directly in support tickets and churn.
Example
A player sits near a state border and their location confidence drops mid-session. A compliant stack degrades gracefully: in-flight bets settle, new bets pause, and the player gets a recheck prompt with a clear explanation. A sloppy one either lets the next bet through — a reportable violation — or dumps the session with no explanation and creates a support escalation instead.