Contact and correction guidance

If a payment needs tracing

Contact the organisation responsible for the last confirmed stage. The bank handles its account entry, the wallet handles its own transaction, and the operator handles the gambling-account balance and withdrawal request. Use a verified application or official website to reach them.

Provide the relevant amount, currency, date, transaction reference and case number through their secure channel. Do not send passwords or one-time codes. Remove unrelated statement entries unless the provider specifically needs them for its investigation.

The statement guide explains how to distinguish a bank-side record from an operator receipt. The wallet hub explains why a merchant payout and a later bank transfer need separate identifiers.

If a public article appears wrong

A useful correction note contains the page address, the precise statement, a current primary-source link and the date of the change. An operator's current help page is more useful than a screenshot of an unrelated affiliate ranking.

Keep personal account evidence out of an editorial note. An article can be corrected without exposing your name, balance, full card number or identity documents. The editorial policy explains how uncertain facts are handled.

Complaints and support

A dispute with a gambling operator should begin through its published complaints procedure. The Commission's guidance explains escalation to the appropriate alternative dispute resolution service. Payment Table GB cannot make that decision or file the complaint on your behalf.

If gambling is causing concern, use the support resources directly. Those services are separate from this publication and are a more appropriate route for help than an unavailable editorial inbox.

Choose the recipient by the action required

What do you need someone to do? A bank can explain an entry on its statement. A casino can explain its account balance or a completed round. An editor can correct a public article. Naming the job first helps you find the right recipient; a general search for casino contact details can send you to an organisation that cannot answer the question.

For example, a wallet receipt showing an outgoing merchant payment raises a different issue from a wallet-to-bank transfer. The wallet can explain its own record and reference; the operator can explain the gambling-account credit; the bank can explain its own incoming or outgoing entry. Matching amounts alone do not give one organisation access to the others' records.

Payment Table GB cannot inspect any of those systems. The guidance here can help identify the relevant stage and prepare a concise description, but it cannot authenticate an account holder, move money, release a withdrawal or promise that a complaint will succeed. No direct editorial inbox is available in this local edition, so this page should not be treated as a place to submit an urgent case.

If the need is support with gambling rather than a record explanation, go directly to the independent support page. An unresolved withdrawal or a difficult account interaction can coexist with a need for support. You do not have to complete the administrative task before contacting the appropriate independent service about how gambling is affecting you.

Build a chronology from confirmed events

Put the events in order before writing to support. Start with the date and time shown on the payment, its amount and currency, the method used and the displayed status. Then explain what you expected to see next and what is actually missing. A short sequence gives the recipient somewhere to start without making them reconstruct the case from scattered screenshots.

Copy the label beside each timestamp, including the time zone where one is shown. Authorisation, wallet receipt and bank posting describe different events, so their dates need not match. If you cannot tell which event a time refers to, ask the provider. Comparing unexplained timestamps can suggest a delay before you have established when the relevant transfer actually started.

Include a separate line in your private notes for each attempt. A second payment with the same amount is still a second event and may have another reference. Combining them into one description can make an apparent duplicate harder to investigate. Avoid creating further attempts while the original status remains unclear, because every additional transaction adds another record to reconcile.

The chronology need not contain every unrelated transaction on the account. Its purpose is to isolate the event under discussion. Use the provider's secure process for any records it specifically requests, and retain the original privately so that a cropped or redacted copy does not become the only evidence available to you.

Distinguish a request from a released payment

A withdrawal request can exist before a payment has been sent. A page showing that the request was received therefore does not necessarily provide the reference for the outgoing bank or card transaction. Ask the operator which stage the request has reached and whether a payment reference exists for a completed release.

Likewise, a receiving bank cannot necessarily trace a payment from an operator's internal request number alone. The relevant identifiers depend on the route. The withdrawal-reference guide explains the distinction between a card-related reference and an operator's own record. Do not assume that every transfer has the same kind of reference or that one identifier can be substituted for another.

A useful description might say that an operator marks a request as completed but the expected destination has no corresponding credit. That identifies the conflict without deciding who caused it. Ask the operator for the route, destination description and appropriate trace information; then use that information with the receiving provider through its verified channel.

Send that question to the organisation handling the missing stage. It can explain its own status and tell you what information to take to the next provider. Copying the same message to unrelated companies usually leaves the central question unanswered: which event are they being asked to trace? The guide helps frame that question, but cannot locate money inside their systems.

Describe a bank entry without guessing its cause

A statement descriptor may differ from the familiar product or website name. That difference is a reason to identify the transaction, not proof that the payment is fraudulent or that a casino has added a fee. Compare the amount, currency and date with your own records, then ask the bank or relevant provider to explain the entry if it remains unfamiliar.

