API-first · White-label · Never in your payment path

The back office for your payment terminals. Your payments stay yours.

Inventory, sales and reconciliation for every merchant on your terminals. Keep your own payment provider, your own merchants and your own brand, and see every gap between a sale and the bank on the day it happens.

Sandbox included Open HTTP API No card numbers stored

POST /v1/terminal/sales
# the terminal sells; the bank approves; we record both
curl -X POST $BASE/v1/terminal/sales \
  -H "Authorization: Bearer $SESSION" \
  -d '{
  "saleId": "7f3c…",
  "lines":  [{ "variantId": "…", "quantity": 2,
              "unitPriceKobo": 500000 }],
  "tenders": [{ "type": "Card", "amountKobo": 1000000,
               "rrn": "230715123456", "tid": "2035AB01" }]
}'

You are in control

Use your payment provider. We never touch the money.

Most POS back offices come bundled with their own payments, so leaving means replacing everything. Tillstack is built the other way round: payments stay with your acquirer, and the business side of every sale lives here.

Your payment provider

Terminals pay through the acquirer you already use. We never hold, move or settle funds, so there is no Tillstack balance to trust. Change provider and the back office does not change.

Your data, your ids

Everything is keyed to your own ids, loaded and read back over an open API. Sync merchants in, export sales out. Nothing about it is trapped.

Your brand and domain

Each reseller and merchant can carry its own name, logo, colour and web address. On receipts and in email, the business is the brand, not us.

Bundled POS and paymentsTillstack
Who settles the moneyThe vendor's payment railsYour acquirer, unchanged
Switching providerReplace the back office tooChange where payment records come from
Card dataOften inside the product's scopeNever received. Masked numbers only; full numbers refused
Your merchants and terminalsLive in the vendor's systemMirrored by your own ids; sync them in and out
Checking the bankWhatever the vendor's report showsReconciled against your acquirer's records
IntegrationTheir SDK, their waySigned HTTP API, sandbox, webhooks, OpenAPI and Postman

The trade is simple: Tillstack does not take payments, so you keep a payment provider. If you already have one, you lose nothing. How it connects.

How it works

Data in, sales through, differences out

Your merchants and terminals already exist. Tillstack takes them from your systems, lets terminals sell against them, checks each sale against what the bank approved, and tells everyone what they need to know.

Your systemsmerchants · branches · terminalsSync API · events · CSV Terminalscatalog · sales · returns · shiftsshort session token, offline-safe Your payment providerapproved paymentsRRN · STAN · TID · amount Tillstack catalog and stock ledgersales and receiptsreconciliationreports by rolewhite-label consolenever in the payment path Webhooks outsale.created · stock.lowsigned, retried, logged Merchant consolecatalog · stock · staff · receiptson their own brand and domain Network viewevery merchant and terminalidle devices, exceptions
  1. Bring your network in. Sync merchants, branches and terminals from your systems, upload a CSV, or add a merchant by hand. Everything is keyed to your ids, so running it twice changes nothing.
  2. Terminals sell. Your terminal app asks your server for a short session, syncs a compact catalog, and records sales. A sale made offline can replay hours later without double-counting stock.
  3. We check it against the bank. Send what your acquirer approved. Each card sale is matched on terminal and reference number, and money taken with no sale, or a sale with no payment, shows up as an exception.
  4. Everyone sees their part. Merchants run their shop, you watch the whole network, and your other systems hear about it through signed webhooks.

How we ingest data

Four doors, one engine

They all follow the same rules, so you can mix them: start with a spreadsheet, move to the API when you are ready.

Sync API

Batches of up to 500 merchants, branches and terminals. Per-item results, so one bad row never fails the rest.

Event webhooks

Tell us when something changes in your system. Duplicates and out-of-order events are handled for you.

CSV import

Upload a file, get a job with a message per bad line. Re-uploading is safe. Merchants can import their own catalogs too.

The console

Add a merchant with its owner, branch and terminals in a guided flow, and invite people by email.

Safe by design: your id is the key, the same data twice is unchanged, and a newer record is never overwritten by an older event. Read how.

What you get

Everything a shop needs, and everything you need to see the shops

Inventory you can explain

An append-only stock ledger per branch, transfers, stock counts with clear differences, and weighted-average valuation. A paid sale is never refused for an empty shelf.

Sales and receipts

Idempotent sales, returns, shifts and cash-up. Print-ready receipts carry the business's own name, address and tax ID.

Reconciliation

Card and transfer sales matched to the bank's approvals. Money without a sale, sales without money and amount mismatches, flagged the same day.

Reports by role

Sales by day, hour, product or cashier; end-of-day; stock value. PTSPs get a network view that makes idle terminals as visible as busy ones.

Built for the till

A compact catalog feed, product pictures resized on request, and category order and favourites the merchant controls, with a preview of the device.

Roles that mean something

Owner, manager, stockkeeper and cashier see different menus, and the API enforces it. Switch someone off and their sessions end at once.

White-label, your domain

Resellers and merchants can use their own name, logo, colour and web address, verified automatically.

Webhooks out

Sales, returns, low stock and unmatched payments, signed, retried with backoff, and logged. Point them at your own systems or at Engage.

Email that is theirs

Invitations that let people choose their own password, resets, and an optional end-of-day summary, all branded as the business.

Who it is for

One platform, three ways in

PTSPs and resellers

Give merchants a real back office on your brand, see how every terminal is doing, and keep the payment relationship exactly where it is.

PTSP guide

Merchants

Set up your catalog (or import it), manage staff and branches, count stock, and see your day, from a phone or a desk.

Merchant guide

Developers

No UI required. Everything the console does is an API call, documented and generated from the running API.

Running without our UI

Security, plainly

Built so one tenant can never see another

Isolation in the data layer

Every query is filtered to the caller's place in the organisation tree by one rule, not by each screen. Cross-tenant access is covered by automated tests.

Signed writes, scoped keys

Writes are HMAC-signed with a five-minute window. Keys carry only the scopes they need, and only a signed-in person can create one.

No card data

Full card numbers are refused and never stored. Terminals hold a short-lived token tied to one device, merchant and branch.

Everything we do, in detail

Questions

Straight answers

Do you process payments?

No. Payments go through your acquirer or payment provider as they do today. Tillstack records what was sold and checks it against the payment records you send us. We never hold or move funds.

Which payment providers does it work with?

Any. We take payment records (terminal, merchant, reference number, trace number, amount, response code, time), not rails. If your provider can send a webhook or an export, a small adapter you own maps it to our format. The mapping.

Do we have to use your screens?

No. Everything the console does is an API call, so you can build your own, or run entirely from scripts. Running without our UI.

How do we get our existing merchants and terminals in?

Sync them over the API, send events as things change, upload a CSV, or add them by hand. Everything is keyed to your own ids and safe to repeat.

What about terminals that are offline?

Each sale carries an id made on the device. Replaying a queued sale later returns the same receipt and moves stock once, and a sale that can never succeed is kept for a manager to review instead of being retried forever.

Can merchants use their own name and domain?

Yes. Resellers and merchants can set a brand name, logo, colour and a custom domain, and the console, receipts and emails follow it.

Is there a sandbox?

Yes. A sandbox organisation gives you test API keys, test-mode webhooks and the same API, isolated from live data. The quickstart runs a full sale in it.

What does it cost?

Talk to us at hello@tillstack.app.

See it with your own terminals

Start in the sandbox in ten minutes, or tell us about your network and we will help you plan the move.