Contact and corrections

For a payment or account problem

Use the operator's official support channel for its account record and the bank or wallet's genuine channel for its own transaction. The payment-problem guide helps identify which record is needed before you contact either organisation.

Do not post card numbers, identity documents, passwords or login codes here. A publication contact channel is not a secure operator-verification route, and sharing those details would not enable us to investigate your account.

For an editorial correction

There is currently no public editorial inbox or submission form for this publication, so this page cannot receive a message or report. The guidance below explains what a useful correction would contain. It does not submit those details to an editor or provide confirmation that a report has been delivered.

A useful correction would identify the article, the statement, its date and the primary source supporting the change. Account-specific allegations should be raised through the relevant organisation's complaint process instead of being treated as evidence about every customer.

For gambling support

Read safer-gambling help for independent support and self-exclusion for ways to reduce access. A missing-payment complaint can be preserved while you stop gambling; further play is not needed to keep the transaction record.

Our editorial policy explains the limits of the publication and its evidence. Cashier Fieldnotes does not accept deposits, process withdrawals or provide paid recovery services. Use an organisation's own verified contact details when it holds the money or record in question.

The privacy notice explains the limits of this editorial package and the details that must be documented when hosting is selected.

Choose the organisation that holds the relevant record

Start with the organisation holding the record you need explained. Your bank has its banking entry, a wallet has its history and an operator has its casino ledger. We explain how those records relate, but reading an article does not give us access to any of them.

If the problem concerns a specific account, use the genuine organisation's support route. Identify the transaction, status and date that you want explained. The publication can help you frame the question, but it cannot log in, authorise a trace or issue instructions to the provider.

A source link in an article is different from a private support destination. It may explain a published product rule without opening the secure account channel needed for your case. Do not assume that a public information page accepts the documents relevant to an account investigation.

The payment-problem guide separates the common stopping points. A declined request, a bank-side reservation and a completed-but-unreceived withdrawal do not necessarily belong with the same organisation. Start with the last action you can establish from the actual record.

For a publication issue, identify the article or control that appears wrong. A broken internal link, an incorrect heading and an inaccurate explanation need different checks from a payment enquiry. You can describe what the page says and supply a public source without providing a bank statement.

No enquiry can be submitted through this page because there is no configured publication form or inbox. The guidance below explains what an appropriate report would contain and where private account matters belong. It does not promise a response through a channel that does not exist.

Open a support route independently when a message is unexpected

An unexpected message may use the name of an organisation cited here. That alone does not verify the sender. Open the service through its known app or address before acting on the request; using the message's own link to confirm its identity would leave the original uncertainty unresolved.

Look for the relevant support option within the actual account or the organisation's official public information. A familiar display name, copied logo or reference to a transaction does not authorise a different address to receive identity records, payment details or login codes.

Pause if a message introduces a step unrelated to your original question. An unresolved withdrawal is not a reason to accept a request for a release charge, security code or remote-control software. We cannot verify the message; ask the genuine organisation through a channel you opened independently.

Ask whether the request is genuine through the organisation's independently opened channel. Describe what the sender asked you to do without forwarding an active login link or copying a security code. You can explain the concern while keeping the details that could grant account access private.

The verification guide explains why a genuine evidence request should have a clear purpose and submission route. It does not certify individual messages. That distinction matters because a general article cannot inspect the sender or the private account involved.

This publication does not sell access to operator support, offer payment recovery services or request a fee to release funds. A person making such a request in its name would not be describing a service supplied by this website.

Prepare a transaction question before opening a conversation

Before opening a support conversation, note the date, amount and currency, payment route, reference and exact displayed status. These details help identify the instruction. Keep what the records show separate from what you expected to happen, so the recipient can check the discrepancy without first unpicking your assumptions.

A clear opening message can state the two records that do not match. For example, a posted debit and an absent casino credit describe an identifiable discrepancy. Saying only that the account balance is wrong gives the reviewer less information about which event to locate.

If several attempts were made, number them and give each its own row in the chronology. A later successful request does not settle the status of an earlier one. Do not merge entries simply because the amounts are the same or the requests occurred close together.

Ask a question the recipient can answer from its own records. An operator can be asked whether it recognises an incoming payment. Once a sender supplies the relevant outgoing details, a receiving provider can be asked to trace that transfer. Neither enquiry needs to cover the whole account history at once.

Keep the support-case number separate from the transaction reference. One tracks a conversation or investigation; the other identifies the payment instruction. A reply containing a new case number is not, by itself, confirmation that the transfer has been located or completed.

The deposit-pending note and withdrawal-pending note provide more detail for their respective situations. Use the explanation that matches the actual state rather than copying a message intended for another kind of transaction.

Distinguish a bank enquiry from an operator enquiry

For the bank, identify the entry you can see: pending, posted or returned. Ask what that entry represents and what the bank needs to investigate it. The casino balance may explain your concern, but it does not tell the bank which of its own records to look for.

An operator enquiry should identify the relevant casino transaction or receiving instruction. If the operator says a withdrawal has been released, ask for the route and the reference appropriate to the payment. An internal approval label may not be the information a receiving bank can use.

