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

Using the console

Operator portal

Everything an operator (or reseller, or platform staff acting for an operator) does by hand in the console. The same data can still arrive through the sync API / CSV import; these screens and that API write the same tables.

Who can do what#

Action Operator admin Reseller admin Merchant owner/admin Platform staff
Add a merchant (POST /v1/organizations, type Merchant, optional mid) yes yes (under itself) no yes, choosing the operator
Edit / suspend an organization (PUT /v1/organizations/{id}) its network its network no any
List / add people (GET/POST /v1/organizations/{id}/users) yes yes its own yes
Branches (POST/PUT /v1/merchants/{id}/branches, scope branches:write) yes yes its own yes
Register, edit, assign terminals (/v1/terminals, scope terminals:write) yes no read only yes, choosing the operator
Network reports (GET /v1/reports/network) yes yes no (own reports) yes
Platform report (GET /v1/reports/platform) no no no yes

Tenancy fences all of it: a merchant, branch or terminal outside the caller's subtree is a plain 404, and a terminal can only be assigned to a merchant of its own operator.

Console screens#

  • Merchants → Add merchant is a wizard: Business (name, slug, MID; platform staff pick the operator) → Owner (generated temporary password, shown once) → first Branch → Terminals (pick from stock and/or paste new TIDs) → Review. Partial failures are reported, not hidden: the merchant is created first, then each later step is attempted and any that failed are listed.
  • Merchants → a merchant has tabs for Branches, Terminals, People and Details (rename, MID, suspend/reactivate), plus "Open their console".
  • Terminals lists every device: TID, model/serial, merchant and branch, last sale, status, with an "Idle" flag for an assigned, active terminal with no sale in 7 days. Register one TID or many at once; edit to change status or move it between merchants/branches, or back into stock.
  • Locations (merchant users): their branches (owner/admin can add and edit) and terminals (read only).

Reports#

Merchant-level, under Reports in the console: Sales (by day, hour, weekday, month, branch, terminal, cashier, product, payment type; chart + table + CSV), End of day (Z report), Stock valuation, Stock movements, and Oversells / refused submissions (acknowledge or mark handled). Operator/reseller: Network performance (merchants, terminals or days; idle merchants and terminals called out; CSV). Back office: Reports (volume, merchants, terminals, daily volume, top operators, webhook delivery health, custom-domain status). All times are Nigerian time (WAT, UTC+1). New sales groupings Hour, Weekday and Month are available on GET /v1/merchants/{id}/reports/sales.