Docs
The short version of how Tash works.
Tash keeps the product intentionally small: create one invoice link, let the client pay in parts, track what is received, in transit, settled, verified, and remaining.
Core workflow
- The operator signs in, connects Stripe, and creates one Tash link for one invoice.
- The client opens the public link and chooses the full amount or a partial amount.
- Card payments complete in Stripe Checkout; manual EFT payments use proof upload and operator verification.
- Tash updates both sides as payment attempts move through received, in transit, settled, or verified states.
Product boundary
- Tash does not custody funds or act as merchant of record.
- Tash does not store card details or auto-charge clients.
- Stripe remains the card processor for Stripe-connected operators.
- Manual EFT verification remains an operator decision.
Trust pages
Start with the support, privacy, and terms summaries linked above. The deeper security overview, subprocessor list, retention model, incident policy, and legal readiness checklist live in the internal trust pack until externally reviewed versions are published.