Guides

Start here

What Tillstack isQuickstartAuthentication

Getting data in

How data gets inSync API referenceYour payment providerReconciliation

Building on it

Terminal integrationSales, returns, shiftsCatalog and stockInventory ledgerCatalog layout on devicesProduct picturesReportsWebhooksEmail and EngageRunning without our UI

Using the console

Operator portalMerchant guide

Reference

Sandbox, OpenAPI, PostmanErrors and limitsSecurity

Reference

Security

What protects your data, stated plainly so you can judge it.

  • Tenant isolation. Every query is filtered to the caller's place in the organisation tree by one rule applied in the data layer, not by each screen. A merchant sees only itself, a reseller its merchants, an operator its network. A resource outside your tree answers 404, the same as one that does not exist. Isolation across operators, resellers and merchants is covered by automated tests.
  • Signed writes. An Operator's writes need an HMAC-SHA256 signature over the exact body with a five-minute window, so captured requests cannot be replayed or altered. Webhooks we send you are signed the same way, with a per-endpoint secret.
  • Keys. Only a hash of an API key is stored. Signing secrets and webhook secrets are encrypted at rest and shown once. A key can only do what its scopes allow, and only a signed-in person can create keys.
  • No card data. Full card numbers are refused and never stored; masks are limited to the first 6 and last 4. Tillstack is not in the payment path.
  • Terminals hold a short-lived token bound to one terminal, one merchant and one branch, with only the abilities a till needs.
  • Passwords are hashed. Reset and invitation links are single-use, expire (an hour and a week), and are stored as hashes. Resetting or switching off a person ends all their sessions. Refresh-token reuse revokes the whole chain.
  • Outbound requests. Webhook URLs must be public https; the destination address is checked again at connect time, so a webhook cannot be aimed at an internal address, and redirects are not followed.
  • Pictures are re-encoded on upload, which strips location and other metadata. The storage bucket is private: pictures are served only through the API.
  • Sandbox tenants are separate from live: test keys never work live, and live keys never work in the sandbox.
  • Audit-minded behaviour. Stock is an append-only ledger. A sale is never silently overwritten. Every webhook delivery is logged.

To report a security concern, email the address in the site footer. Please give us a reasonable chance to fix things before disclosing.