Build a Complete JustBit Complaint Evidence File

Build the chronology from primary records

List deposits, gameplay or bonus state, withdrawal requests, verification messages, restriction notices and support replies in timestamp order. Attach transaction hashes, request IDs and balance screenshots to the event they prove.

Separate what the account displayed from what support later said. Do not fill a missing fact with an assumption about why the account was blocked.

• Transaction and withdrawal IDs
• Exact restriction wording
• KYC submissions and receipts

State one requested resolution

Ask for a specific outcome: identify the missing verification item, restore account access, process an eligible withdrawal or provide the clause used for a decision. Include a reasonable response date and keep the request in the same case.

Avoid duplicate tickets, abusive messages or contradictory versions. A calm file makes it easier for an internal reviewer or independent mediator to follow the money and decisions.

• Amount in dispute
• Current owner of the case
• Requested remedy and date

Escalate without exposing secrets

If the internal process stalls, prepare a redacted version for the complaint channel relevant to the operator's current terms and licence. Verify the operator identity and jurisdiction from the live footer before choosing a destination.

Redact passwords, one-time codes, full card data, private keys and unnecessary identity numbers. Keep the unredacted evidence offline for the authenticated process only.

Questions players ask