Contact and account questions

Account and payment enquiries

Use the help section within the operator's recognised website or account. Keep the transaction reference, date, currency and disputed amount available. Do not disclose a password, PIN or one-time banking code to anyone claiming that those secrets are needed to investigate.

If ordinary support does not resolve the issue, our complaints guide explains how to organise a written chronology and identify the appropriate escalation route. It is guidance for preparing your own records, rather than a claims-submission service.

Start by identifying the kind of help required

“I do not understand this amount” can mean several things. You might be questioning a sentence in an article, an entry in a casino account or the effect gambling is having on your life. Each needs a different kind of help. Start with the page or record you are looking at and the part you need explained; that will help identify the organisation able to answer.

If the issue is a sentence on this website, describe the article and the statement. If it is a transaction in an account, use the organisation holding that account record. If it is the effect gambling is having on your life, independent support is a separate route. Resolving one of these tasks is not a prerequisite for beginning another.

This page helps prepare those distinctions. It is not an operated message form, a payment trace or a claims-submission service. No personal documents need to be sent to Cashier Trace in order to decide which type of question is being asked.

The publication does not have access to account controls

Cashier Trace cannot see a casino balance, authorise a withdrawal, check a wallet's private history or change a bank instruction. A screenshot-like illustration in an article does not establish account access. The publication's name beside a guide is an editorial identity, not authority over an operator's systems.

An account-specific request should therefore begin through the operator's or provider's recognised secure route. A general article can explain which reference might be relevant, but it cannot retrieve that reference from a private system. Sending more private material to an unrelated publication would not create the missing access.

The same boundary applies to the homepage's inactive listing and the Play navigation link. The listing has no connected offer destination, while Play opens the local game catalogue. Neither is an operator support desk. Their presence does not create a channel through which the publication can act on a reader's money or account.

Describe a publication correction without a financial dossier

A useful publication correction identifies the page title, the heading and the exact statement that appears wrong. Add the public source that seems to conflict with it and explain the scope of the difference. This is enough to define an editorial question without including account credentials.

For example, a reader might notice that a game note names the original release while a linked source now displays a sequel. The question concerns the match between the article and its source. It does not require a statement of how much the reader deposited or whether a particular round won.

Keep an interpretation separate from an observation. “The link now opens a different title” is a direct observation. “The entire article must be false” is a broader conclusion requiring more evidence. A narrowly described mismatch makes a correction easier to assess and avoids obscuring a useful point inside an unsupported accusation.

Direct a merchant-record question to the merchant

An operator can normally identify the instructions and account entries recorded in its own system. A payment provider or bank may hold a different part of the journey. Begin by identifying whether the question concerns an instruction that was requested, one that was approved, one that was dispatched or an entry later received elsewhere.

The phrase “withdrawal completed” needs its original context. It may be a status shown in one system, rather than a statement from the receiving bank. Preserve the actual wording and ask which event it represents. Do not rewrite a status into a stronger claim before contacting the next organisation.

The payment-stage index separates those journeys. Its purpose is to help define the next question, not to select an organisation at random. If there is no evidence that a payment left the merchant, a receiving provider may not yet have a corresponding record to investigate.

A wallet-to-bank enquiry begins at a later stage

Money already available in a wallet can be the starting point for a new bank-transfer instruction. That instruction is separate from any earlier merchant payment into the wallet. A query about the second stage should identify the wallet transfer, not rely only on a casino withdrawal reference from the first stage.

Keep the amount, currency, destination and status associated with that later instruction together. A wallet balance and a transfer amount are not interchangeable. If only part of the balance was selected, the difference may be deliberate rather than an unexplained loss. The records need to show what was actually instructed.

The dedicated PayPal bank-transfer note and Skrill bank-transfer note explain the distinction. Their provider-specific sources should be checked through the recognised service before private evidence is supplied. This publication cannot look up either transfer merely because it discusses the route.

A voucher enquiry needs the location of the remaining value

An unused voucher refund and a merchant payment dispute are different tasks. First establish whether the value remains on the voucher or whether a payment has already been made with it. The original purchase value alone does not settle that question.

If value remains unused, the provider's own refund information is relevant. If it was spent but a merchant credit is missing, the merchant payment record becomes important. Do not describe every movement involving a voucher as a casino withdrawal; the organisation able to answer may depend on which event actually occurred.

Our PaysafeCard refund explanation and Neosurf refund explanation keep those questions apart. A voucher code is sensitive value-bearing information. It should not be sent to a publication or to someone offering an unofficial balance check merely to begin a general discussion.

A game-rule question is different from a payment question

