Pay by mobile casino deposits are supposed to be frictionless. Tap, confirm, play. In practice, though, a surprising number of players hit a wall between tapping “deposit” and seeing their balance update. Whether it’s a cryptic “Error 4,” a silent timeout that charges nothing but resolves nothing, or an SMS confirmation that never arrives, these failures are frustrating precisely because they offer so little feedback.
This pay by mobile troubleshooting guide breaks down every common failure type, explains what is actually happening behind the scenes, and gives you specific steps to fix it. We cover the major UK payment rails including Boku, Fonix, Siru, and PayviaPhone, and flag where the problem often originates — the carrier, the provider, your browser, or the casino itself.
How Pay by Mobile Actually Works
Before troubleshooting anything, it helps to understand the process you are troubleshooting. Pay by mobile routes your deposit through your mobile carrier, not through a bank. The casino connects to a billing provider (Boku, Fonix, etc.), which sends a charge request to your network. Your network approves or rejects the request based on your airtime credit, your monthly spend cap, and whether premium billing is enabled on your account.
You then receive an SMS or call to confirm. Once you confirm, the provider notifies the casino, and your balance is credited. The entire chain involves four parties: the casino, the billing provider, your carrier, and you.
When something breaks, it usually breaks at one of three points: the carrier rejects the charge before you even see a confirmation prompt; the confirmation message never reaches you; or confirmation is sent but the casino platform fails to receive the signal. Each of these has a different fix.
The 60-Second First-Response Checklist
When a deposit fails, run through this list before anything else. Most issues resolve at step one or two.
- Turn off Wi-Fi. Pay by mobile relies on header enrichment to detect your phone number from your mobile data connection. Wi-Fi routes through a broadband IP address and strips that identification entirely.
- Check your balance or spend cap. The charge needs to clear the full deposit amount plus any carrier fee. Even being a few pence short causes a decline.
- Look in your SMS inbox. Many apparent failures are just unconfirmed PINs or unanswered “Y” prompts sitting unread. The confirmation window is usually around ten minutes.
- Check whether premium billing is barred. New SIM cards and some contract upgrades come with premium services blocked by default. You can unbar on EE by texting to 150, O2 to 2020, Vodafone to 97613, and Three to 83030.
- Try a smaller amount. Attempting £5 when £10 failed tells you immediately whether it is a cap problem or a rail problem.
Understanding Pay by Mobile Error Codes
| Error Code / Message | What It Means | How to Fix It |
| Error 4 — “Insufficient balance” | Airtime credit or spend cap is below the deposit amount | Top up your PAYG balance or raise the spend cap via your carrier app |
| Error 23 — “Premium service barred” | Your SIM blocks Payforit charges; common on new contracts | Text UNBAR to your network shortcode or call customer care |
| “Payment time-out” | The SMS confirmation window expired before you responded | Restart the deposit and reply promptly; do not switch browser tabs |
| “Token mismatch / Invalid session” | You navigated away from the payment page before confirming | Keep the payment tab open; clear cookies and retry |
| Error 32 (Boku) — “MSISDN blocked” | The number has a chargeback history and is flagged by Boku | Contact Boku support directly to request an unblock |
| Error 9001 (Fonix) — “Carrier rejection” | Spend cap or premium bar is active at carrier level | Lift the cap or bar through your carrier account settings |
| Error 402 (Siru) — “Too many transactions” | Siru’s hourly micro-limit (around £15 in the UK) has been reached | Wait approximately 60 minutes before trying again |
| Error 604 (PayviaPhone) — “Invalid shortcode” | Your handset SMS centre settings are outdated | Reboot the phone or manually resend the SMS to shortcode 84988 |
Why Your SMS Confirmation Never Arrived
This is one of the more disorienting failures because the deposit page seems to be working, you are just waiting for a message that never comes.
The most common reason is that premium SMS is restricted at the device or carrier level. Some Android models come with premium SMS filters turned on; check your messaging app settings and look for anything labelled “special message settings” or “premium SMS.” iOS handles this differently — if you are on iPhone, the block is almost always at the carrier level rather than the handset.
A less obvious cause is Wi-Fi Calling. When this feature is active, some carriers route SMS delivery through the internet rather than the cellular network, and header enrichment falls apart. Disabling Wi-Fi Calling in your phone settings and then retrying the deposit resolves this in a fair number of cases.
If you are using Boku specifically, there is a manual fallback: text “START” to the Boku shortcode 65065. This can kick a stalled session back into life.
Network-Specific Spend Cap Troubleshooting
UK carriers handle spend caps differently, and the default limits catch a lot of players off guard.
EE
EE applies a default monthly cap on premium services that sits below most players’ expectations. You can check and raise it through the My EE app under “Account” and then “Add-ons.” If you prefer not to use the app, calling 150 from your EE number connects you to billing.
O2
O2 lets you manage premium service settings through the My O2 app. Navigate to “Plan” and look for “Charges” or “Premium services.” Texting SPEND to 2020 gives you your current usage status, which is useful for diagnosing cap-related failures without logging into the app.
Vodafone
Vodafone defaults to a fairly low monthly premium services allowance on new contracts. The quickest route to changing it is through the My Vodafone app. Alternatively, texting INFO to 97613 gives you an instant read of your current premium billing status.
Three
Three has had a slightly chequered history with third-party billing services, and some account types have premium billing blocked outright rather than capped. If UNBAR (sent to 83030) does not work, you may need to speak to Three customer support directly, as some account types require agent-side changes.
Provider-Specific Fixes
Boku
Boku handles the largest share of pay by mobile casino transactions in the UK, so it generates the most support questions.
Error 4 is responsible for the overwhelming majority of Boku failures. Before anything else, confirm your airtime balance is above the deposit amount plus a small buffer for the billing fee.
If you are not receiving Boku SMS messages, the fix is usually one of two things: disable Wi-Fi Calling, or text “START” to 65065. If an ad-blocker is running, whitelist the casino domain — some aggressive blockers interfere with the payment redirect page.
Error 32 (MSISDN blocked) means Boku has flagged your number, usually because of a disputed charge in the past. This requires contacting Boku support rather than your carrier; the casino cannot resolve it on your behalf.
Fonix
Fonix error 9001 is a carrier-side rejection, usually triggered by a spend cap or a premium billing bar. The casino’s payment button may still appear to work normally right up until the point Fonix receives a rejection signal from your carrier, so it can look like the casino is the problem when it is not.
If the payment page goes blank or shows a white screen after you enter your number, an ad-blocker is almost certainly the culprit. Fonix’s redirect flow is particularly sensitive to content-blocking scripts.
Siru Mobile
Siru uses a voice call confirmation instead of SMS, which catches some users off guard. The call comes from an automated system and asks you to press a number to confirm. If your phone does not show the caller ID, or if you dismiss the call, the transaction fails silently.
Siru also enforces a relatively tight hourly transaction limit. If you see Error 402, there is no workaround other than waiting — attempting the deposit repeatedly will not bypass it and may complicate the resolution.
PayviaPhone
The PIN loop issue on PayviaPhone, where the page keeps asking for a PIN after you have already entered one, is almost always a browser caching problem. Opening the deposit flow in a private/incognito window resolves it immediately in most cases.
Error 604 is a handset-side issue. A device reboot refreshes the SMS centre settings, and if that does not work, sending the confirmation SMS manually to shortcode 84988 usually completes the transaction.
Deposit Was Charged But Casino Credit Never Appeared
The charge shows on your phone bill but the casino balance has not moved. Most of the time, this is a processing delay — the signal travelling from carrier to billing provider to casino can take up to 15 or 20 minutes under congested conditions.
Wait 30 minutes. If nothing changes, contact the casino’s live chat with the deposit amount, transaction time, and phone number you used. If they confirm no notification was received, call your carrier’s premium billing team with the same details so they can trace the charge reference.
Act fast. Billing disputes have a narrow resolution window, and the sooner both parties have the reference data in hand, the better.
What to Do When Nothing Works
Some failure scenarios do not respond to the standard fixes.
Three consecutive declines with correct balance and no restrictions: At this point the issue is likely at provider level rather than carrier level. Contact the casino’s live chat and ask for a payment reference ID. Then raise a support ticket with the relevant provider (Boku, Fonix, etc.) quoting that ID.
Charge on the bill but no casino credit after 48 hours: Escalate to your mobile operator’s premium services team. They can initiate a formal trace on the transaction. If this does not resolve within five working days, contact the Phone-paid Services Authority (PSA), which has jurisdiction over mobile billing complaints in the UK.
Persistent blocks despite UNBAR: Some carriers require agent-side changes for accounts where premium billing was disabled as a condition of a deal or contract. Only a call to customer services resolves this.
Common Pay by Mobile Problems at a Glance
Here is a quick reference summary for the most frequent issues:
- Deposit declined — Check airtime balance and monthly spend cap before retrying. A £5 test deposit helps confirm whether the cap is the issue.
- No SMS received — Disable Wi-Fi Calling, check premium SMS settings on your handset, and try the Boku START shortcode if applicable.
- White screen on payment page — Disable ad-blockers or whitelist the casino domain; reload in incognito mode.
- PIN loop or token mismatch — Clear browser cookies and cache; retry in a private window.
- Charged but no credit — Contact casino live chat within 30 minutes; escalate to the carrier’s premium billing team if unresolved.
- Error 402 / Too many transactions — This is a Siru-specific hourly cap; wait 60 minutes before retrying.
FAQ
Does switching on airplane mode and back help with SMS issues?
Yes, it often does. Toggling airplane mode forces your SIM to re-register with the cell tower, which can trigger delivery of queued messages that got stuck in transit. It takes about 30 seconds and is worth trying before anything more complicated.
Can a VPN cause pay by mobile deposits to fail?
Yes. VPNs mask your IP address and can strip the header enrichment data that billing providers use to identify your phone number. Disable any active VPN before attempting a deposit via mobile billing.
Is Error 23 permanent?
No. Once you lift the premium services bar through your carrier app or customer support, deposits through pay by mobile should resume immediately. The fix is reversible and does not affect your wider account.
Why does a £5 deposit work but a £10 deposit fail?
Your remaining daily or monthly cap is below £10. Caps are calculated on the gross amount, which includes any carrier billing fee on top of the deposit amount. A successful £5 deposit tells you the rail is working fine — only the cap needs raising.
Will a failed deposit appear on my phone bill?
No. Carriers only bill transactions they approve. A decline is rejected before it ever reaches the billing stage, so nothing appears on your statement. The only exception is if you see a charge without receiving credit — that means the carrier approved the transaction but the credit chain broke downstream.
What if the casino says they received the deposit but it is not in my account?
This can indicate a KYC hold, a bonus restriction, or a technical issue on the casino’s platform rather than a billing failure. Ask the casino support team specifically whether the deposit shows as “received and processed” or just “received.” The distinction matters for where the fault lies.
Who has ultimate authority over billing disputes?
In the UK, the Phone-paid Services Authority (PSA) regulates all premium-rate mobile services. If both the casino and your mobile operator fail to resolve a billing dispute, the PSA is the appropriate escalation body. The Communications Ombudsman handles broader carrier complaints if the issue relates to your network’s handling of the transaction rather than the casino itself.