Screenshots Proof

Capture the relevant screen and exact status or error, keep useful time and reference details when safe, and explain the sequence of events in a short timeline.

Show enough of the page to identify the transaction, account step or setting involved. A tiny crop of an error message may omit the context support needs; capture the full message and the surrounding screen where useful.

If displayed, note the date, time, status, amount, currency and transaction or ticket reference relevant to the issue. Keep screenshots in order when several steps matter, and preserve the original files when possible instead of repeatedly recompressing them.

Before sharing, hide unrelated personal details and never include passwords, private keys, seed phrases, one-time codes or full payment credentials. Use the platform's official support channel and include a brief account of what you expected, what happened and what you already tried.

Evidence capture checklist

• Relevant page or step, not just an isolated crop
• Exact error or status text shown on screen
• Date and time when useful and available
• Safe transaction, withdrawal or ticket reference
• Ordered screenshots for a multi-step issue
• Short timeline of expected and observed behavior

Before you share

• Redact passwords, seed phrases, private keys and one-time codes
• Hide full payment credentials and unrelated personal data
• Avoid recropping until the relevant context is lost
• Do not treat a screenshot as a guaranteed dispute outcome

Save the original captures, redact information unrelated to the case, and send the ordered evidence with a short timeline through official support.