An apparent difference in a game total should first be described using the named release, the round and the rule being questioned. A bank receipt cannot establish how a game feature was calculated, just as a feature animation cannot establish that money reached a bank.

The game-note directory explains settlement terms such as returned stakes and repeated evaluations. The named-game catalogue identifies particular releases. These pages can help phrase the question, but an account-specific game-history enquiry still belongs with the organisation that holds the round record.

Do not invent a round identifier or substitute the identifier from another session. If a reference is unavailable, state that plainly and retain whatever original information is available. A precise description of the missing record is more useful than a confident but incorrect reference.

Identify the reference before copying it into a message

Several references can appear during one journey. A merchant request number, a wallet transaction identifier and a bank entry reference may all concern related money while identifying different events. Label the reference with the system that issued it.

Write a short label beside each reference: “merchant withdrawal request”, “wallet receipt” or “wallet-to-bank transfer”, for example. That tells the recipient where to look. A string of letters and numbers may be copied perfectly yet refer to a different stage from the one under discussion. The label matters as much as the accuracy of the characters, especially when an enquiry passes between organisations.

For a publication question, a public page address is generally more appropriate than a transaction identifier. Do not include account-specific addresses containing private session information when a plain article address will do. The information supplied should follow the purpose of the enquiry, rather than everything that happens to be available.

Prepare a short chronology with separate observations

A chronology need not reproduce every activity in an account. Begin with the event relevant to the issue and add the later observations that explain the question. Keep the date, amount, currency and displayed status attached to each line.

Here is a simple example of a chronology: a request is recorded on Monday, the merchant's status changes on Tuesday, and the receiving account is checked on Wednesday. These are three separate observations, each with its own date. If there is no dispatch record, leave that event unconfirmed. The sequence is still useful: it tells the recipient what is known and which link needs investigating.

Distinguish what was shown from what was inferred. “The bank history did not show a matching entry when checked” describes the observation. “The money was never sent” goes further. The recipient may be able to establish the missing link, but the initial message should not present that link as already known.

Ask a question the recipient can answer

A focused enquiry requests a particular explanation or record. It can ask which instruction a status refers to, whether a dispatch record exists or which rule produced a rejection. The question should correspond to information held by the recipient.

For example, asking an operator to identify the reference for a dispatched payment is different from asking a publication to make the payment arrive. The first requests a record from the organisation that may hold it. The second asks for an action outside the publication's role.

Avoid combining several unrelated disputes into one opening paragraph. If a missing award, a rejected withdrawal and a card entry are all involved, identify each event and explain any supported connection. A list of distinct questions is easier to follow than treating every account concern as one unexplained total.

Use a factual opening instead of an assumed cause

A useful opening states the event and the question before proposing a cause. “I requested a GBP withdrawal and cannot identify the matching receiving entry” is more precise than “your bank blocked my money” when the route is not yet known.

You can then identify the available record and ask what information is missing. If a provider has already supplied a reason, quote or accurately summarise that reason in its original context. Do not turn a generic help article into an account-specific explanation unless the provider has actually applied it to the event.

You can be firm and precise at the same time. “Please identify the dispatch reference for this request” tells the recipient what answer is needed. If the reply discusses only the general process, you can then point to that unanswered question. This gives a follow-up a clear purpose without relying on a guessed technical cause or an accusation against an organisation that may hold only part of the record.

Keep a full original and a proportionate shared copy

An original record can matter later, so keep it privately where appropriate. A copy prepared for a particular enquiry should include what that recipient legitimately needs and avoid unrelated private information. The same document need not be sent to every organisation mentioned in the story.

A public editorial question normally does not require a full bank statement. A provider investigation may ask for evidence through its own secure process. These are different purposes. Redacting an unrelated detail for a general explanation is not the same thing as changing an amount, date or event material to the question.

Before sharing a screenshot, inspect its edges, browser tabs and notification areas. A selected payment can be surrounded by other account information. Keep the original distinct from any edited copy so that privacy preparation does not accidentally become an alteration of the underlying record.

Handle a referral without losing the original question

One organisation may direct a reader to another because it holds only part of the journey. Before moving on, preserve the response and identify what it establishes. A referral is not automatically a finding that a payment succeeded, failed or belongs to someone else.

Ask which record should be quoted to the next recipient and what stage has actually been confirmed. If no confirmation is supplied, retain that gap. An enquiry can otherwise become a loop in which each new recipient is given a stronger version of the previous response than the response actually supported.

When returning to an earlier organisation, keep the chronology together. Explain what the later recipient could and could not identify. A concise account of that exchange is more useful than restarting with a new story or making another financial instruction in the hope of generating a clearer record.

