Developer support

How to get help — and how to write a ticket we can act on immediately.

All developer channels are staffed by engineers who work on the platform daily.

Channels

ChannelUse forResponse
developers@qashx.ioAPI bugs, integration help, sandbox issues.Business hours, < 1 business day.
security@qashx.ioVulnerability disclosure. PGP available.Acknowledged < 24 h.
incidents@qashx.ioLive production impact — payments failing.24/7 pager, < 30 min.
compliance@qashx.ioAML/KYC blocks, sanctions review, licensing.Business hours, < 2 business days.
Status pageLive uptime and incidents.Coming soon at /status.html.

SLAs

PlanResponseUptime target
Developer (free)Best-effort, business hours.99.5%
Growth< 4 business hours.99.9%
Enterprise24/7, < 30 min for P1.99.95% with financial credits.

Writing a productive ticket

Include every item — it lets us skip the back-and-forth:

  1. The request_id from the response (or X-Request-Id header).
  2. The environment (test or live) and the last 4 chars of the API key.
  3. Full request URL, method, and redacted body.
  4. Full response status, headers, and body.
  5. The exact time (with timezone) the failure occurred.
  6. The behavior you expected vs what you observed.

Never send raw API keys or webhook secrets. If you must reference one, share only the last 4 characters.

Vulnerability disclosure

We follow coordinated disclosure. Report to security@qashx.io — do not open public issues.