Wallet and digital banking infrastructure for regulated institutions
If you hold a licence and need the rails, building them yourself is eighteen months and a permanent engineering team. FeePrime is that layer, ready to operate.
A clear boundary first: FeePrime is infrastructure, not a licence and not a regulator-facing shield. You operate it under your own authorisation, and your compliance obligations remain entirely yours. What we remove is the engineering, not the responsibility.
Issue and distribute
Define yourself as a currency issuer and issue a wallet currency your customers hold and transfer. A user-facing code can be pegged to a real ISO currency that governs formatting and decimals, so an FCFA-denominated product behaves correctly everywhere without duplicating your money logic.
Appoint distributors — agents, branches, partners — each with their own operations, limits and reporting, so cash-in and cash-out reach places your branches do not.
Control who can do what, and how much
Tiers set what a customer may do at each level of verification. KYC records carry the evidence behind the decision. Transaction limits apply per tier, so raising a customer’s ceiling is a deliberate, recorded act rather than a configuration change nobody can trace.
Vaults and scheduled vault operations manage the float behind the system.
A ledger that keeps the evidence
Every movement is a stored entry, not a number recomputed at read time. Balances are a checkpoint plus the movements since it, so a balance is exact in real time and remains explainable afterwards.
This matters most on the day it goes wrong. A wrong figure you can trace to the movements that produced it is a support ticket. A wrong figure with no arithmetic behind it is an investigation with nothing to investigate.
Reconciliation brings external activity — gateways, partner accounts — into a queue your team clears, rather than a spreadsheet somebody maintains privately.
Built to be audited
The controls the rest of FeePrime uses are exactly what a supervised institution needs anyway:
- Nothing is destroyed — records are archived, never deleted.
- Every change carries its author, its timestamp and its previous value.
- Two-person approval can be required per module, so making a change and confirming it are different people.
- Scoped API keys with their own permissions and optional IP restriction, so an integration holds exactly the rights it needs.
Integrate with what you already run
A REST data API covers reads and writes across the platform, so your core banking system, your channels and your reporting stack talk to it directly rather than through exports.
Next step: we will walk your team through the ledger model and the issuer, distributor and tier structure against your own product design, and be straightforward about what is configuration and what is genuine development.