A wallet introduces another possible boundary. Receipt of a casino payment into the wallet and a later transfer to a bank should be recorded separately. The PayPal article and Skrill article explain why an onward transfer is not automatically the same instruction as the casino payout.

If the issue concerns a duplicate or unrecognised transaction, describe that specific issue through the relevant provider's process. Do not treat every gambling loss, missing credit or payment disagreement as if it were the same kind of bank dispute.

The refund and dispute page explains the importance of preserving the reason for an enquiry. It does not guarantee that a bank or operator will reach a particular decision. The actual facts and applicable process remain with the organisations handling the case.

Choose the evidence for the recipient's part of the enquiry. A bank entry or a confirmed outgoing reference may be all that is relevant to the question. Sending every organisation the same unrestricted folder exposes more information and can make the record you want checked harder to find.

Explain a game-rule question using the release and the round

For a game enquiry, record the exact release or table variant and the round reference, where available. A studio name or broad category may leave several versions in view. Artwork from an article is not a reliable way to identify which configuration you opened in an account.

Then identify the rule that appears relevant. A natural-blackjack payout is different from the outcome of another winning hand. A slot feature trigger is different from an ordinary symbol payment. The recipient needs to know which rule and which recorded event you want connected.

Describe what you saw and ask how the recorded round was settled. An interrupted animation can justify that question without proving that a particular award is due. A screenshot preserves the display at one moment; the account history is needed to connect it with the recorded result.

The rules index and named-game library provide background explanations. They do not inspect your session or certify that a third party's configuration matches the information described in an article. Use the opened game's own information for the account-specific version.

Do not replay a hand or spin to try to reproduce the earlier event. A new round cannot replace the original identifier and may introduce a different outcome. The useful support question concerns the existing record and the rule applied to that record.

If you believe the publication's explanation is wrong, that is a separate editorial matter. Identify the passage and an accessible primary source. Private game history belongs in the genuine account-support process, not in a public request to revise a general article.

A useful editorial correction identifies a precise statement

For a correction, start with the page address and the sentence or table cell concerned. Quote enough to identify the passage, then explain what appears wrong. An editor needs a claim to check against a source, not a copy of the entire article with no indication of the disputed point.

Identify the relevant product, market and date. A provider offering a feature elsewhere is not necessarily evidence that a British guide is wrong. A different game configuration does not automatically invalidate a statement about the configuration explicitly identified in the article.

If a calculation seems wrong, show its inputs and the step where your answer differs. The disagreement may concern arithmetic or the meaning of an input. Returned stake and profit, for example, are different quantities even when both are included in the same final payment.

An accessible primary source is generally more useful than an unsupported assertion that another website says otherwise. A bank, provider, studio or public body's own material can identify the scope of the statement. Preserve any qualification that appears beside the figure or rule.

Do not supply an identity document or complete bank history to prove an editorial wording issue. Those documents would not give the publication authority to inspect your private case. A correction can usually explain the public inconsistency without exposing unrelated personal information.

The editorial policy explains how we handle examples, source dates and uncertainty. No sending mechanism is available on this page and no response timetable is promised. You can use the guidance to prepare a precise correction privately, but reading it does not create or submit a publication report.

Describe a broken link by its label and destination

For a broken link, note the page, the visible link label and what opened when you selected it. If an error appeared, record that too. These details help distinguish a wrong destination on our site from a later problem inside an external service we do not control.

The navbar uses the same destinations throughout the site. Cashier opens the payment hub; Game rules opens the game index. The disclosure next to either section name opens its related articles. If the destination differs from that description, identify the label and page so the inconsistency is clear.

Play opens the local game library. It does not create an operator account or authorise a gambling transaction. If it opens an unrelated destination, that would be a navigation defect worth identifying through the page and link label rather than a reason to disclose account details.

A source reference can behave differently from an internal article link. The reference may open another organisation whose availability the publication does not control. Record whether the issue concerns the link itself or a later step within that organisation's service.

If an old bookmark leads to the page-not-found guide, use the current section links to locate the intended subject. A missing path does not establish that a transaction or account has disappeared. The website's article addresses and an operator's account records are unrelated systems.

Do not add private information to a page address while trying to demonstrate a link problem. A transaction reference or email address in a query string may be exposed wherever that address is copied. The plain article path and the visible label are normally enough for a navigation report.

Describe a display problem without exposing private screen content

Describe the device context and the element you cannot use or read. A heading extending beyond the screen is a different problem from a table scrolling inside its own bordered area. Explain what happens and which part is affected, rather than reporting only that the whole page looks wrong.

Before sharing a screenshot through any future publication channel, check its edges as well as the article. Crop or redact unrelated tabs, messages and account details. A layout problem on a public page can be shown without exposing a banking app, an inbox or another person's notification.

Record whether the issue occurs before or after opening a menu, contents list or reading card. Those controls can change what is visible without changing the article itself. A precise description helps distinguish an overlapping element from a normal expansion in document flow.

The reading cards can be closed through their labelled close control, Escape or the surrounding backdrop. They do not require a personal submission. If a card obstructs another control or does not close, describe the page and the visible state rather than supplying private browsing history.

