Bingo apps and bingo mobile sites run on different plumbing, and the promo mechanics differ with them. A code you type into a cashier box behaves nothing like a banner you tap inside an app, even when both carry the same words. This article walks through a realistic support case involving BINGO100 to show why in-app promos are account-bound, why typing them elsewhere returns an invalid code error, and how to check your own account before you assume a bonus has failed.
The case: a BINGO100 banner tapped in-app and a code typed on the mobile site
A player installs a UK bingo app, registers, and sees a banner on the lobby screen advertising BINGO100. She taps it. The screen refreshes, a bonus lands in her balance, and she plays. No code was entered at any point. Days later, browsing the same operator’s mobile site on the same phone, she finds a terms page that mentions BINGO100 and assumes the bonus is a voucher she can claim again. She types BINGO100 into the promo box on the mobile site and gets an error along the lines of “invalid code”. She contacts support convinced the operator has broken a promise.
This is one of the most common promo-related tickets in UK bingo, and the resolution is almost always the same. The banner she tapped was a deep link into her account, not a code. The bonus was applied server-side to her player record at the moment of the tap. The promo box on the mobile site is a different mechanism entirely, checking a code against a voucher database, and BINGO100 was never a voucher. The word on the banner is a label for a campaign, not a string the cashier recognises.
The same confusion turns up in reverse. Players read about WELCOME2026, which is used as a promo code in bingo apps and on some operator sites at registration, and then assume every capitalised word they see is a code. Some are. Many are not. The difference is whether the string is checked at a cashier or whether the tap itself carries the entitlement.
Why the tap worked and the typed code did not
When you tap a banner inside a native app, the app already knows who you are. You are logged in, the device holds a session token, and the tap sends a request that says, in effect, apply campaign X to account Y. The operator’s system checks your eligibility once, applies the bonus, and writes it to your account history. Nothing needs typing because the app has already done the identification step for you.
A promo code box is a fallback for people the system cannot otherwise identify. It matches a string to a campaign and then checks the account. If BINGO100 exists only as an in-app campaign trigger, there is no string to match, so the box rejects it. That is not a bug. It is two different systems doing two different jobs, and the error message is technically accurate even if it reads like a slap.
There is a second layer. In-app promos are usually tied to the app install and the account, which means they are account-bound in a way codes are not. A code can sometimes be shared, passed to a friend, or posted on a forum. An in-app promo cannot, because it fires only from inside an authenticated session. Operators like this because it limits abuse. Players trip over it because the promo looks portable when it is not.
What account-bound actually means when you go looking for the bonus
Account-bound means the entitlement lives on your player record, not in a string you hold. If you want to know whether a promo has been applied, the answer is in your account, not in your memory of a banner. The bonus history, the transaction log, or the promotions section of your account will show the credit and the campaign name attached to it. That is the paper trail support will ask you to check first.
It also means the promo follows the account, not the device. If you install the same operator’s app on a second phone and log in, the promo does not re-apply. It was consumed on the first tap. Players who expect a fresh bonus on every install are usually disappointed, and the terms almost always say so in the small print. One account, one application, one bonus.
The practical consequence is that you should treat every in-app banner as a one-shot. Tap it once, then go and confirm the credit in your account before you play. If the balance has not moved, do not tap again in a loop. Check the promotions history, read the T&Cs attached to the campaign, and only then contact support with the campaign name and a timestamp. That sequence resolves most cases in a single message.
Where the same words appear as real codes
Some strings genuinely are codes, and it helps to know which is which. WELCOME2026 is used as a promo code in bingo apps and on operator sites at registration, so typing it into a cashier or a sign-up field is the correct move. GOLD50 and BINGO100 appear in some operators’ marketing as code-style labels, but whether they function as vouchers depends entirely on the operator and the campaign, and the label alone tells you nothing, as is also worth remembering when you compare https://bingodaily.uk/bingo-apps/ offers.
The reliable test is where you found it. If the string sits next to a box that says “enter code”, it is probably a code. If it sits on a banner you tap inside a logged-in app, it is probably a campaign label. If it appears in a review round-up of the best bingo apps UK, treat it as a description of an offer, not an instruction to type. Reviews summarise; they do not issue vouchers.
Operator differences matter here. 888 Ladies offers an iOS app, and its in-app promotions fire from the lobby. Betfred Bingo offers an iOS app with a similar tap-to-apply model. Betfair Bingo offers iOS and Android apps, so the same account can hold entitlements claimed on either platform. Barbados Bingo offers a mobile site rather than a native app, which means its promotions tend to run through account login on the web rather than an in-app tap. None of this is universal, but the pattern is consistent: native apps lean on taps, mobile sites lean on codes and logged-in claims.
How to check, claim and escalate without wasting a support ticket
Start with the account, not the code box. Log in, open the promotions or bonus history section, and look for the campaign name and the credit date. If it is there, the promo worked and the code box is irrelevant. If it is not there, note the exact campaign name from the banner, the time you tapped, and the device you used. That trio is what support needs to trace the request.
If you are on a mobile site rather than a native app, the mechanics shift. A mobile site cannot deep link into an installed app’s session, so promotions usually run through account login and a claim button in the promotions page, or through a code if the campaign is set up that way. Typing an in-app campaign label into that box will fail. Check the promotions page first and see whether the offer is listed as a claimable item on your account.
Native apps are installed from the App Store or Google Play, and that install path matters for promo eligibility. Some campaigns are restricted to app users, which is exactly why they are account-bound and tap-driven. If you claimed on the app and then want to use the same offer on the mobile site, you cannot. The entitlement is already on your account. What you can do is log in on the mobile site and play with the bonus balance, because the balance is account-level even when the promo trigger was app-level.
Before any of this, set your deposit limits in the player’s account. A deposit limit is a safer play tool that caps what you can put in, and it sits alongside the promo settings rather than replacing them. If a bonus tempts you to deposit more than you planned, the limit is the control that stops the spiral. BeGambleAware provides safer gambling support, GamCare runs a helpline, and GamStop supports self-exclusion if you need a hard break. These tools are free and independent of any operator.
Watch the practical costs too. Native apps take storage space, need app updates, and consume mobile data allowance when you play off Wi-Fi. A mobile site with a home screen bookmark avoids the install and the updates but loses the tap-to-apply convenience. Neither is better in the abstract. The trade-off is convenience against control, and the promo mechanics follow the platform you choose.
If you do end up raising a ticket, keep it factual. State the campaign name, the platform (native app or mobile site), the time of the tap, and whether the credit appears in your bonus history. Ask specifically whether the campaign is account-bound or code-based. Support can answer that in one line, and it saves the back-and-forth that comes from a player insisting a banner was a voucher. Most operators will also confirm in writing that the bonus has been applied, which is useful if the balance display lags.
One more habit worth building. When you see a promo in an app, screenshot it before you tap. The screenshot captures the campaign name, the terms link, and the date, which is more than enough for support to work from if the credit does not land. It also stops you confusing two campaigns later, which is how a lot of these tickets start in the first place.
Treat in-app banners as taps and cashier boxes as codes, and the confusion mostly disappears. Confirm the credit in your account history before you play, read the T&Cs attached to the specific campaign, and do not assume a label you saw in an app will work when typed into a mobile site. If a promo fails, report it once with the campaign name and a timestamp rather than retrying the code. Bingo Daily reviews the best bingo apps UK and flags which offers are tap-based and which are code-based, so check a round-up before you assume every capitalised word is a voucher. Set your deposit limit early, keep the safer play tools in view, and let the account history, not the banner, be your source of truth.