Configuration, not bespoke software.
Every institution that has ever been quoted for a custom registry system has been quoted for the same six things. Here they are, and you own the configuration of each.
“Our documents are unusual.”
Document types you define
Describe each document — fields, types, validation, numbering format, and whether each field prints on the certificate or shows to a verifier. One schema generates the applicant form, the staff form and the printed output.
“Our process is specific to us.”
Workflows you configure
Ordered stages with an assignee, approver and service level each. Requests cannot skip a stage or move backwards without a recorded reason. Walk-in and online applications share one queue.
“Could a clerk use the registrar’s signature?”
Attributed authorisation
A personal credential per signing officer, lockout after repeated failures, an audit entry per authorisation, and processing held as a separate permission from issuing. Bulk-sign a reviewed queue in one action.
“Where does the money actually go?”
Payments and settlement
Paystack, Flutterwave and Remita, with the platform fee deducted at the gateway so your share never leaves your control. Cash is recorded in the same ledger. Edict never custodies tenant funds.
“Who did what, and can we prove it?”
Audit trail and access control
An append-only log across stage transitions, generation, authorisation, revocation, annulment, amendment, permission changes and verification queries — each with the actor and a timestamp.
“We already have a gazetted certificate design.”
Templates and printed output
Lay the document out in a zone editor, or upload the design you already use as a PDF, SVG, PNG, JPG or HTML file and map your fields onto it. Institutions with an existing design keep it.