Images should have descriptions of their subjects, and the main text should remain available independently of a provider practice view. If a practice view cannot load, the article still supplies its explanatory content. A report should identify which of those elements failed.

A reproducible observation would help with a future display report: the page, the control and what happened when you used it. We cannot diagnose every device from a general description. This page offers no remote session, software installation or file-upload service, and does not invite access to your device.

Report a source or image concern at its actual scope

A source concern needs the statement it supports and the reason that support appears to have changed. A page failing to open is one observation; a page publishing contradictory information is another. Keep them separate so an access failure is not mistaken for evidence of a factual change.

If a source moved, the useful information is its genuine new location and the relevant passage. Do not use a lookalike domain or an unrelated review page as a replacement solely because the original address is unavailable. The subject and authority still need to match.

For an image concern, identify the scene and the article containing it. Our generated artwork illustrates a subject; it does not document a deposit or a round we played. It cannot establish a reader's balance or the exact version of a game, however familiar the theme may look.

Where an official provider asset is attributed, the attribution is separate from a claim that the publication created that asset. An issue with the attribution should identify the file or caption and the relevant public source. There is no need to attach a reader's account screenshot.

The About page explains the publication's scope and the role of its visuals. The editorial policy explains why artwork must not override a verified factual description. A precise concern can address that relationship without turning the report into a private game dispute.

No public rights or correction channel is currently available here. This section explains what a future report would need to identify, but it cannot receive one or promise a handling process. If a channel is introduced, its purpose and contact details will need to be stated before readers are asked to use it.

Keep personal records within the appropriate secure channel

Do not put account credentials, card security codes or one-time login codes into a publication enquiry or article address. They are not evidence needed to correct a sentence. Sharing them would not give this site a legitimate way to inspect your account or resolve the issue behind the correction.

Covering some details does not necessarily make an identity or payment-ownership document suitable to share anywhere. If an operator requests evidence, ask through its genuine secure process which fields must remain visible. We cannot decide whether a particular redaction will satisfy that account’s verification request.

For a transaction enquiry, provide the information the relevant organisation actually needs. A redacted entry identifying the disputed instruction may serve a different purpose from a statement used to establish ownership. The verification guide explains why those purposes should be separated.

If you are helping someone else, leave them in control of their account and support conversation. You can help order the chronology or clarify a question without logging in as them. There is no need to receive their passwords, security codes or authority to act through a different identity.

Keep downloaded evidence under your own control, especially on a shared device. Closing a tab does not necessarily remove a file saved to a downloads folder. The privacy notice describes the website's own behaviour and its lack of an account-document submission facility.

No public comment area is available here for posting account allegations or documents. The absence of such a feature is deliberate in this package. It prevents the page from appearing to offer a private case-review service that the publication does not supply.

Use direct support when the concern is about gambling harm

A publication correction and a request for personal gambling support are different kinds of contact. If gambling is affecting wellbeing, essential spending or relationships, use the independent organisations linked from the support guide rather than waiting for an editorial response.

The official GamCare website describes its own support options. Open the service directly to read current availability and privacy information. A source reference here does not create a confidential conversation with that organisation through this page.

You can stop gambling while a payment enquiry continues. Save the case and transaction references, close the game and use the official support route for the records. Another deposit or round is not needed to preserve the question, and cannot make the original enquiry more valid.

If reducing access is the immediate task, the self-exclusion guide distinguishes the relevant tools and their scope. It does not suggest alternate accounts or ways to defeat an exclusion. An outstanding balance should be discussed with the operator through its official process.

A trusted person can help organise a next step while you keep control of the account. That help should not require passwords or security codes. We cannot assess your circumstances, provide treatment or respond to an emergency, so use direct specialist support for the personal concern.

We do not offer a priority inbox, recovery fee or special payment channel for someone under pressure. Use specialist support for the gambling concern and the organisation holding the record for the account enquiry. Those tasks can continue separately, without a promise from this publication about either outcome.

What this page can help with

For now, this page helps you distinguish an account enquiry from a publication matter and points to relevant reading. It cannot receive a message or attachment, or create a case. There is no configured submission channel, so reading the guidance should not leave you expecting a reply.

A button that only appears to send a report would be misleading. So would an invented email address, postal address or staff identity. The current page states the limitation directly rather than leaving the reader uncertain about whether a message has been delivered.

If a publication channel is added in a later version, its actual purpose and privacy information would need to be described then. That change would not turn it into operator support or authorise the collection of account credentials. The boundaries described throughout this guide would still matter.

The reserved showcase on the home page is also inactive. It has no account destination and cannot accept a payment or register a reader. It should not be confused with a contact control, a submitted enquiry or confirmation of a commercial relationship.

For now, choose the existing article that matches the question, use the organisation's genuine channel for a private record and keep non-sensitive publication observations distinct. The site is an editorial reference, not a service for recovering gambling losses or guaranteeing the outcome of a complaint.

Before sending information, check that the route has a clear recipient and purpose, as well as a working submission mechanism. A name associated with the topic is not enough. For a private account issue, use the independently opened channel of the organisation that actually holds the record you need explained.