What is Bespot Gatekeeper?

Bespot Gatekeeper is a highly customizable fraud prevention and geolocation verification platform for mobile and web applications. It verifies user locations, detects device integrity issues, and monitors network connections to help organizations—particularly in the iGaming, Media Streaming, and Financial Services industries—comply with regulations and protect digital transactions from fraud.

Using Gatekeeper

Use Gatekeeper to confidently secure your applications against location spoofing, device manipulation, and suspicious network usage. Our introductory guides provide a clear overview of Gatekeeper’s ecosystem, including step-by-step instructions for configuring your fraud strategy through policies and rules, integrating the SDKs, and reviewing real-time transaction data in the Bespot Dashboard.

You’ll also learn how to tailor geofences, apply device checks, and define network integrity requirements—all without adding complexity to your existing workflows. By following these guides, you can quickly implement location-based compliance, minimize fraud risk, and focus on delivering a seamless user experience. Gatekeeper does the heavy lifting behind the scenes, so you can get back to building and growing your business with peace of mind.

Key Concepts

Policies

A policy defines an overarching fraud prevention or compliance strategy. For instance, you might create a policy that focuses on detecting suspicious user geolocation or device tampering. Each policy determines how Gatekeeper evaluates risk and ultimately returns an Action (e.g., Block, Monitor, etc.).

Rules

Within each policy, you combine one or more rules. A rule is a logical expression—such as “If the user appears outside an approved geofence AND a mock location is detected”—that, when true, indicates heightened risk.

Checks

Checks are the building blocks behind your rules. Each check represents a distinct signal or condition—like “mock location flag,” “network interface name,” or “root/jailbreak detection.” You can chain multiple checks together (using AND/OR logic) to form a single rule. When a rule’s required checks are evaluated to be true, the parent policy is triggered.

Policy Actions

After a policy’s rules (and their underlying checks) are evaluated, Gatekeeper issues a Policy Action that your application can enforce in real-time. There are four primary policy outcomes:

  • Safe The user proceeds normally, with no restrictions.

  • Monitor The user is allowed to continue, but the session is flagged for additional observation or logging.

  • Limit Access Access to specific features (e.g., certain transactions) is restricted due to a significant risk detected.

  • Block The highest-risk scenario, in which the user is denied access altogether.

Table of contents