Publish your NAV once. Distribute through as many networks as you want.
Your fund is entered once, its net asset value struck by you alone. Every brokerage, bank or Mobile Money operator you authorise places it under your mandate — and you can suspend that mandate in one move. Inopay does not manage, does not custody, does not place: we carry.
Portfolio
2 450 000 FCFA
Managing the fund is not the hard part. Distributing it is.
A well-managed UCI only gathers assets if it can be placed. Today the NAV travels by email and spreadsheet, every distributor re-keys it into its own system, and nobody can say who was authorised on which date. The day a placing agent values a unit it does not manage, that is no longer an operational nuisance: it is a control failure.
What you do from your workspace
Four actions, all reversible, all dated.
Publish the net asset value
- ▸By API from your portfolio system, by multi-fund CSV import, or by hand in the portal.
- ▸Re-publishing the same date corrects the value: the history stays readable, the correction is traced.
- ▸No rejected row is silently dropped — the import returns the line number of every failure.
- ▸With no eligible NAV, no order executes. Inopay never estimates a value on your behalf.
Authorise, suspend, terminate
- ▸A distributor only sees your fund if you have granted it an active mandate.
- ▸The placement retrocession is the one you agree with it, carried in the mandate.
- ▸A suspension takes effect immediately: the fund leaves its catalogue, its orders are refused.
- ▸A reason is required to suspend. It stays attached to the authorisation.
Three roles, three distinct places
The AMF-UMOA framework separates them. So does our data model — this is not a display convention.
You, the management company
You create the UCI, manage the portfolio and strike the NAV. The fund belongs to you in the system, not to the network that places it.
The depositary
Holds and controls the assets. Declared on the fund record and shown to investors. Inopay does not interface with it.
The distributor
Brokerage, bank or Mobile Money operator. Places the units under your mandate, owns the client relationship and the KYC.
Inopay
The rail between the three. Neither manager, nor depositary, nor placing agent — and we take nothing on your assets under management.
An accepted consequence: to distribute a fund on Inopay, its management company must be on Inopay. We refuse to let a placing agent enter the NAV of a fund it does not manage — that is precisely the flaw this model fixes.
Your flows, without your distributor's clients
You have a legitimate interest in tracking your flows: subscriptions, redemptions, net units, day by day. You do not need the identity of the subscribers — they are the distributor's clients, and both law and contract leave them there. Our database access rules enforce it: flows are returned to you aggregated, with no nominative column. This is not a screen setting; it is checked by automated tests on every release.
A proven infrastructure
Inopay is built for regulated partners. Technical and legal proofs come before the numbers.
Portable KYC Ed25519
Offline verification via /.well-known. Verified once, reusable everywhere — each institution keeps its own due-diligence decision.
SHA-256 audit ledger
Append-only chained. Every order traceable, immutable, exportable.
Compliance by design
Built for the AMF-UMOA framework — BRVM live today; BVMAC and GSE on the roadmap through licensed partners.
100% non-custodial
Inopay never holds funds or securities. PSP flow → partner SGI direct.
Your fund deserves more than one counter
Tell us which funds you manage and through which networks you want them placed. We answer with the price list, the technical scope, and what is not built yet.