Skip to content

Security

Built so that money does not get lost.

This is what the platform commits to. The technical detail is handed to our customers, on request, under a confidentiality agreement.

  • 01

    A doubt is never a failure.

  • 02

    An error that blocks beats an error that creates money.

  • 03

    Nothing is erased, everything is corrected.

Our rules

  • Least privilege

    Every account, service and role has only the rights it needs, and not one more.

  • Defense in depth

    No protection rests on a single layer: if one gives way, the others hold.

  • Fail closed

    When in doubt or on error, the action is refused. An error that blocks a transaction beats an error that creates or destroys money.

  • Safe by default

    The safest setting is the default one. Weakening it takes an explicit choice, and it is visible.

  • No trust in input

    Everything from a merchant, a browser or an operator is checked before it is used.

  • Everything is traced

    Every sensitive action is attributed to a person and kept in a journal that nobody can change.

The money

Every franc has an entry, and entries are never erased.

The heart of the platform is a double-entry ledger. What matters to you is its guarantees.

  • Every movement is balanced

    Every operation is written so that the total cancels out. An unbalanced journal is refused.

  • Nothing is erased

    Entries are never modified or deleted: a mistake is corrected by a reversing entry, and the history stays complete.

  • Never twice

    A request is never sent twice to an operator. A payment of uncertain outcome goes through a check, then a human: never an automatic replay.

  • Sending again does not double

    Sending the same order twice never creates two payments.

A collection, seen from the ledger

10,000 KES collected, 1.5% fee. What one receives, another gives.

DebitCredit
Funds at the operator10 000—
Merchant balance—9 850
Platform fee—150
Total10 00010 000
Balanced10 000 − 10 000 = 0

Your access

Your integration, your teams and your withdrawals follow strict rules.

  • Authenticated requests

    Every request from your server is authenticated, and your secret never travels. You can restrict access to your addresses.

  • Separate environments

    The sandbox and production share nothing: no keys, no data.

  • A confirmation to act on money

    A withdrawal, a new key or a sensitive change asks for an extra confirmation, bound to the exact action.

  • Clear roles and rights

    Everyone sees and does only what their role allows. A suspended account is cut at once.

Operations

A platform that holds, and watches itself.

Reliability is part of security.

  • A doubt is never a failure

    When an operator does not answer, the transaction stays pending and is resolved by a check. A payment that may have happened is never declared lost.

  • Every country is isolated

    A failing operator does not stop the others.

  • Tested at every change

    Nothing ships without passing a battery of automatic checks, including security tests.

  • Written rules

    The security requirements are written down, and every new function that touches money is analysed before it ships.

The detailed security file

For our serious customers and candidates, we hand over, under a confidentiality agreement, a technical file: architecture, protections, tests, recovery plans. Ask for it with your access request.

Ask it before you sign: we answer in writing.