How should payment screenshots be presented evidentially?¶

Payment screenshots should be presented as captured views of an application, account or transaction, not as complete provider records.

Avoid this assumption: That a screenshot is self-explanatory, complete and sufficient to prove the transaction and user. Preserve the original image where possible.

Record the source device, application or website, account context, date obtained, displayed time, timezone and who captured it.

Avoid cropping away the account name, transaction reference, status, navigation context or surrounding entries unless a separate full version is retained.

A screenshot may show a balance, payment, wallet address, receipt or transaction hash.

It may not show whether the item was pending, reversed, refunded, edited or displayed in a different currency.

Images can also be altered, forwarded, recreated or generated from another account.

Compare the screenshot with provider records, transaction exports, merchant evidence, bank statements or blockchain data.

Where metadata is available, preserve it. Record whether the image came from the original device, a message attachment, cloud storage or another secondary source.

Do not assume that the person possessing the screenshot controlled the account or completed the transaction.

They may have received it from someone else or captured a shared screen.

When presenting the evidence, label the screenshot accurately and explain what it depicts.

Identify any missing context or inconsistencies.

Do not use a screenshot as a substitute for requesting the underlying provider record where that record is material and obtainable.

Operational takeaway¶

Present payment screenshots as contextual visual evidence, preserve their source and full display, and verify the underlying transaction through provider, merchant or blockchain records.