ZocumentsOn this page
The five-minute upload check
- 01Match the reason
Remove files that answer a different claim. A delivery scan will not explain an incorrect amount.
- 02Open the export
Check that text is readable, screenshots are not cropped, and pages are in chronological order.
- 03Check the limits
Confirm file type, per-file size, combined size, page count, and whether the portal accepts one or multiple files.
- 04Name the exhibits
Use labels that match the response and the portal field, not filenames like IMG_4821.
- 05Keep your copy
Save the exact submitted packet and confirmation outside the upload form if the processor does not provide a download.
What a usable file looks like
| File | Useful when it shows | Common failure |
|---|---|---|
| Carrier record | Delivered status, date, and address connected to the order | Tracking number with no delivery result |
| Receipt or invoice | Items, amount, currency, and transaction date | Tiny screenshot with the total cut off |
| Support thread | The customer's report and your specific response | A full inbox export with unrelated conversations |
| Policy excerpt | The terms accepted for this transaction | A current policy with no evidence it applied at checkout |
Remove noise, not proof
Crop unrelated messages, hide secrets and full payment credentials, and preserve the date, amount, order connection, and relevant text. Do not redact the very field that makes the record useful. See privacy & limits for how the local builder handles draft data.
Build after the files pass
The chargeback evidence guide helps choose records by reason. Once you have them, Zocuments can map attachments to evidence items and export one packet for you to review before submitting through your processor.
