Preserve original records
Export statements or receipts where available and keep screenshots as supporting context, not the only copy.
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.
Show stable identifiers
Include transaction ID, amount, currency, date, descriptor and masked destination sufficient to match both sides.
Capture page context
Record the exact hostname, cashier state, terms version and visible status without exposing session tokens.
Build a dated chronology
List instruction, authorisation, credit, withdrawal request, approval, dispatch and receipt in one ordered table.
Redact before sharing
Remove passwords, full card numbers, security codes, seeds and unrelated transactions while retaining evidence needed for tracing.
Evidence should be complete without becoming a credential leak
A support team needs traceable facts, not access to the account. Never provide remote-control access or live authentication secrets to prove a transaction.
Questions this page resolves
Is a bank screenshot enough?
Usually not; pair it with a statement or reference and the matching casino transaction record.
Should I edit the original file?
Keep an untouched original securely and create a separate redacted copy for sharing.
How should messages be stored?
Retain full headers or ticket IDs, dates and the verified contact channel rather than isolated chat fragments.