Skip to content

REC-000318end to end

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. Here is the whole of it, in the order it happens.

APPLICANTSubmits a requestForm generated from your document type’s field schemaAPPLICANTPays the feePaystack, Flutterwave or Remita — or cash, recorded at the countercannot skip a stageYOUR STAFFRoutes through the workflowOrdered stages, each with an assignee, approver and service levelon approvalSIGNING OFFICERAuthorises with a personal PINRepeated failed attempts lock the signing capabilityEDICTIssues the documentNumbered, sealed, QR printed — integrity hash of the file storedANYONEVerifies from the codeVALID · REVOKED · EXPIRED · NOT FOUND · INVALID
Responsibility changes hands three times, and the document only becomes independently checkable at the last step. Brass marks the two points where authority is applied.

  1. REC-000318defined

    Describe the document, not the code

    You describe each document your institution issues — its name, numbering format, sections and fields — in a builder. Fields carry types, validation, placeholder and help text, and two flags that decide a great deal: whether the field prints on the certificate, and whether a verifier sees it. That is how a party's full name prints on a marriage certificate while the identity number behind it stays out of the verification response.

  2. REC-000318routed

    Route it the way your office already works

    Each document type gets a workflow: an ordered set of stages, each with an assignee, an approver and a service level. A request cannot skip a stage, and cannot move backwards without a recorded reason. Walk-in counters and online applications land in the same queue.

  3. REC-000318paid

    Take the fee at the point of request

    Fees are set per document type. Applicants pay through Paystack, Flutterwave or Remita and receive an automatic receipt. Funds settle to your institution's own account at the gateway — Edict never custodies tenant funds. Cash at the counter is recorded in the same ledger, so the counter and the portal reconcile against one number.

  4. REC-000318authorised

    Authorise with a named officer

    Signing is a deliberate, attributable act. Each signing officer sets a personal PIN; entering it authorises one document or a reviewed batch. 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.

  5. REC-000318issued

    Issue something that carries its own proof

    The generated PDF carries your authorised signature block, its document number, and a QR code holding its verification code. A cryptographic hash of the exact issued file is stored against the record, so any later alteration to that file is detectable.

  6. REC-000318verified

    Let a stranger check it without calling you

    Anyone holding the document can verify it and gets one of five unambiguous answers. If the document was later corrected and re-issued, the old code returns REVOKED and names the issuance that replaced it.

Why the schema is the whole trick.

Institutions are usually told their documents are too particular for off-the-shelf software. They are not — they are particular in their fields, and fields are data. Describe them once and every surface follows.

Document typefield schemadefined once, by youApplicant’s online formevery field marked requiredStaff entry formplus internal-only fieldsPrinted certificatefields flagged show_on_certificateVerification responsefields flagged show_on_verificationChange a field once and allfour surfaces follow — there isno second definition to drift.
The two flags on the last two surfaces are what let a certificate print a party's full name while the verification response a stranger sees withholds the identity number behind it.

Where the money goes.

The question a finance officer asks first, and the one most platforms answer badly.

Applicantpays the document feePayment gatewayPaystack, Flutterwaveor Remitasplit at sourceYour institutionsettles to your accountEdict feenegotiated percentageThere is no arrow from the applicant to Edict.A ledger entry is written per payment, and asettlement statement issued monthly.
The split happens inside the gateway using its native subaccount facility, so your share never enters an Edict-controlled account. Cash taken at the counter carries no platform fee at all.

What "sealed" means here, precisely.

We would rather be exact than let a word do more work than it should. Edict records anattributed authorisation — a named officer, gated by a personal PIN, written to an append-only audit log — and binds it to acryptographic hash of the exact issued file, so alteration after issuance is detectable.

Edict does not currently issue certificates from a certificate authority, or apply PAdES or PKI cryptographic signatures. If your document type requires a wet-ink signature by statute, the workflow supports a physical-signature stage inside the same tracked process, so you keep the audit trail and the verification channel without anyone pretending the law says something it doesn't.

See it with your documentHow verification works