A rejected bonus code is one of the most frustrating things that can happen at a cashier screen. You have typed the BetAhoy promo code exactly as advertised, hit confirm, and the box flashes red. Maybe it says the code is invalid, maybe it says it has already been used, or maybe nothing happens at all and the 100 free spins simply never land in your account. The money is gone from your balance, the offer is missing, and when you open live chat the first thing you are asked is whether you entered the code correctly.<\/p>\n
That question is where most complaints live or die. If you cannot show that BASS100 went into the field in the right case, in the right box, at the right time, support will log the issue as user error and close the ticket. If you can show it, the burden shifts to the operator to explain why its own system rejected a valid code. The difference between those two outcomes is rarely the strength of your argument. It is almost always the quality of your screenshots.<\/p>\n
This guide walks through the evidence you need to build before you escalate anything, from the moment the code entry screen throws an error to the point where an alternative dispute resolution provider reads your file. It covers what to capture and when, how to document a missing free spins balance against the operator’s own ledger, and how to assemble the whole thing into a pack that stands up to scrutiny. BetAhoy is operated by Bet Ahoy Ltd under UK Gambling Commission licence 100094, which means a formal complaints route and access to ADR exist whether the support agent on shift mentions them or not. Knowing what that route expects from you is half the battle. The other half is a folder of clean, timestamped images taken before you touched anything else. Start there, and the rest of the process gets a lot simpler.<\/p>\n
Promo codes fail in a handful of predictable ways, and the reason yours failed matters more than most players realise. When you contact support about a BetAhoy promo code that did not work, the first question is always the same: was the code wrong, or was the system wrong? If you mistyped BASS100, that is on you. If you entered it correctly and the BetAhoy casino still refused it, that is an operator-side rejection, and that is the version of events a complaint can actually win on.<\/p>\n
Most rejected codes fall into one of four buckets. The first is a genuine typo: BASS100 entered as BASS1OO (letter O for zero), BASS 100 with a stray space, or bass100 in lowercase on a form that is case-sensitive. The second is a timing problem. The welcome offer that unlocks 100 free spins on Big Bass Splash requires a \u00a310 qualifying stake, and if the deposit settles after the code field closes, the code is rejected even though you typed it perfectly.<\/p>\n
The third is an eligibility clash. A no-deposit bonus code may be blocked because you already claimed a welcome offer, because your payment method is excluded, or because the code is tied to a specific game and Big Bass Splash was not the selected slot. The fourth is a straight system fault: the code field accepts the text, the page reloads, and the bonus ledger shows nothing. Buckets one and two are usually player-side. Buckets three and four are where Bet Ahoy Ltd, which holds UKGC licence 100094, has some explaining to do.<\/p>\n
That distinction decides outcomes. A complaint that says „the code did not work” gets a scripted reply about checking your spelling. A complaint that says „BASS100 was entered at 14:32 on 12 June, the screen showed this exact error, and the terms do not list my payment method as excluded” forces the operator to answer the actual point. The UK Gambling Commission does not adjudicate individual bonus disputes, so your case goes to the operator first and then to an ADR provider. Both stages work from documents, not recollections.<\/p>\n
| Failure mode<\/th>\n | Who is at fault<\/th>\n | Evidence that settles it<\/th>\n | Likely outcome of a complaint<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|---|
| Typo or wrong case in the code field<\/td>\n | Player<\/td>\n | Screenshot showing the mistyped text<\/td>\n | Rejected, goodwill gesture at most<\/td>\n<\/tr>\n |
| Code entered after the qualifying stake window closed<\/td>\n | Usually player<\/td>\n | Timestamps on deposit and code entry<\/td>\n | Rejected unless terms were ambiguous<\/td>\n<\/tr>\n |
| Excluded payment method or duplicate claim<\/td>\n | Player, if terms were clear<\/td>\n | Terms and conditions clause plus deposit record<\/td>\n | Rejected if the exclusion was visible before deposit<\/td>\n<\/tr>\n |
| Code accepted, no bonus credited<\/td>\n | Operator<\/td>\n | Timestamped confirmation screen and bonus ledger<\/td>\n | Frequently upheld, spins or cash equivalent credited<\/td>\n<\/tr>\n |
| Code rejected with no stated reason<\/td>\n | Operator<\/td>\n | Error message screenshot and support transcript<\/td>\n | Often upheld at ADR stage<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n One more wrinkle. BetAhoy launched in May 2026, so its platform is young and its code-redemption flow has had little time to bed in. The casino runs on EveryMatrix, the sportsbook on FSB Technology, and promo codes often sit across both systems. A code that validates on the casino side but not the wallet side produces exactly the silent failure that generates complaints. If that happened to you, the screenshots you take in the next five minutes are worth more than anything you write afterwards.<\/p>\n What UKGC and ADR Expect From Your Evidence<\/h2>\n |