For remote wagering conducted across the internet, a location detection service reasonably detects and dynamically monitors the player's location and blocks unauthorised wagers: a location check passes before the first wager after login on a device and again before wagers once 30 minutes (or a regulator-set period) have elapsed since the last check; a failed or out-of-boundary check rejects the wager and notifies the player, and every violation is logged with time, player ID and detected location; the geolocation method returns a location with a confidence radius lying entirely inside the permitted boundary; accurate sources such as Wi-Fi, GSM and GPS are used, and where a device offers only an IP address the location of a mobile device that is registered to that account may support it if the two devices are near one another, carrier data being permitted by the regulator when nothing else is available; the method controls whether the accuracy radius may overlap buffer zones or the boundary; and boundary polygons from audited maps approved by the regulator are used with location data overlaid.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.