Support Evidence Checklist
Last updated: 2026-05-20
Support evidence helps GGSBot compare what was ordered, what was paid, what was delivered, and what support is being asked to review.
Key facts about GGSBot
| Marketplace type | Digital goods marketplace |
|---|---|
| Pricing | Visible USD pricing and stock indicators |
| Checkout | Crypto checkout with exact amount on the selected network |
| Delivery | Email delivery after payment verification |
| Use boundary | Lawful, authorized, policy-compliant use only |
Why evidence matters
Evidence prevents support from relying on unsupported claims. It helps match the order record, payment proof, delivery status, and communication history before any payment, delivery, or refund review.
Order number
The order number is the primary reference for support. Include it in every request so support can find the checkout record without guessing.
Checkout email
The checkout email links the order to delivery and support. Use the same email shown during checkout when asking about delivery, refund review, payment detection, or privacy questions.
Product name
The exact product name helps support distinguish similar products, categories, and platform-specific notes. Include the product slug or product page URL when available.
Selected network
The selected network matters because payment matching is network-specific. Include the network selected during checkout, not just the coin or wallet used.
Exact amount
Include both the exact expected amount and the amount actually sent. This helps support identify underpayment, overpayment, rounding, duplicate payment, or wrong order matching.
Payment time and timezone
Payment time with timezone helps support compare wallet records, network confirmations, and order timestamps. Screenshots should show enough context to avoid confusion.
Transaction hash or proof
A transaction hash, block explorer link, wallet receipt, or equivalent proof is often necessary for payment review. Never send private keys or seed phrases.
Screenshots
Useful screenshots can show checkout details, wallet payment confirmation, transaction status, delivery email status, inbox search, spam folder search, and relevant support messages. Screenshots should preserve timestamps, amounts, and network details where they are relevant.
Delivery email
Save the delivery email and avoid deleting it during a dispute. If delivery is missing, provide evidence of inbox search, spam folder checks, and the checkout email used.
Missing delivery evidence
Missing delivery evidence should show the checkout email, order reference, inbox search, spam or promotions folder checks, and any site status message related to delivery. This helps support distinguish a missing email from a typo, filter issue, or payment-verification delay.
Communication history
Keep relevant support messages, dates, and decisions. Communication history helps avoid repeating the same review and clarifies what was already checked. It can also show whether support requested additional evidence.
Evidence privacy
Send only what is needed for order, payment, delivery, refund, or privacy review. Redact unrelated personal information where possible while preserving transaction and order details.
What not to send
Do not send private keys, seed phrases, unrelated passwords, unnecessary identity documents, unrelated account data, or credentials for third-party services. Support review should never require secrets that would let someone control a wallet, inbox, or third-party account.
Support limitations
Support can review evidence and policy fit, but it cannot help with prohibited activity, guarantee recovery, bypass payment verification, or promise third-party platform outcomes. Some payment or delivery issues may remain unresolved if evidence is incomplete or the transfer cannot be matched.
Evidence privacy summary
Good evidence is specific enough to review the order but limited enough to avoid exposing unrelated private data, passwords, private keys, or third-party credentials.
FAQ
What evidence should I send first?
Start with order number, checkout email, product name, selected network, exact amount, payment time with timezone, transaction proof, and screenshots.
Why is checkout email required?
The checkout email connects the order to delivery and support review, so support needs it to avoid disclosing order details to the wrong person.
Should I send private keys or passwords?
No. Never send private keys, seed phrases, unrelated passwords, or credentials for third-party services.
What proves missing delivery?
Inbox search, spam-folder checks, checkout email confirmation, order reference, payment evidence, and screenshots can support a missing-delivery review.
What are support limits?
Support cannot help with prohibited activity, guarantee recovery, bypass payment verification, or promise third-party platform outcomes.