The bank-statement guide helps distinguish a source-account entry from a merchant receipt. If you first funded a wallet and later paid an operator, the bank may show the wallet-related stage rather than a direct casino payment. Both records can be real without being identical descriptions of the same event.

If you do not recognise an entry, say exactly that and explain what you have checked. Do not describe it as unauthorised merely because the merchant name looks unfamiliar. If you suspect an unauthorised payment, follow the bank's process for that concern. The bank needs your account of the events; this publication cannot classify the transaction or choose a complaint category for you.

Do not post a full statement in a public comment or send it to a supposed helper who contacted you unexpectedly. The relevant provider may need sensitive evidence through a verified secure channel. An editorial discussion needs far less: usually the public statement being questioned and the source that contradicts it, rather than your personal financial history.

Explain a minimum without authorising another payment

If a cashier amount differs from a public help table, record the exact method name and GBP amount before doing anything further. A saved-card checkout, debit-card form and bank-authorised payment may have separate instructions. A complaint saying only that the minimum is wrong can conceal that the public page and account screen refer to different routes.

Show support the two instructions you are comparing: the heading and minimum on the help page, then the method and required amount displayed in your account. Redact personal details from a screenshot before sharing it through the verified channel. Ask which instruction applies. You can get that clarification without sending a payment to find out which number the cashier accepts.

For residual money below a withdrawal threshold, ask the operator about returning the remaining cash balance. Adding money or placing another bet changes the situation and can create further losses. The minimum-withdrawal guide explains the reading task; it does not establish that every operator uses the same manual process or promises a particular result.

The small-deposit comparisons are documentation examples, not support channels for the operators named. If a method is unavailable in an actual account, the comparison cannot activate it. A published logo or a previous successful transaction also cannot override an account restriction. Clarification belongs with the provider responsible for the current instructions.

Keep game settlement separate from cashier settlement

A game return is not the same event as a withdrawal to a payment account. In baccarat, a displayed return may include the original stake. In roulette, one winning component may be offset by losing components in the same allocation. Those calculations should be resolved against the round record before describing a difference as a missing bank payment.

For a game inquiry, identify the exact game and version, round identifier, bets placed, result and rule you believe applies. The table-game guides explain particular terminology, but the game's own current help supplies the relevant version-specific instructions. A cropped balance image without the round details may not establish what was staked or settled.

Keep hypothetical examples from the articles out of the factual account of your round. Our £20 commission illustration explains a calculation; it is not evidence that your table used that commission or that your own bet had the same amount. State the actual record and ask the operator to explain its treatment under the published rule.

Playing another round is unnecessary for making that inquiry. A fresh result cannot validate the historical record and may introduce another loss or confusion. Preserve the old identifier and ask for a component-by-component explanation. This publication does not review private game logs or adjudicate the operator's explanation.

Prepare a public-source correction note

An editorial correction should identify a public claim rather than request an account action. Start with the article address and copy the specific sentence into your own note. Describe what needs changing: an outdated amount, an incorrect definition, an arithmetic error, an ambiguous scope statement or a source that no longer supports the wording.

Then identify the primary evidence. Include the source address, relevant heading and the date you observed the information. A provider's own terms or help page usually addresses a product claim more directly than a third-party ranking. Where the source is historical, retain its date instead of presenting an old statement as the current universal position.

Point to the precise change the evidence supports. If a help page changes the minimum for one method, identify that method instead of asking for every payment row to be rewritten. In a game guide, a corrected blackjack payout leaves the dealer's soft-total rule as a separate issue. A narrow correction is easier to check and less likely to disturb accurate information elsewhere.

There is no submission facility represented here, and preparing a note does not create one. The publication's real contact arrangements must be established before a public launch. Until then, retain your note privately and use the official organisation directly if the issue also affects an account action that cannot wait for an editorial update.

Send only the evidence the recipient needs

Match the evidence to the recipient. For a bank enquiry, use its own authentication process and supply the transaction details requested. For a game settlement, the operator may need the round identifier. For a public definition, an editor usually needs only the sentence and a source link. Your name, balance and card details do not help establish what a published rule says.

Redaction should remove information rather than merely make it less noticeable. A full screenshot can reveal a name in the header, a balance in another panel or unrelated transactions below the relevant entry. Inspect the whole image before sharing a copy. Keep the original securely for the provider if its verified investigation process requires it.

Do not share a password, PIN, recovery phrase or one-time code as proof of a correction. None is necessary to show that a public rule or amount has changed. If a support interaction asks for sensitive authentication, verify that you are in the organisation's official application or website and follow its own security guidance rather than a link supplied by an unknown helper.

