#018
January 02, 2026:- Dispute System Draft & Match Redemption Workflow
Purpose
To design and initiate a transparent user-led dispute and account redemption process, while reinforcing Tapzi’s integrity as a skill-first competitive platform.
Key Highlights
🧾 Dispute Reporting Draft (User-Facing)
Initial dispute submission flow created with status tracking (e.g., “Under Review”, “Resolved”).
Upload functionality enabled for evidence (screenshots, replay hashes).
Replays now flagged within backend for administrator audit view.
💻 Redemption & Appeal Framework Initiated
Players flagged for suspicious activity can now submit redemption forms.
Backend logic queues flagged users for manual review with timestamp and session metadata.
Admin panel shows behavioral context (match pacing, reconnection patterns, historical flags).
📈 Dispute Event Telemetry Logging
Every flagged dispute emits structured logs to the event pipeline.
Feed supports upcoming audit timeline UI and training data for anti-cheat tuning.
Match reward distribution paused on flagged accounts pending resolution.
📣 Discord & Email Alerts Linked to Disputes (Internal)
Admins receive real-time alerts when a new dispute is filed or escalated.
Basic reminder system active—escalated disputes not reviewed within 72 hours trigger re-alert.
Why It Matters
Builds user trust by offering clear, fair pathways for resolving false flags or bad moderation.
Reduces long-term support load via automation and asynchronous appeal flow.
Lays groundwork for transparent moderation logs and community trust scoring.
Improves internal review cadence through automated prioritization.
Open Issues
Some dispute event timelines misaligned due to clock desync across microservices.
Evidence upload does not currently preview images (e.g., .webp, large PNGs).
Redemption flow lacks user notification logic post-decision.
Fixed
Admin reviewer reassignment now includes audit log entries with reviewer ID + timestamp.
“Flagged Match” label now visible in admin replay viewer.
Repeat dispute resubmissions from same user are throttled to prevent spam.
Next Steps
Add document preview for uploaded evidence (lightbox/image viewer in UI).
Integrate automated dispute response timer and reminder email flow.
Push anonymized dispute verdicts into anti-cheat model training corpus.
Begin internal review on feedback language used in rejected appeals.
Last updated
Was this helpful?

