Support

Clear support for payment workflows.

Tash support focuses on payment-link availability, Stripe connection health, evidence upload safety, notifications, and ledger correctness.

Pilot support policyLast updated 19 May 2026

Channels

Operators can reach support at [email protected]. Security issues should go to [email protected] so they are routed directly to the incident process.

Never send raw secrets, full card details, unredacted database URLs, or raw public-link tokens through support email.

Severity levels

  • Sev 1: payment creation, auth, tenant isolation, evidence safety, or ledger correctness is critically affected.
  • Sev 2: a major workflow is degraded but a workaround exists.
  • Sev 3: a non-critical defect or confusing product behavior needs correction.
  • Sev 4: a product question, feature request, or documentation request.

Escalation triggers

  • A ledger entry appears duplicated, missing, or inconsistent with the source payment attempt.
  • A user can see data from another organization or a public token may have leaked.
  • Stripe webhook verification, replay handling, refunds, disputes, or payout state looks wrong.
  • Manual evidence upload, malware scanning, private storage, or signed URL access behaves unexpectedly.
  • The production API, worker, database, email provider, or public payment links are unavailable.