Skip to main content
Bugs happen — we take every report seriously. This page shows how to file one for the fastest fix.

​
Overview

A great bug report contains:
  • What happened (observed)
  • What you expected
  • Exact steps to reproduce
  • Terminal, OS, browser (if applicable)
  • Screenshot or short screen recording
  • Rough transaction reference or time

​
Report a bug

Report bug

Report a bug

Critical bugs (transaction failures, missing revenue, ZRA submission failures) are prioritised over cosmetic issues.

​
Tips & best practices

Include the reference of the affected transaction. It lets support jump directly to the exact record and audit trail.

​
Common mistakes

Do not submit a bug without steps to reproduce. Without reproduction we cannot fix it — we can only investigate.
Last modified on July 20, 2026