If you’ve ever opened an account with an Australian-licensed bookmaker to bet on anything from a CS2 Major to the local footy, the accuracy of the personal details sitting on file with that operator isn’t some background admin task – it’s the entire foundation of the self-exclusion system meant to protect you. Palmer Bookmaking Pty Ltd, trading as Palmerbet, has just found that out the hard way, entering an 18-month court-enforceable undertaking with the Australian Communications and Media Authority (ACMA) after a customer who registered with BetStop, the National Self-Exclusion Register, on 2 September 2023 kept betting with the operator for nearly 18 more months.
BetStop doesn’t care what you’re betting on. It covers every licensed interactive wagering account in Australia, whether the customer is chasing esports outrights, racing multis or AFL lines, which means the same identity-matching plumbing that failed this Palmerbet customer sits under any esports market the operator books. A mismatch in a name field is a mismatch regardless of which odds board it shows up on.
What makes this case sting is that Palmerbet isn’t accused of ignoring the register. It’s accused of feeding it garbage. ACMA’s investigation found the operator repeatedly submitted the customer’s details using a shortened first name and an incorrect date of birth, details that returned negative matches against BetStop’s database and let the account stay open and active.
How a Shortened Name Turned Into 553 Contraventions
The timeline is the whole story here. The customer registered with BetStop on 2 September 2023, and Palmerbet first flagged them to the database four days later, on 6 September, but with the flawed personal information already baked in. Operators are legally required to close accounts held by registered individuals “as soon as practicable,” yet Palmerbet accepted bets from this customer on 18 separate occasions between December 2024 and February 2025.
ACMA counted 18 contraventions of section 61KA(3) of the Interactive Gambling Act – one for every day wagering services were provided to a self-excluded individual – plus 535 separate contraventions of section 61MB(5) for failing to close the account, counted day by day past the point it should have shut. The account only closed on 22 February 2025, the day the register finally returned a positive match. ACMA estimated that with accurate data from the start, closure could have happened within 24 hours of that first September 2023 check, a gap that turns a data-entry error into a customer-data controls problem worth 553 individual breaches.
Procedures Existed. They Just Didn’t Reach Everyone
Palmerbet isn’t a bookmaker that never bothered updating its systems. The operator had actually tightened onboarding in mid-2023, adding proper date-of-birth verification for new sign-ups. The problem was legacy accounts, older records like this customer’s that never got run back through the new checks, sitting there with unverified or simply wrong identity data until a positive BetStop match forced the issue.
ACMA concluded Palmerbet failed to take “reasonable precautions and exercise due diligence” in verifying and handling that identity data, which is a polite regulatory way of saying the fix never got applied where it mattered most.
Palmerbet Isn’t Alone on This List
Earlier this month, wagering operator Dabble Sports was also hit with penalties over repeated BetStop failures, and ACMA’s public investigations record lists several other 2026 outcomes touching operators including Entain, Chasebet and BetPlay for various BetStop-related contraventions. None of that means the register itself is broken; it means the enforcement spotlight on self-exclusion compliance across Australian-licensed wagering, esports betting markets included, is only getting brighter.
Carolyn Lidgerwood, an ACMA member, framed the stakes plainly around why these cases keep getting pursued: providers must respect that decision and must have robust systems in place, she said of operators’ obligations once a customer chooses to self-exclude.
The Verdict
Palmerbet is now expected to run an independent review of its BetStop compliance systems and refund every deposit the self-excluded customer made between September 2023 and February 2025. That’s the correct remedy, but it doesn’t undo the core lesson: a national self-exclusion register is only as good as the name and birthdate an operator types into it. Get that wrong on a single legacy account and you don’t get one breach, you get hundreds, and every bet placed under a false negative counts against you.
