Terms
Tash coordinates payment journeys. It does not hold the money.
This page summarizes the product boundary that operators should understand before using Tash for staged invoice payments.
Product role
Tash creates payment links, records payment attempts, receives provider webhooks, writes ledger entries, and sends status notifications. Operators remain responsible for their invoices, customer relationships, Stripe account, bank account, and payment-provider settings.
Payment boundary
- Tash does not custody funds.
- Tash does not act as merchant of record.
- Tash does not store card details.
- Tash does not auto-charge clients.
- Tash does not control Stripe payout timing or guarantee bank settlement timing.
Operator responsibilities
- Connect and maintain the correct Stripe account or supported payment method.
- Create accurate invoice links, amounts, customer details, and payment instructions.
- Review manual EFT evidence against the operator's own bank records before marking it verified.
- Handle refunds, disputes, tax, accounting, and customer communication obligations for their own business.
Formal legal terms
Formal Terms of Service, Privacy Policy, Data Processing Addendum, acceptable-use rules, and any SLA must be reviewed and approved before broad enterprise contract use. Tash should not claim SOC 2, ISO 27001, external penetration-test completion, or guaranteed settlement timing until those controls and evidence exist.