Recent GAMSTOP exclusions must be blocked at next session

Requirement

Players newly added to the GAMSTOP register must be blocked at their next session start. The block must occur regardless of which brand or platform within the licensee group they attempt to access.

Remediation guidance

Confirm the operator's PAM (EveryMatrix / SoftSwiss / OpenBet / Playtech) consumes the GAMSTOP webhook + applies a hard block on player_id match. Use the affected_records list to confirm each was blocked.

Evidence specification

{
  "query": "recent_exclusions",
  "required_fields": [
    "gamstop_id",
    "added_at",
    "reason_code",
    "exclusion_period"
  ]
}

Recent evaluations (Apollo Gaming Ltd.)