Security and controls

Every action that moves money has a second pair of eyes.

Verified identity, dual control on the actions that matter, and a permission system the server enforces — not menu items an interface merely hides. Built for the institution that answers to a board and a regulator, and for the collector who just wants their own money to tie out.

Controls

Six controls, built in from day one.

01

Ghana Card verification

A member's identity is verified against the national ID at the point they are added, through the National Identification Authority (NIA) — not typed in and taken on trust.
02

Maker-checker dual control

A second person must approve a payout, a reversal, a forfeit or an overpayment resolution before it executes. No single member of staff can do all four alone.
03

Audit log, actor typed

Every sensitive action is logged against who did it and what kind of actor they were — staff, member or system — not just a timestamp and an ID.
04

Thirteen staff permissions

Thirteen distinct permissions, checked on the server for every request. Hiding a button in the interface is not a control; the platform enforces it where the request actually lands.
05

Organisation verification

An organisation moves through a verification lifecycle before it can start collecting from members — not straight from sign-up to live.
06

Collect-only agent role

A field agent can be scoped to collection alone — no access to payouts, reversals or the ledger — so the person on the round carries exactly the risk their job requires, and no more.

Dual control

Four actions no one person can take alone.

Payouts

Releasing a member's money needs a second approval before the instruction goes to the provider.

Reversals

Undoing a posted transaction needs a second approval — reversals just as much as the actions they undo.

Forfeits

Forfeiting a balance needs a second approval, with the reason recorded against it.

Overpayment resolutions

Deciding what happens to money paid in over the expected amount needs a second approval, not a unilateral call.

Custody

We hold the record, not the money.

SusuPaa is not a custodian. Your members’ savings never sit with us, and there is no SusuPaa account they pass through.

The money moves on licensed rails

Collections and payouts run through the mobile money networks and the licensed payment providers named on our homepage — MTN, Telecel and AirtelTigo, via Moolre, Hubtel, Paystack and LibertePay.

Funds rest in your name, not ours

What a provider holds between collection and settlement is held in your organisation’s own account. SusuPaa reads it and reconciles it against the ledger; it never takes possession of it.

What we actually hold is the ledger

Every cedi has a journal entry behind it, and that entry is the thing we are responsible for — its accuracy, its audit trail, and your ability to prove it to a board or a regulator.

Bring your board or your regulator questions.

See the controls running against your own book — thirty minutes, screen shared.