Platform notice
- Chargeback, payout hold, reserve, deduction, claim, compliance review, or decision notice.
- Exact text of any reason code, policy reason, or decision message.
- Date received and any response deadline.
Case intake
Send the facts we need, and nothing we should not handle.
After fit review or scope approval, use this checklist to send a clean evidence file. We work remotely from notices, screenshots, records, and timelines for clients in the US, UK, Canada, Australia, and EU. We do not need passwords or account access.
What to include
The minimum useful case file.
Timeline
- What happened first, second, and third.
- What you already submitted, changed, or answered.
- Any prior dispute response, support response, or internal decision.
Evidence
- Screenshots, emails, invoices, photos, receipts, tracking, payment records, or messages.
- Business documents, order IDs, transaction IDs, or retailer claim IDs where relevant.
- Public URLs or policy pages connected to the case.
Do not send
Some information should stay out of the file.
A cleaner file is safer and easier to review. Send only what helps explain the dispute, hold, claim, or platform issue.
No access credentials.
Do not send passwords, two-factor codes, recovery codes, private keys, or backup codes.
No full payment data.
Do not send full card numbers, bank login data, or unrelated financial records.
No unsupported claims.
Do not invent facts or ask us to create evidence. We organize the record you can support.
Suggested format
Make the first review fast.
Email subject
Use: Case materials - [platform or provider] - [business name] - [deadline if any].
File names
Name files by order: 01-notice, 02-timeline, 03-order-or-payment-records, 04-screenshots, 05-messages.
One summary
Include 5-10 bullet points explaining what happened and what outcome you are seeking.
One folder is best
If there are many files, send one folder link with view access instead of scattered attachments.