How to Build Proof for a BC Game Deposit or Withdrawal Dispute
This page is a general framework for evidence, not a fix for one specific problem. Whether the issue is a deposit, a withdrawal or an account restriction, the underlying discipline of proof-building is the same.
Strong evidence means exact timestamps, transaction IDs, account UID, network details and screenshots gathered before you contact support, not reconstructed from memory afterward.
Why evidence quality decides outcomes
Support teams cannot resolve what they cannot verify. A dispute backed by exact figures, identifiers and screenshots moves through review far faster than one based on a general description of what supposedly happened.
The core evidence checklist
| Evidence type | Why it matters | When to capture it |
|---|---|---|
| Account UID | identifies your account precisely | have it ready before contacting support |
| Transaction ID (TXID) | proves a specific transaction exists | immediately after sending or receiving funds |
| Timestamp | anchors the case to an exact moment | at the time of the action, not later |
| Screenshot of status screen | shows what you actually saw | as soon as something looks wrong |
Screenshots that actually help
- the deposit or withdrawal status screen showing the exact state at that time
- your sending wallet or payment app confirming the transaction
- any error message shown, captured exactly as it appeared
- the amount, date and time visible in the same frame where possible
Timestamps, TXID and wallet route details
For crypto transactions, the transaction ID or hash is one of the strongest pieces of evidence available, since it can often be independently verified on the network itself. Pair it with the exact date, time, asset, network and destination address to remove any ambiguity about which transaction you are referring to.
How to present evidence clearly
Organise your case in a logical order: what happened, when it happened, what proof you have, and what outcome you are asking for. A single, well-structured message with attachments is far more effective than the same information spread across several disconnected messages.
Common evidence mistakes
- taking screenshots only after the issue has already changed or disappeared
- describing an amount or date from memory instead of checking the actual record
- submitting a transaction ID without confirming it matches the exact transaction in question
- sending evidence across multiple separate messages instead of one organised case
Frequently asked questions
What is the single most useful piece of evidence for a BC Game dispute?
For crypto transactions, the transaction ID is often the strongest evidence, since it can frequently be verified independently on the network.
When should I take screenshots?
As close to the moment of the issue as possible, not after the screen or status has already changed.
Should I send evidence in one message or several?
One organised message with all relevant details and attachments is more effective than splitting the same case across multiple messages.