How a VeriCam verification actually runs.
Eight controlled stages from request to public re-verification. Every transition is timestamped, every action is auditable, every decision is human-reviewed.
- 08:12EXTRACTSystem
- 08:14ROUTEOfficer · Etienne
- 08:14CONTACTUB Portal
- 08:31OPENUB Registrar
Built for the realities of Cameroon verification.
Most international verification platforms assume a digital-first registry that responds promptly to email. That assumption fails in Cameroon — and that gap is exactly what we built around. Cameroon verification is not a tooling problem; it is an on-the-ground problem.
When the inbox doesn't answer, we pick up the phone. When the phone doesn't answer, someone walks into the registrar's office. Every step is logged.
Many institutions lack staffed verification inboxes. We escalate across channels until a primary source responds.
Local officers visit institutions when digital channels exhaust. Every visit is documented with date, contact and outcome.
Bilingual workflows across English and French institutions. OCR and templates tuned for both linguistic traditions.
Where records pre-date digitisation, we coordinate physical-archive lookups rather than treating absence as a fail.
For credentials requiring Ministry of Higher Education or Secondary Education confirmation, we route requests appropriately.
Email, telephone, official portals and direct registrar contact — every attempt is captured in the case audit trail.
Almost no global verification provider can dispatch a local officer to a Cameroonian registrar. We can — and we do. That is the difference between “unable to verify” and a confirmed primary-source response.
Five stages. One audit trail. Each phase produces evidence.
Where most verification services jump straight from documents to outcome, VeriCam separates intake, extraction, primary-source confirmation, officer review and supervisor issuance — by code, not by policy.
Intake
Capture identity, credential, evidence and consent.
- Applicant identity & DOB
- Credential type + institution
- Document uploads
- Signed consent form
- Case ID CMR-YYYY-XXXXXX
- Encrypted document hashes
- Consent record
- Zod-validated payload
- Consent flag enforced before submit
- Files scanned at ingest
Extraction
Parse documents and surface anomalies — never decide outcomes.
- OCR + field extraction
- Risk-signal scoring
- Institution match
- Duplicate detection
- AIExtraction record
- Confidence per field
- FraudFlag rows
- Provider versioning
- Confidence required ≥ threshold
- Officer can override
Primary-source
Confirm or deny the credential at the issuing institution.
- Route to onboarded portal
- Or documented manual outreach
- Capture channel + person
- Store evidence
- InstitutionResponse
- Channel · contact · date
- Uploaded evidence
- Tracked outreach attempts
- Channel of record
- Suspected-fraud escalation
Review
Classify the outcome with explicit, written rationale.
- Compare evidence vs response
- Reconcile anomalies
- Write rationale
- Escalate if needed
- VerificationStep CLASSIFY_RESULT
- Rationale text
- Officer audit trail
- AI signals advisory only
- Officer cannot self-approve
- Supervisor required
Issuance
Approve and issue an immutable, re-verifiable report.
- Two-person sign-off
- Generate verification ID
- Emit QR + PDF
- Notify recipient
- Report payload snapshot
- Public verification ID
- Tamper-evident metadata
- Approval enforced in code
- Revoke / supersede supported
- Public lookup hides PII
Explainable extraction
Every parsed field is shown with confidence and detected anomalies. AI is a tool, never a decider.
Officer + supervisor sign-off
Two-person review is required by code. Reports cannot issue without a supervisor approval audit entry.
Primary-source confirmation
Verified outcomes always cite the issuing institution's response, channel and date — never document-only inference.
Operational visibility, not screenshots.
Every case moves through the same instrumented pipeline. Admins, officers and requesting organisations see exactly where each verification is — and why. Below is an operational snapshot of a live VeriCam workspace.
- ·KPIs by status. Open, manual review, awaiting institution, overdue.
- ·Real-time queue. Cases ordered by SLA and risk.
- ·Audit feed. Every action — login, decision, contact, report — recorded.
- ·Turnaround analytics. Officer load, response times, outcome ratios.
| Case | Status | Risk | SLA |
|---|---|---|---|
| CMR-2026-000142 | Primary-source | Med | 2d |
| CMR-2026-000139 | Manual review | High | Today |
| CMR-2026-000136 | Awaiting | Low | 3d |
| CMR-2026-000130 | Officer review | Low | 5d |
| CMR-2026-000123 | Issued | Low | — |
- 8:42ISSUESolange M.CMR-2026-000123 · VERIFIED
- 8:31RESPONDUB RegistrarConfirmed BSc CS 2022
- 8:14EXTRACTSystemCMR-2026-000142 · 4 fields, 1 signal
- 8:13ASSIGNSolange M.Etienne ← CMR-2026-000142
- 8:12CREATEHarvard AdmissionsCMR-2026-000142
AI-assisted intake. Always under human supervision.
Our extraction pipeline reads documents, scores risk signals and matches the issuing institution against our intelligence database. It is built to accelerate analysts, not to replace them. Every field is shown with confidence; every anomaly is explained.
- ·OCR + structured-field extraction across English and French Cameroonian templates.
- ·Risk signals: template mismatch, altered image, duplicate certificate numbers, inconsistent dates.
- ·Institution matching against an alias-aware reference database.
- ·Officers see exactly what the model believed — and why — before deciding.
The verification belongs to the institution. We carry the evidence.
Onboarded Cameroonian institutions receive cases directly in a secure registrar portal. For institutions not yet onboarded, our officers conduct documented outreach — and every channel, contact, response and piece of evidence is recorded on the case.
- ·Registrar portal: confirm, deny or request more information with a click.
- ·Manual outreach: registrar email, phone, in-person — channel, date and person captured.
- ·Suspected-fraud channel: escalates the case and flags it for compliance review.
- ·Every response stored on the case file and reflected in the final report.
- 08:13Assigned the case.
- 08:14Routed to onboarded institution.
- 08:16Posted attached evidence to portal.
- nowAwaiting registrar response.
- 08:14PORTAL · UB registrar (primary)
- 08:14EMAIL · [email protected]
- 08:31EMAIL opened by registrar
- 08:31Registrar opened the request.
- —Awaiting confirmation.
- —Evidence will be attached.
- —Audit entry recorded.
An investigation surface. Not a checkbox.
Officers work each case in a compliance-grade investigation view: applicant data, AI extraction, risk signals, institution responses, outreach log and audit trail — all in one frame, with the decision pane on the right. Outcomes require explicit rationale.
- ·Side-by-side comparison of applicant submission vs institution response.
- ·Officer rationale is required and stored verbatim in the report payload.
- ·Cases above risk threshold require supervisor escalation before classification.
- ·Officer cannot issue their own report — supervisor approval is enforced in code.
| Field | Submitted | Institution | Match |
|---|---|---|---|
| Applicant name | Marie Tchakounté | Marie Tchakounté | Match |
| DOB | 04 Mar 1996 | 04 Mar 1996 | Match |
| Programme | BSc Computer Science | BSc Computer Science | Match |
| Year | 2022 | 2022 | Match |
| Grade | Second Class Upper | Second Class Upper | Match |
| Certificate № | UB-BSC-2022-3811 | UB-BSC-2022-3811 | Match |
Audit-ready by code. Every action is traceable.
VeriCam writes an immutable AuditLog row for every action that touches a case: login, document upload, AI extraction, institution response, classification, supervisor approval, report issuance, revocation, re-verification download. Reports can be reconstructed years later.
- ·Actor identity. User id, role, IP, user agent.
- ·Timestamped diff. Before/after values for state transitions.
- ·Evidence linkage. Documents and responses referenced by id.
- ·Immutable. Never overwritten — superseded by new entries.
- 2026-05-03 09:14ISSUESolange MbargaSuper AdminReport RPT-CMR-2026-000142-A
- 2026-05-03 09:14APPROVESolange MbargaSuper AdminVerificationCase · Outcome VERIFIED
- 2026-05-03 08:58CLASSIFYEtienne NkomoOfficerRationale recorded · Outcome VERIFIED
- 2026-05-03 08:42RESPONDUB RegistrarInstitutionInstitutionResponse · VERIFIED via PORTAL
- 2026-05-03 08:31OPENUB RegistrarInstitutionReviewed evidence pack
- 2026-05-03 08:16UPLOADEtienne NkomoOfficerInstitutionEvidence · evidence-bundle.pdf
- 2026-05-03 08:14EXTRACTSystemAI PipelineAIExtraction · 8 fields · 1 risk signal
- 2026-05-03 08:13ASSIGNSolange MbargaSuper AdminOfficer = Etienne Nkomo
- 2026-05-03 08:12CREATEHarvard · Sarah WhitmanForeign requesterVerificationCase CMR-2026-000142
Five outcomes. No informal in-between states.
Every case resolves into one of five outcomes. Each has a precise institutional meaning and a recommended next action for the requesting organisation.
Primary-source confirmation of all material facts of the credential.
The institution explicitly confirmed the applicant's record matches what was submitted.
Accept the credential subject to your own admissions / employment policy.
Some facts confirmed by the institution, others could not be confirmed or were inconsistent.
The institution confirmed core enrolment but could not validate every claim (e.g. classification).
Review the case rationale and decide whether the verified facts are sufficient for your decision.
After documented good-faith outreach, no authoritative response was obtained.
This is not a finding of fraud — only that the issuing institution did not respond.
Request additional documentation directly from the applicant or escalate to your evaluator.
Primary source could not confirm the credential exists as presented.
The institution disowned the credential or its records contradict the document submitted.
Treat the credential as unconfirmed. Consider downstream policy (rejection, follow-up, audit).
Material indicators of fabrication, supported by institution disavowal or document evidence.
Reserved for cases where evidence rises to the level of an integrity concern.
Halt processing. Reference report rationale for follow-up and disclosure considerations.
A typical case, day by day.
Verification is not instant — and we will not pretend otherwise. Real institutional outreach takes real time. Here is what a routine Cameroonian degree verification looks like when nothing goes wrong.
Cases requiring field verification, ministry confirmation or archival lookup take longer. Every elapsed day is logged with the operational action that occurred.
- Day 1Case submitted
Applicant or institution submits credential documents through the secure intake portal. Consent is captured and logged.
- Day 1AI-assisted intake & risk analysis
Document fields are extracted with confidence scores. Fraud signals (F-01…F-08) are evaluated. Anomalies surface for officer attention.
- Day 2Primary-source outreach initiated
Verification request transmitted to the issuing institution via the registered channel (institution portal, registrar email or recognised intermediary).
- Day 3–5Institution response or escalation
When the institution responds, evidence is attached to the case file. When silent, the case escalates to telephone follow-up and, if needed, local officer visit.
- Day 5–7Officer review & supervisor sign-off
Verification officer drafts the case rationale citing every primary-source artefact. Supervisor independently reviews and approves before report issuance.
- Day 7Tamper-evident report issued
Report is generated with a verification ID, payload snapshot hash and public QR. The receiving institution can re-verify at any future date.
Cameroonian institutions in the loop. Free for accredited bodies.
Onboarded Cameroonian institutions receive verification requests in a secure inbox. Registrar staff can confirm or deny records with one click — and VeriCam handles the official report on their behalf. Free for accredited institutions during pilot rollout.
Verification-grade controls — not platform-marketing checkboxes.
The same controls that make a verification credible — least privilege, encrypted storage, audit retention, consent — are enforced in code, not promised in copy.
Uploads encrypted across the pipeline. Production deployments use a managed KMS.
Applicants explicitly authorise release to a named recipient; consent is logged and revocable.
Each report carries an immutable verification ID, payload snapshot and public QR.
Six roles with distinct permissions. Officers cannot self-issue reports.
Risk signals fire alerts. Suspected fraud halts issuance and flags compliance review.
AuditLog rows are never overwritten; full history is preserved across the case's lifetime.
Public verification pages reveal status and dates only — never documents or PII.
Two-person sign-off is enforced in code, not policy. Supervisors cannot self-approve their own decisions.
An institutional report. Re-verifiable forever.
The final report is a structured document with a verification ID, machine-checkable metadata and a public QR re-verification page. The payload snapshot is immutable: even if VeriCam's internal records change, the report remains verifiable against the snapshot.
- ·Verification ID, report number, public lookup ID.
- ·Outcome, confidence, method, channels and dates.
- ·Officer and supervisor of record disclosed on the report.
- ·Revocation and supersession flow if facts change.
- ·Public verification page never exposes uploaded documents.
Verification is not a paperwork step. It is a decision that affects a life.
Embassy adjudicators, university admissions officers and licensing bodies make consequential decisions on the basis of credential authenticity. When verification is inconclusive, those decisions carry hidden risk — for the institution and for the applicant.
Visa, admissions, employment and licensing decisions stall when credential authenticity cannot be reliably confirmed. Applicants wait. Institutions absorb operational cost.
Capable candidates are sometimes set aside because the receiving institution cannot reliably confirm a record from an issuing country it does not know how to reach.
VeriCam exists so that institutions and evaluators make credential decisions on the basis of primary-source evidence — not document inspection alone, not hope, not statistical probability.
“Verification failures delay visas, admissions, employment and licensing. VeriCam exists so that Cameroon credentials are no longer the reason a qualified applicant is held back.”
Bring evidence-based verification into your workflow.
Submit your first case, request a guided walkthrough with our verification team, or apply to onboard your institution. Most replies arrive within one business day.