REC-000318issuedIss. 01
Certified documents, issued in minutes and verified without a phone call.
Edict gives courts, universities, registries and professional bodies a branded workspace to take a request, collect the fee, route it for officer authorisation, and issue a sealed document that any third party can check from its code — in seconds, without contacting your office.
Institutions are onboarded with our team. No credit card, no self-serve setup, no obligation.
Kano State High Court
Certified True Copy
- Issued to
- Amina Yusuf
- Document no.
- DOC-000318
- Issued
- 4 August 2026
- Issuance
- 01 of REC-000318
Authorised signature
Chief Registrar
Scan to verify
REC-000318requested
You already know where the days go.
A request arrives at the counter. The fee is paid in cash and receipted by hand. The file moves between desks with no record of who held it or for how long. The registrar signs a stack at the end of the week. And when a bank in Lagos or an embassy in Abuja wants to know whether the certificate in front of them is real, they call your office — and someone has to go and look in a book.
| Today | With Edict |
|---|---|
| Applicant must attend in person | Applies on your own subdomain, uploads supporting documents, pays online |
| Cash at the counter, receipted by hand | Paystack, Flutterwave or Remita — settled to your account, receipted automatically |
| The file moves desk to desk, untracked | Every stage change is a recorded event with a named actor and a timestamp |
| The registrar signs a weekly stack | A named officer authorises with a personal PIN, one document or a reviewed batch |
| A verifier telephones your office | The verifier scans the code and has an answer in seconds, under your name |
| A forged certificate looks like a real one | The issued file carries a cryptographic hash; any alteration breaks it |
REC-000318authorised
One chain, from the counter to the verifier.
Nothing in this chain is bespoke software written for one institution. It is configuration — and you own the configuration.
Describe the document
You describe each document you issue — its name, numbering format, sections and fields — in a builder. Fields carry types, validation, and two flags that matter more than they look: whether the field prints on the certificate, and whether a verifier sees it. That single schema then generates the applicant's form, your staff's entry form and the printed document.
Route it your way
Each document type gets a workflow — ordered stages, each with its assignee, approver and service level. A request cannot skip a stage, and cannot move backwards without a recorded reason.
Take the fee at the request
Fees are set per document type and paid through Paystack, Flutterwave or Remita. Funds settle to your institution's own account at the gateway. Cash and walk-in payments are recorded in the same ledger, so the counter and the portal reconcile against one number.
Authorise with a named officer
Signing is a deliberate, attributable act. Each signing officer sets a personal PIN; entering it authorises a document or a reviewed batch. Repeated failed attempts lock that officer's signing capability. Every authorisation writes an audit entry naming the officer, the document and the moment — and the issued file carries a cryptographic hash of its exact bytes, so any later alteration is detectable.
REC-000318verified
Let the document prove itself.
Every issued document carries a code, printed as a QR. Anyone holding the document can check it — no account, no login, no call to your office — and gets one of five unambiguous answers.
- Valid
- Issued by the institution and unaltered since.
- Revoked
- Withdrawn by the issuer — and if a corrected version exists, it is named.
- Expired
- Genuine, but past the validity date the institution set.
- Not found
- No document with this code was ever issued.
- Invalid
- The code exists but the document does not stand.
Public verification is rate-limited per source and returns only what a verifier needs. Organisations that check at volume use the API instead.
Document verified
This document is authentic and has not been altered since issuance.
- Record number
- REC-000318
- Document number
- DOC-000318
- Title
- Certified True Copy
- Recipient
- Amina Yusuf
- Institution
- Kano State High Court
- Issued
- 4 August 2026
REC-000318Iss. 02supersedes Iss. 01
When a document is corrected, the old copy says so.
Amina's certificate had a misspelled name. The registry issued an amendment — a corrected document with a new issuance number that supersedes the original. Anyone still holding the old copy and scanning its code does not simply get a failure. They are told which document number replaced it, which is the answer they actually need when two versions are in circulation.
Verification can earn, not cost
Banks and employers verify your documents constantly, and today that costs your office time and earns nothing. You can register them, set your own price and bulk tiers, and keep all of it. They deal with your portal, under your branding.
Your fees never pass through us
The platform fee is deducted at the payment gateway using its native split facility. Your share goes straight to your institution's account and ours to ours. Edict never custodies tenant funds.
Document revoked
This document was withdrawn by the issuing institution.
- Record number
- REC-000318
- Document number
- DOC-000318
- Title
- Certified True Copy
- Recipient
- Amina Yusuf
- Institution
- Kano State High Court
- Issued
- 4 August 2026
Superseded by DOC-000412 — ask the holder for the current issuance.
Built for the document you issue.
The documents, the workflow and the vocabulary change by institution. The platform doesn't.
Courts
Certified True Copies, marriage and divorce certificates, letters of administration, probate.
Edict for courts →Universities & polytechnics
Transcripts, degree certificates, attestation letters, student status verification.
Edict for universities →Government registries
Birth and death certificates, business name registrations, change of name.
Edict for registries →Professional bodies
Membership certificates, practising licences, certificates of good standing.
Edict for professional bodies →We're early, and we'd rather you heard it from us.
Edict is a new platform. We are onboarding our first institutions now, and we are not going to decorate this page with logos we haven't earned or numbers we haven't measured.
What we can show you is the thing itself: a public verification endpoint you can test, an architecture we document in full, a security posture we will put in writing, and a team that will be in the room during your onboarding. Early institutions get direct access to the people building the platform and real influence over what gets built next.
Questions we get asked
Our institution’s data cannot sit in a shared database.
On the standard tiers your records are logically separated from every other institution’s, and that separation is enforced beneath the application rather than by application code that could be got wrong — a request without your institution’s context returns nothing at all. If logical separation is not acceptable to your procurement policy, the Enterprise tier provisions you on dedicated infrastructure in a region you choose, with the same controls still in force.
What happens when we issue a document in error?
Three options, all recorded. Revoke the document, and its code returns REVOKED. Annul the underlying record if the whole thing was invalid. Or issue an amendment: a corrected document with a new issuance number that supersedes the old one. In that case the old code returns REVOKED and names the document number that replaced it. Nothing is silently deleted.
Could a clerk use the registrar’s signature?
No. Authorisation requires the signing officer’s own PIN, held only by them. Repeated failed attempts lock that officer’s signing capability and write a failure entry to the audit log. Processing and authorising are separate permissions, so staff who prepare documents cannot issue them.
We already use an e-signature tool.
E-signature tools sign a file somebody else produced by hand. They do not take the request, collect the fee, enforce your approval order, generate the document from your own field schema, number it, or give a third party anywhere to check it a year later. If your problem is signing, a signature tool is enough. If your problem is issuance, it is not.
We don’t have the IT capacity to run this.
You do not run it. There is no server for your institution to maintain and no self-serve setup to get wrong. Our team configures your workspace with you — your document types, workflow, fee schedule, templates, staff accounts and their roles. You go live when you say you are ready.
How much is it?
Pricing depends on how many documents you issue, how many branches and staff accounts you have, your verification volume, and whether you require a dedicated database. Tell us those five numbers and we will send a written quote.
See it with your own documents.
Send us one document type you issue today — a Certified True Copy, a transcript, a licence — and we'll configure it and walk the whole chain with you, from an applicant's request to a verifier's scan.