You enter a promo code, hit confirm, and the bonus never lands. Or worse, it lands but not the one you typed. Before you fire off an angry email, understand this: most “code error” complaints collapse because the player has no evidence of what they actually entered. The operator’s database says one thing, your memory says another, and the dispute goes nowhere. This guide walks you through proving a genuine bonus code error, the kind where the fault sits with the operator and not your typing, using the exact evidence trail that the UK Gambling Commission and alternative dispute resolution (ADR) providers expect to see.
Document the error before you touch anything else
The single most important move happens in the first sixty seconds after a code fails. Do not close the window, do not refresh, do not try the code again “just to check.” Capture a timestamped screenshot of the code entry screen exactly as it appears, showing the code you typed, the field state, and any on-screen confirmation or error message. Then open your bonus ledger or transaction history and screenshot that too, with the timestamp visible. This two-shot sequence is the difference between a complaint that gets upheld and one that gets closed with a template reply.
Why does this matter so much? UKGC-licensed operators and the ADR services that handle escalated disputes work on documented evidence. The regulator’s complaints framework expects the player to show that the code was entered correctly and that the error was operator-side. Without a screenshot of the entry screen, you cannot prove you typed BASS100 and not BASS1OO, and that single character difference is the operator’s favourite defence. A ledger screenshot proves the bonus did not credit, which closes the other half of the argument.
What a usable screenshot actually contains
A screenshot with no timestamp is close to worthless. On mobile, enable the device clock in your status bar before capturing, or use a screen recorder that stamps the footage. On desktop, capture the full browser window including the system clock, or better, use a tool that overlays the date and time. The screenshot needs to show the promo code field with your entry visible, the page URL, and the moment of failure. If the site shows an error banner, keep it in frame. If it silently fails, capture the ledger showing no bonus and the timestamp on the last transaction.
Store the files with names that encode the date and time, for example betahoy-code-entry-2026-06-14-1932.png. Keep the originals, not crops. If you later need to escalate to an ADR provider, they will want the unedited image file with its metadata intact, and a cropped or re-saved JPEG can be challenged. A short screen recording of the whole sequence, from entering the code to the ledger showing nothing, is even stronger and takes about twenty seconds to make.
Build the paper trail the operator and ADR will accept
Once the evidence is captured, the complaint itself needs structure. Start by checking the terms attached to the specific promotion. A BetAhoy promo code like BASS100 unlocks 100 free spins on Big Bass Splash, but the BetAhoy welcome offer requires a £10 qualifying stake, and if you staked £9.99 the code was never going to work. Read the eligibility conditions before you allege an error, because a valid code applied outside its conditions is not an operator fault, and claiming otherwise weakens your position.
If the conditions were met, move to the operator’s live chat and get a written record. Ask the agent to confirm, in the chat, that the code was entered, the time it was entered, and the outcome. Screenshot the chat transcript or request it by email. This creates a second independent record that the attempt happened, which matters because operators can and do point to “no record of the code being used” when the real issue is a backend failure. Keep the reference number the agent gives you.
Then submit a formal complaint through the operator’s own process and keep every reply. UKGC-licensed brands must give you a final response within eight weeks, and the ADR route only opens after that or after a deadlock letter. Your complaint should attach the timestamped screenshots, the chat reference, and a plain statement of what you entered, when, and what should have happened. Do not editorialise. State the facts and attach the evidence.
Where sister sites and platform quirks fit in
One wrinkle worth knowing: many brands share infrastructure, and a code that works on one site in a group can fail on a sister site because the promotion was configured for a different domain. If you suspect this, screenshot the promotion page showing the code advertised on the site you used, alongside the failed entry. That proves the code was offered where you tried it. BetAhoy runs its casino platform on EveryMatrix and its sportsbook on FSB Technology, so the failure could sit in the promotion engine rather than the front end, and the operator will know which. Your job is only to prove the attempt and the advertised offer, not to diagnose the stack.
Licensing detail helps here. BetAhoy is operated by Bet Ahoy Ltd, which holds UKGC licence 100094. That licence number is your anchor when escalating: quote it in your complaint and in any ADR submission, because it ties the dispute to a specific regulated entity and removes any argument about which company is responsible. If a code error involves a game from a named provider such as Pragmatic Play, Red Tiger, Hacksaw Gaming or Evolution, note the game title in your evidence, as bonus crediting can fail at the game level rather than the account level, and you can check the operator’s details at https://bet-ahoy.uk/ before you escalate.
Escalate in the right order and keep the evidence chain intact
Escalation follows a fixed ladder, and skipping rungs gets you bounced back. Step one is the operator’s customer support. Step two is the formal complaints team, with a written complaint and your evidence attached. Step three is the ADR provider named in the operator’s terms, which for most UKGC-licensed brands is an approved service such as eCOGRA or IBAS. Step four, only if the ADR process fails or the operator breaches the rules, is the UK Gambling Commission itself, which does not adjudicate individual disputes but does act on patterns of non-compliance.
At each rung, send the same evidence pack with a short covering note. Do not add new claims late in the process, and do not remove anything. If the operator’s final response contradicts your screenshots, point to the specific timestamp. ADR adjudicators respond well to a clean, chronological pack: entry screenshot, ledger screenshot, chat transcript, complaint and reply. They respond badly to screenshots with no timestamp, cropped images, and claims that shift between emails.
One more practical point. BetAhoy withdrawals require mandatory KYC checks, and a bonus dispute can run alongside an identity verification hold. Do not let the two get tangled. Complete your KYC promptly, keep that correspondence separate from the bonus complaint, and make sure your bonus evidence does not depend on account access you might lose during verification. If your account is restricted mid-dispute, screenshot the restriction notice with its timestamp and add it to the pack.
When the code was fine and the fault was elsewhere
Some failures look like code errors but are not. A no-deposit bonus code may fail because you already claimed it, because your account is flagged for a bonus abuse rule, or because a GAMSTOP self-exclusion on a linked account is blocking promotional credit. Check these before escalating, because an ADR adjudicator will find them and your complaint will fail. Deposit method can also matter: BetAhoy supports Visa and Trustly deposits, and some promotions exclude certain payment methods, so a code that “does not work” after a Trustly deposit may simply be ineligible under the terms.
If the promotion ran on a game from a specific provider, note whether the game loaded correctly at all. A Big Bass Splash free spins award, for example, needs the game to be available in your jurisdiction and your account to be eligible for Pragmatic Play titles. The Dog House Megaways 1000 and other Megaways releases can carry separate promotional rules. None of this excuses a genuine operator error, but ruling these out first makes your complaint much harder to dismiss.
Finally, if you see the same code failure reported by other players, gather their timestamps too, with their consent. A pattern of failures at the same time on the same code is powerful evidence that the fault was operator-side, and ADR providers take notice when multiple complainants present consistent, timestamped records. One player with a clean pack can win a dispute; five players with matching packs almost always do.
Proving a bonus code error comes down to discipline in the first minute. Screenshot the entry screen and the ledger with timestamps, save the originals, get the chat in writing, check the terms and eligibility rules, then climb the complaint ladder in order with the same evidence pack at every step. Quote the licence, keep your KYC separate, and let the timeline do the arguing. Do that and a genuine operator-side error is very hard to wave away.