Follow up with the unresolved point

A useful follow-up names the earlier enquiry and quotes the question that remains unanswered. For example: “Your reply explains the usual withdrawal process, but I still need the dispatch reference for request A.” Include the original enquiry date so the exchange can be found. You do not need to repeat every paragraph of the first message when a short reference and one clear question will carry the discussion forward.

Add genuinely new observations with their dates. Do not silently edit the original chronology so that it appears the new information was known from the start. Keeping the sequence honest helps distinguish a changing situation from a contradiction in the earlier record.

This publication does not promise a response time from an operator, bank or provider. The relevant service's own current information should be used for its process. A publication can explain how to state a follow-up clearly without inventing a deadline or claiming authority to expedite the case.

Treat an external destination as a separate service

Source and support links lead to organisations with their own processes. Check that the destination is the intended service before entering information. A link included as factual evidence is not an account-verification channel operated by Cashier Trace.

Be particularly careful with unsolicited requests for passwords, full card details, one-time codes or a payment supposedly needed to release funds. Those requests should not be accepted merely because a message repeats the name of an article or a familiar provider. Use the actual organisation's established route to check what is required.

An image of a phone or cashier in this publication is also not a live support interface. It cannot receive a message, inspect a code or confirm a transaction. The privacy information explains why illustrations and reading controls should remain separate from the handling of account evidence.

Report a usability problem as a usability problem

A broken internal link, unreadable table or missing image can be described without financial information. Identify the page, the control and what happened when it was used. If the issue depends on screen size, that detail can help explain it.

For example, “the Comparisons navigation opens the wrong article” describes a routing problem. “The paragraph is clipped on a narrow screen” describes a presentation problem. Neither requires a casino balance or identity document. A short description of the observable behaviour is enough to define the publication-level task.

Keep a content disagreement separate when both occur. A page can display correctly while containing a statement that needs correction, or contain accurate wording while a navigation control fails. Separating the two makes it possible to fix the actual problem rather than treating every difficulty as a dispute about the information itself.

A source disagreement needs the product and period

When a source appears to disagree with a page, identify whether both refer to the same product, release and period. A new game edition or a different payment product may explain why the figures cannot be combined. The difference still deserves attention, but its scope needs to be clear.

Give the public source address and the relevant wording rather than copying a large unrelated page. A correction request should make it possible to locate the disputed field. If only an excerpt is accessible, describe that limitation instead of presenting the entire source as inspected.

The editorial evidence policy explains how unsupported values, historical examples and hypothetical calculations are separated. An editorial response should address that evidence boundary. It cannot settle an individual account claim merely by changing an article's wording.

State what would count as an answer

An enquiry is easier to follow when it identifies the requested outcome. A publication correction might ask for a source to be replaced or a sentence to be narrowed. A payment enquiry might ask for the dispatch reference or the reason attached to a particular rejection. These are different outcomes, and neither should be hidden behind a general demand to “sort everything out”.

Keep an explanation request separate from a request to move money. An organisation may be able to explain a record without being the organisation able to change it. Conversely, a balance change without an explanation may leave the original question unresolved. Naming the requested outcome makes that distinction visible before the exchange begins.

If the evidence is incomplete, the requested outcome can be the missing record itself. There is no need to invent a cause simply to sound decisive. A clear question about one instruction, amount or statement gives the recipient something specific to address and gives the reader a way to recognise whether the response actually answers it.

Independent support is available for a different kind of need

If gambling is affecting everyday life, the Help page provides independent support information. A person does not need to complete a transaction investigation or assemble a perfect chronology before seeking that kind of help.

Support and account enquiries can coexist, but their purposes differ. An operator may investigate a transaction record; an independent support service can discuss the effects of gambling. Asking one organisation for help does not require treating it as responsible for every aspect of the situation.

This publication is not a counselling service and does not operate an emergency inbox. Its contact guidance should not delay seeking appropriate help elsewhere. The relevant next step is the organisation suited to the actual need, whether that need is an explanation of published wording, action on an account record or independent support.

Questions about this publication

The about page describes Cashier Trace's market and subject scope. Our editorial policy explains how sources, uncertain figures and hypothetical examples are handled. The privacy information sets out why private account records should not be sent to a general information publication.

No enquiry form is operated here. A link to a primary source takes you to a separate organisation with its own contact arrangements. Check that organisation's official information before supplying personal details.

Independent support

For gambling-related harm, use the independent resources on our support page. A payment dispute does not need to be resolved before you seek help with the effects of gambling.