Lock the identity record
Capture landing, login and cashier domains plus contracting entity and support address used when the event occurred. Preserve redirect history and any merchant or wallet recipient.
This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Describe one primary issue
Classify registration, KYC, deposit, crypto attribution, withdrawal, bonus, account closure or support conduct. State amount, currency or asset, network and requested remedy precisely.
Build the evidence sequence
List transaction hashes, payment references, account ledger states, ticket numbers, documents supplied and responses in chronological order. Redact secrets while retaining originals.
Escalate to the correct body
Use the verified operator process, then check regulator, ACMA, bank, exchange or cyber-reporting competence for the actual issue. A recovery guarantee is not an official route.
Do not pay to unlock a complaint
Requests for crypto prepayment, tax, insurance, seed phrases or remote access are separate warning signs and should be documented without complying.
Questions this page resolves
Which Caswino domain should I name?
The exact hostname used for account and transaction actions, including redirects.
Can a regulator trace a crypto payment?
Provide the transaction hash and operator identity, but competence depends on the body and issue.
Should I open many support chats?
Prefer one complete case with a reference and written final response.