Solutions · Bonus-abuse defence
Don't pay bonuses to players who only deposited for the bonus.
Bonus-abuse hunters take a real slice of every operator's bonus budget. Canon detects the pattern at decision time and routes hunters to cooldown or no-action — not to a bigger nudge.
Today
Detection comes after the bonus is paid.
Most operators detect bonus abuse in finance reconciliation, weeks after the bonus has been paid out and withdrawn.
Block one device or IP, the hunter spins up another. Account-level blocking is a treadmill that never wins.
Aggressive abuse rules also block legitimate players with overlapping signal patterns — withdrawal-heavy, multi-account households, etc.
With Canon
Detection at decision time, not post-hoc.
Canon scores every player on a hunter likelihood derived from deposit, wagering, withdrawal, and time-of-day patterns.
Suspected hunters get cooldown or no-action decisions — never a bonus. The cost of a wrong call is zero spend, not a payout.
Confirmed hunters feed the model. Detection improves operator-by-operator as the signal pattern library grows.
Decisions are scored with confidence intervals; borderline players get held for review rather than blanket-blocked.
“The hunters were a known leak. We never expected to recover this much without false-positive complaints.”
Run hunter defence against your last quarter.
We can replay your historical event stream and report how many suspected-hunter bonuses Canon would have caught — no integration needed.