Harobed

Security

Security is a set of controls, not a promise.

Money platforms fail in predictable ways: a duplicated webhook, an edited balance, an approval by the wrong person, a leaked document. Harobed is built around those failure modes.

Controls

What protects the money.

Each control is enforced in the API and recorded, not left to a policy document or a member of staff’s memory.

A ledger that refuses to be wrong

Every financial action posts a balanced journal entry. Entries are append-only; a correction is a reversing entry linked to the original, never an edit.

A tamper-evident audit trail

Decisions and postings are written to a hash-chained log with the actor, time and reason. Removing or changing a record breaks the chain and is detectable.

Maker-checker

Sensitive actions need a second authorised person: configuration changes, manual journals, large withdrawals, waivers, distributions and role changes.

Step-up authentication

A signed-in session is not enough to move money. Money and identity changes re-verify the transaction PIN, with attempt limits and a lockout.

Name-matched payouts

Payouts leave only to a verified bank account whose name matches the member’s KYC record. New beneficiary accounts can carry a cooling-off period.

Idempotency and reconciliation

Every payment, posting and webhook carries a unique reference. Duplicates are ignored, and daily reconciliation compares our ledger with the partner’s settlement report.

Role-based access

Staff see only what their role needs. Operations, credit, accounting and audit are separate permissions, and every access decision is recorded.

Private documents

KYC documents live in private object storage. Reviewers receive short-lived links; the bucket is not public, and document keys are scoped to the member.

Member protection

The member is part of the control.

A platform cannot protect a member who is not involved. Harobed gives members the evidence and the friction to notice a problem early.

  • A receipt for every contribution, withdrawal and repayment.
  • Statements built from the ledger, not a separate reporting copy.
  • A transaction PIN on money and identity changes, separate from the app lock.
  • Alerts and a delivery record for notices that need attention.
  • A visible status for every loan application, guarantee and withdrawal.
  • A named route to the team when a transaction does not look right.

Data protection

Collect less. Keep it only as long as needed.

Identity data is collected for KYC and payment compliance. Transaction data is kept for the ledger, statements and audit. Access is limited by role, and documents are served through short-lived links.

The privacy notice sets out the data we collect, why, who processes it and the rights available to a member under the Nigeria Data Protection Act.

Read the privacy notice

Honesty

No certification theatre.

We do not display badges we have not earned. If your cooperative needs a specific assurance, ask and we will tell you exactly what has been completed and what has not.

What we will not claim

  • That any system is perfectly secure.
  • That a certification exists before it is issued.
  • That a provider’s licence is our own.
  • That a member’s money is risk-free.

Security questions and reports go to support@harobed.com.ng.

Ask the awkward security question.

If your committee, auditor or IT reviewer needs a specific answer about controls, data handling or payment flows, ask us directly.