Four records, one minute
Look at the bank or card record and the cashier record. Note where the journey stopped — amount, payment sheet, bank app, return, or balance. Note the app version and the system version. That is the whole diagnosis, and it takes about a minute.
The pair of records places you in one of the usual states: nothing happened, authorised and not settled, settled and not credited, duplicated, or complete. Where the journey stopped tells you which party to ask.
Everything that goes wrong after this point goes wrong because someone retried before collecting those four records. A retry during an unresolved authorisation is how duplicates are made, and on mobile the failure is usually in the return rather than in the payment.
Screenshot as you go. Mobile errors are replaced within seconds and the wording is sometimes the only clue about which stage failed.
| Bank record | Cashier record | What it means |
|---|---|---|
| Nothing | Nothing | Refused before any payment was made |
| Pending | Nothing | Authorised, not settled or not matched |
| Settled | Credited | Complete |
| Settled | Nothing | Paid and not applied — request a trace |
| Two entries | One credit | Duplicate — report both references |
| Pending then gone | Nothing | Authorisation expired, no money moved |
Mobile-specific causes
Four causes are specific to phones. The payment instrument is not enrolled on this device, so the sheet has nothing usable. The bank app is not installed or not signed in, so authentication stalls. Background restrictions interrupted the handoff. Or the network changed mid-journey and the return failed.
None of those is visible from inside the casino app, and all of them produce a generic cashier error. That is why the test order starts on the phone rather than with support.
Repeat the action in a mobile browser. If it works, the app build or its handoff was the problem. Switch network. If it works, the network was. Restart. If it works, a stale session was.
Causes that are not mobile at all
A bank gambling block refuses every method, on every device, by design. If nothing works anywhere, that is the first thing to check, and it is a consumer control rather than a fault.
Incomplete verification at the operator also blocks every method, and it presents as a payment failure rather than as a verification message. Checking the account’s verification status takes a moment and explains a surprising number of cases.
Deposit limits — the operator’s or your own — produce the same generic error. A limit you set is working correctly, and the cooling-off period on raising one is deliberate.
- Every method failing everywhere points at a bank block or verification.
- A limit you set produces a refusal that is working as intended.
- Enrolment, bank app, background restrictions and network are the mobile four.
- The browser test separates the app build from the account.
- Collect app and system versions before messaging support.
Asking for a trace properly
If money moved and nothing credited, send the amount, the currency, the exact time, the reference or transaction identifier, the method, and the device and app version. Ask one question: is there an unmatched incoming payment with this reference.
Do not send a bank statement unless asked, and if you do, keep the reference and date intact while redacting unrelated entries. Removing the reference is the most common way customers make their own trace impossible.
Never send card numbers, banking passwords or codes through an app chat. A trace needs an identifier, not access, and a phone makes it far too easy to paste the wrong thing.
If a duplicate was created
Report both references immediately and state which outcome you want: one payment credited and the other returned. Saying so prevents the account being topped up with money you did not intend to gamble.
Duplicates take longer to unwind than the original problem, because each reference is reconciled separately and one usually has to be returned through the payment chain.
The prevention is the same single rule: never retry while the outcome of the first attempt is unknown.
What to write to support
Four sentences. Where the journey stopped. What the bank record shows. What the cashier shows. The app and system versions, and the result of the browser test.
That message gets a specific answer because it has already excluded the variables support would otherwise ask about. It is also the message that makes a later complaint easy, because it is dated and factual.
- Note where the journey stopped and screenshot the error.
- Check the bank record and the cashier record together.
- Test the same action in a mobile browser, then on another network.
- Record the app and system versions.
- Request a trace with identifiers if money moved and nothing credited.
FAQ
Why is the error message so vague?
Because the failure can come from the operator, the payment sheet, the bank or the network, and the app receives a generic result. Where the journey stopped is the information the message lacks.
Should I retry the payment?
Not until you have checked the bank record. On mobile the failure is usually in the return rather than the payment, so a retry often creates a duplicate.
Nothing works on any method. What is that?
Usually a bank gambling block or incomplete verification at the operator. Both refuse everything and neither is a mobile problem.
Does the app version matter?
Yes. Many sudden cashier failures follow an app or system update, and the version pair is the most useful detail you can give support.
Can support see why the bank declined?
Often not in detail. If your bank saw the attempt, the reason sits with the bank; if it did not, the refusal happened at the operator.
Next pages
Sources
- Financial Conduct Authority: information for consumers, checked 18 November 2026.
- UK Gambling Commission: Licence Conditions and Codes of Practice, checked 18 November 2026.
- UK Gambling Commission: age and identity verification, checked 18 November 2026.



