Enterprise

At volume,
the books are the product.

Past a certain size the interesting question is no longer whether the shop works. It is whether the money can be explained, reconciled and audited — every day, without anyone being asked to take it on trust.

Start free Talk to us

Limits: Set with you, per store
Reconciliation: Nightly, platform-wide
Terms: Negotiated, not listed

Where it goes wrong

Scale breaks the things nobody was watching.

The failures that matter at volume are not outages. They are quiet disagreements between two numbers that were supposed to be the same one.

The balance and the history stop agreeing

A stored balance drifts a few kobo from the sum of its own transactions, nobody notices for months, and by the time anyone does there is no way to say when it started.

A retry pays somebody twice

Payment providers resend confirmations as a matter of course. A system that treats the second delivery as a second event is a system that has already lost money.

Nobody can say who changed what

At small scale you remember. At volume you need a record, and “we think it was support” is not one.

Watch it prove itself

The nightly run, in full.

Every wallet on the platform, re-added from its first row and compared against its stored balance. Run it and watch it check itself — including what happens on the night it finds a discrepancy.

Scheduled nightly · 03:00

One kobo of disagreement fails the run. Not a warning, not a rounded figure — a non-zero exit code, every night, across every wallet on the platform.

A faithful model of the reconciliation command’s real output and its real behaviour: any drift fails the run.

What you get

What changes at volume.

Six things that are either negotiated with you or simply true of the platform.

Limits set per store: Storage, store count and assistant allowance can each be raised for your account specifically, above whatever the published plans say.
Commercial terms, agreed: Commission and settlement are a conversation at this size, which is exactly why the Business tier carries no price tag on the pricing page.
An append-only money record: No update path and no delete path on a ledger row. A correction is a new, opposing entry, so the original mistake stays readable forever.
Reconciliation that fails loudly: A scheduled job re-adds every row for every wallet nightly and exits non-zero on a single kobo of disagreement. Drift is caught by the platform, not by an accountant.
Audit logs and two-factor access: Administrative actions are recorded, and accounts can require a second factor. Both matter more the more people touch the system.
Verification handled properly: Identity documents are stored in a separate private bucket, excluded from every media listing, and reachable only through short-lived signed links.