Start here
What Tillstack is
Tillstack is the back office for payment terminals. A payment company (an operator) already has merchants and terminals out in the field. Tillstack gives those merchants inventory, sales, receipts, reports and reconciliation, and gives the operator one place to see how its whole network is doing. It is API-first: everything the web console does, you can do with HTTP calls, so you can use our screens, your own, or none at all.
It does not move money. Payments keep flowing through your acquirer or payment provider exactly as they do today. Tillstack records what was sold, checks it against what the bank approved, and shows you the difference. Why that matters.
Who is who#
Platform -> Operator -> Reseller (optional) -> Merchant -> Branch -> Terminal| What it is | How it talks to Tillstack | |
|---|---|---|
| Operator | The payment company that owns the relationship with merchants and terminals. | A server-side API key, with signed writes. Or its staff in the console. |
| Reseller | Optional. Sells on to merchants under its own brand. | Console, or API key. |
| Merchant | The shop. Owns a catalog, staff, branches and stock. | Its staff in the console, or an API key. |
| Branch | A physical location and its own stock room. | Belongs to a merchant. |
| Terminal | A device with a TID, assigned to a merchant's branch. | Never holds a long-lived secret: your backend mints it a short session token. |
Everyone sees only their own subtree. A merchant sees its own data, a reseller sees all its merchants, an operator sees everything beneath it, and one tenant can never read another's. This is enforced on every query, not just at the screens, and covered by tests.
Three ideas to know#
1. Money is whole kobo. 150000 means ₦1,500.00. There are no decimals and no floats anywhere in the API. Prices are VAT-inclusive.
2. Your ids are the keys. When you send us a merchant, branch or terminal you give it your id (externalId). Sending the same thing twice changes nothing, so retries are always safe.
3. Everything is idempotent. Sales carry a client-generated id, so a terminal that was offline can replay hours later and never double-counts stock. Webhooks we send you carry an event id, so you can ignore a repeat.
Ways to use it#
| You are... | You will probably... |
|---|---|
| An Operator with its own systems | Sync your merchants, branches and terminals, send transactions, and give merchants the console or white-label it. |
| An Operator that wants a fast start | Upload CSVs, use the console to add merchants by hand (Operator portal). |
| A developer building a terminal app | Mint a session, sync the catalog, record sales. |
| A merchant | Sign in to the console: Merchant guide. |
| Building your own UI | Use the API reference and the guides: running without our UI. |
Next: the quickstart runs a complete flow in about ten minutes.