Skip to the content

For partners

How Jeimba handles money and records.

For payment providers, banks, funders, accountants and resellers. This is what the product does today, described plainly. Where something is not built yet, we say so.

Payments are confirmed by the provider.

  • A payment counts only after the provider (Paystack or Hubtel) confirms it through its own check. What a customer's browser or phone says is never believed.
  • The amount and currency must match exactly. A payment for a different amount is refused.
  • Callbacks that a provider does not sign are never trusted. They only prompt Jeimba to ask the provider directly.
  • Each business uses its own provider account, so money goes to the business's account, not through ours. Their keys are stored encrypted and are never shown again.
  • A mobile money payment that Jeimba started can be used for one sale only, for the exact amount and at the right branch. Otherwise the sale is refused.
  • Plan fees are charged through Jeimba's own provider account, and automatic renewal keeps the price the owner agreed to until they accept a new one.

Records that cannot be quietly changed.

  • Sales, payments, stock movements, the customer ledger and the accounting journal are append-only. A mistake is fixed with a refund, void or reversal that shows in the history.
  • Sealed sales: each sale is fingerprinted and chained to the one before. Anyone with a receipt link can check whether the record is genuine, altered or not yet sealed.
  • Every management action is written to an activity log with who, what and when. The log cannot be edited.
  • Accounts are double-entry and every entry must balance before it is accepted.
  • Reports and the books are worked out from the records each time; nothing is a typed-over total.

Access is limited, and visible.

  • Each business is separate. Staff see only their own business, and can be limited to one branch.
  • Passwords and PINs are stored as one-way hashes. API keys are shown once and only a hash is kept.
  • The Jeimba team's own accounts need an authenticator-app code on every sign-in.
  • The Jeimba team sees counts and totals, not a business's customers or sale lines. To help an owner, support can open the business in a read-only view with a stated reason. The owner is notified and it appears in their own activity log.
  • Customer consent is recorded with its wording and date. A customer's data can be exported, and a customer can be forgotten.

Working with us.

Payment providers and banks

Jeimba connects to Paystack and Hubtel today, for payments and text messages. If you offer an API a retail till could use, we would like to hear from you.

Funders

Jeimba is early. We will tell you what is built, what is not, and how it is used, with real figures when there are real figures.

Accountants and resellers

Your clients can give you a login (for example the Auditor or Finance role) to see their books and reports, and every report downloads as a spreadsheet. A dedicated reseller portal is not built yet; if you would set up many businesses, tell us what you would need.