PRACTICAL GUIDES
How to report a broken promo code and collect useful evidence
Reproduce the issue without another deposit, redact secrets and send a verifiable report.
1. Stop before paying again
Failure can come from spacing, expiry, new-account rules, region, minimum amount or a promotion already attached to the account. Check these without another deposit. If the code should be confirmed before payment, no confirmation is enough reason to stop.
- The code is copied without spaces
- Account, region and minimum are checked
- Another deposit is not used as a test
2. Record a reproducible path
Include the platform and exact domain, code, timestamp with time zone, input page, selected method and error text. List each step from opening the page to failure. Do not claim that a code fails for everyone after testing one account.
- Domain, code and time are included
- Steps can be repeated in the same order
- The conclusion stays within observed evidence
3. Create a safe screenshot
Show the code field, system message and relevant terms, but cover login, balance, address, document ID, QR code, trade URL, payment details and 2FA. Do not send a full HAR or console export unless tokens and cookies have been removed.
- The code and error are readable
- Personal data and secrets are redacted
- No session token or cookie is included
4. Submit and follow the status
Ask official platform support first, then send the report to the directory with the ticket number. A code status should change after reproducible testing or partner confirmation, not one comment. Save the response and schedule a recheck.
- An official support ticket exists
- The source response is saved
- A recheck date is assigned
FAQ
Must I deposit to prove the error?+
No. Do not transfer money only to test; document the stage where confirmation should appear.
Can I send a balance screenshot?+
Crop or redact the balance and identifiers unless they are essential to the report.
Should one report remove a code?+
No. It should trigger review because region, account type or a temporary error may be responsible.