This page does not provide a secure upload channel. A familiar logo or an article about a wallet is not evidence that the publication is authorised to receive that wallet's account records. Keeping the evidence with the organisation that can act on it is more useful than distributing it widely to readers or unrelated services.

Use official entry points for account support

Reach a provider through an application you already use or by navigating to its official website. Check the organisation and service before entering account information. A search result, social-media reply or private message that uses the right product name is not enough to establish that it is the verified support route for your account.

If an unfamiliar person offers to trace a withdrawal, release funds or recover a transfer, do not infer authority from their knowing a public transaction term. The relevant bank, wallet or operator has its own authentication process. Payment Table GB does not appoint recovery agents, contact readers about pending funds or request a payment to unlock a supposed balance.

For crypto-related records, an asset address or transaction identifier can be useful evidence without giving anyone the ability to reverse the transfer. A recovery phrase is a different kind of information and should not be sent as part of an inquiry. The crypto-methods guide distinguishes the route and its records without promising universal recovery.

When you have a genuine existing case, quote the provider's case number in follow-up communication through the same verified system. This helps connect the discussion without circulating sensitive documents again. The publication cannot authenticate an adviser or inspect the case, so any account-specific verification remains between you and the responsible organisation.

Keep a complaint distinct from an information request

An information request asks what a status, rule or deduction means. A complaint asks the organisation to consider a stated concern through its complaints procedure. Both can begin with the same facts, but the desired action should be clear. Use the operator's published process when making a formal gambling complaint rather than assuming every live-chat question automatically starts that process.

The Gambling Commission's complaints guidance is the appropriate starting point for understanding the published route and alternative dispute resolution context. Read the current guidance and the operator's procedure directly. This page does not supply a universal timetable or decide which independent body can consider a particular dispute.

Organise a complaint around four points: what happened, the evidence you have, the answer already received and the outcome you want. Use the amounts from your own case, not an article's hypothetical calculation. Keep the correspondence and case references together. Someone reading the complaint should be able to follow its history without searching through a folder of unrelated screenshots.

Payment Table GB cannot submit the complaint, represent you, order a refund or predict an outcome. An editorial correction and a complaint can proceed as separate matters: an article may need narrowing even if the account dispute remains unresolved. Conversely, a personal outcome does not necessarily establish a new general rule for every account or operator.

Make the next message easier to answer

Read the draft once as if you were the person receiving it. Can you tell which service and payment it concerns? Is the reference for an event that recipient handles? End with a clear request, such as an explanation of a status or the reference for a released payment. Put unrelated account concerns in their own message so the main question stays easy to answer.

Use concrete terms where possible. A statement that an operator receipt shows £10 while the destination record shows no matching credit is clearer than saying the money disappeared everywhere. If you do not know which route was used, say so and ask for it. An explicit unknown is more useful than a guessed method that sends the inquiry to the wrong department.

Keep the account concern separate from any pressure to recover losses. No support inquiry requires another wager to make its evidence stronger. If continuing the task is increasing an urge to gamble, pause it and use the independent support resources. The existing record can remain available without further play while you seek appropriate help.

This local edition offers guidance for preparing and directing an inquiry, rather than a destination for that inquiry. Its practical value is the distinction between an editorial fact, a payment record, a game settlement and a support need. Once that distinction is clear, the next action can go to the organisation that actually has the relevant role.

A hypothetical inquiry can be short and complete

Here is a hypothetical enquiry to prepare privately: an operator marks a £10 withdrawal completed, but the nominated destination shows no matching credit. You have the operator's request reference. Ask which route was used, whether the payment was released and which reference the receiving provider can trace. That gives support a specific discrepancy to investigate without guessing where the money is held.

That is different from writing that a payment is definitely lost or that every provider has delayed it. The verified operator can explain its own completion status and supply the relevant information. The receiving provider can then address its own record with the appropriate reference. The publication cannot perform either action or determine the location of the money from the hypothetical description.

For an editorial example, the equivalent concise note might identify an article's minimum-amount sentence, the official method table now showing a different amount and the date of observation. It would ask for that public sentence to be reviewed. It would not need the writer's gambling balance, transaction receipt or identity evidence, because the source itself addresses the public claim.

Before using any such structure, replace the illustration with the facts of the actual task. Keep unknowns explicit and do not attach a guessed network, payment method or rule. A well-directed inquiry is not a promise of a particular result; it simply gives the responsible recipient a clearer question to answer. No message should be sent to this preparation publication by inventing an address, because no direct monitored editorial channel has been established here.

Keep the existing case reference with any follow-up, and distinguish a request for information from a new complaint. The verified recipient's actual process determines how the message is handled.