Skip to content
CasinoCanFollow the money, understand the account
Follow the money, understand the account

Recognising a legitimate route for Zora account help

When a payment or account issue needs help, open support through the Zora interface you have intentionally accessed.

3 min read
01

Start from the operator interface

When a payment or account issue needs help, open support through the Zora interface you have intentionally accessed. An unsolicited message claiming to know about a delayed withdrawal is not evidence that its sender represents the operator. A review website such as CasinoCan does not hold your casino account, cannot release funds and should not receive login credentials. Check the destination before sending a document or entering sensitive information.

02

Separate investigation data from authorisation data

A transaction reference, amount and observed status can help identify an issue. A password, card security code or one-time authorisation code serves a different purpose and should not be shared in a support conversation. If a message asks for a new payment to unlock an unexplained prize or accelerate a payout, do not infer legitimacy from the use of Zora’s name or logo. Verify the request through the operator’s own support route before taking action.

03

Keep the response connected to the original case

Use the case reference and compare any requested action with the issue you raised. A document request should have a stated purpose and a secure submission route; clarify uncertainty instead of sending a broad collection of personal records. If you suspect that account credentials were exposed, use the operator’s account-security process rather than discussing the secret itself in public. This guide explains a cautious communication workflow, not a guarantee that a particular message or website has been authenticated by CasinoCan.

Public terms: identification and verification are separate account requirements
Public terms: identification and verification are separate account requirementsPublic Zora interface · 9 November 2026 · English version.
04

Verify a conversation through a known route

If a message arrives outside the channel where you opened the case, return to the operator interface independently and ask whether it belongs to the existing reference. A sender who repeats a public promotion amount or uses the correct logo has not thereby proved access to your case. Compare the requested action with the issue you actually raised. A question about a missing game credit should not require handing over control of your device or approving an unrelated payment. Do not follow a new link merely because the message says it is urgent. Use the operator’s known account route to clarify the request before disclosing information.

05

Prepare a minimal evidence packet

For a deposit question, the amount, currency, time, provider reference and casino reference may identify the record without exposing unrelated transactions. For a round question, the title, accepted stake and round identifier are more relevant than a full bank statement. Follow any legitimate document requirements through the designated secure upload route, and clarify permitted redaction instead of changing evidence arbitrarily. Keep an index of what you sent and which case it belongs to. This reduces the chance of forwarding the wrong file when several issues are open. Do not put passwords, security codes or one-time approvals in screenshots or text intended for troubleshooting.

06

If the requested action does not fit the case

Pause and state the mismatch through the verified support channel. For example, ask why a request concerning a payment reference would require a new payment, a remote-control session or a change to account contact details. Do not test the request with a small amount or a partial credential. If you already disclosed a secret, stop reusing it in messages and follow the relevant account-security process through the service itself. Preserve the suspicious message without publicly posting sensitive details. CasinoCan cannot authenticate an individual correspondent or recover an account; this workflow helps you keep investigation evidence separate from the permissions that authorise access or movement of money.