For Developers · Dashboard

Anti-Bypass

Panda Anti-Bypass is our native, self-hosted defense against ad-link bypassers — no third-party middleman, no injected ads. It shows a short verification page before your ad, detects skipped ads and bypass tools, and can log the attempts and/or block them. It runs on top of Deep-BYPASS, so you can use both together.

How it works

When a user reaches a checkpoint, Panda sends them to a lightweight verification page (hosted by us — styled to your service) with a short timer, then on to your ad. The link the user completes points back to a Panda endpoint that verifies the completion server-side, using multiple independent checks that a real completion satisfies on its own. From those it produces a verdict and, depending on your settings, logs it and/or withholds the key.

Panda checks the result — whether the ad was genuinely completed — rather than fingerprinting individual tools. That means it keeps working against new bypass services without needing an update for each one.

The three controls

Enable — the master switch for this service. Off means the normal getkey flow, with no verification page.
Logging — record every verdict and fire your webhook. Observe-only; it never blocks. Leave this on for a while first to see your real traffic before enabling blocking.
Blocking — deny the key when a bypass is detected. The user sees a Blocked page instead of their key. Turn this on only after your logs look clean, so you don't block real users.

If both Logging and Blocking are off, anti-bypass turns itself off (back to normal) — there's nothing to do with a verdict, so the page is skipped.

Verification timer

The timer (default 10 seconds, adjustable 5–60s) is how long the user waits on the verification page before continuing to your ad. Keep it short for a good user experience — verification does not depend on the user waiting longer.

Your Discord webhook

Set a Discord webhook on the Anti-Bypass page and every verdict (or every blocked attempt) posts to your channel. This is separate from the platform-wide webhook the Panda team configures — if both are set, both receive the log.

Working alongside Deep-BYPASS

Panda Anti-Bypass runs on top of Deep-BYPASS. When both are enabled and the revenue mode is Deep-BYPASS-compatible, the ad the user is sent to (after the Panda page) is the Deep-BYPASS-protected link. If Deep-BYPASS is unavailable or errors, Panda falls back to its own protection so the flow never breaks.

Configure both on the same Anti-Bypass page in your service settings — Panda on top, Deep-BYPASS below.

Reading the logs

Beyond the webhook, verdicts are stored and shown in the dashboard. Each record includes the score, the signals that fired, the action (allow / challenge / block), and the country · browser · device segment, so you can spot false positives per segment before turning on blocking.

Defaults

Anti-Bypass: off per service (you opt in).
Logging: on once enabled.
Blocking: off — enable deliberately after reviewing logs.