IntelSocial
Reddit on Bet365 XPoint: wrong-state detection (MD→NJ), endless Verify install loop
Source. Reddit + X/Twitter public posts. Monitoring initiated March 2026.
Bet365 / XPoint is generating strong negative signal. Users report:
- Wrong-state detection — Maryland users placed in New Jersey
- Endless XPoint Verify install loop on desktop
- Multiple posts explicitly contrasting the broken Bet365 experience with GeoComply-powered books that "work fine"
Users are naming the provider switch as the root cause. This is a clean attribution — the geo layer is being identified by the community itself, not just by us.
Contrast. GeoComply complaints in the same monitoring window are vague and operator-attributed. Negative posts on FanDuel / DraftKings / Hard Rock exist, but frustration is directed at the operator experience, not the geo layer. No posts characterise GeoComply as fundamentally broken.