AcademicEmploymentProfessionalHow it worksUniversitiesSchoolsEmployers & BGVPlatformsIntelligenceDevelopersTrust & SecurityCandidate RightsPlansSign in
How DCS Bonafide Works

From messy packet to evidence-backed state.

Upload · Structure · Verify · Review · Preserve

The platform preserves the original evidence, turns mixed packets into structured credentials, runs the verification lanes applicable to each credential, escalates only when necessary and records every material step.

Verification pipelineMinimum evidence first
PreserveImmutable original
StructurePages, documents, identity
VerifySource + intelligence + forensic lanes
ResolveEvidence request or human review
RecordResult + audit evidence
Source-firstAuthoritative routes outrank appearanceMinimum evidenceEscalate only what can resolve uncertaintyHuman gateSerious adverse outcomes require reviewAuditableMaterial actions preserve lineage
WHAT BONAFIDE DOES

Purpose-built verification capabilities.

Each capability is a visible part of the verification workflow—not a hidden AI score.

Upload edge

Authenticate tenant/case, stream bytes, detect content type, hash while streaming, quarantine scan and commit immutable evidence.

Document graph

Split pages, group documents, pair front/back pages and classify credential types.

Quality/OCR/identity

Assess DPI/blur/skew/crop/glare, extract structured fields and resolve names/identifiers with explainable identity states.

Pillar lanes

Academic, Employment or Professional verification uses the relevant source/regulatory/forensic/chronology logic.

Decision & human review

Separate confidence dimensions feed policy. Potential serious discrepancies cannot bypass the human gate.

Evidence record

Reports, source snapshots, communications, review actions and optional receipts preserve a reproducible audit trail.

EVIDENCE MODEL

The minimum evidence principle controls escalation.

A blurry page triggers a rescan of that page. A possible local edit may trigger the original PDF/backside. A new academic version creates a profile/source-review task. A missing automatic source launches Bonafide Desk. The whole packet is not re-requested unnecessarily.

  • Interactive API/self-service: high priority
  • Evidence resume/rescan: medium-high priority
  • Manual Bonafide Desk: customer/route SLA
  • Enterprise bulk: throughput optimized without starving interactive work
  • Reference/data acquisition: background workers separate from production verification
Verification pipelineMinimum evidence first
PreserveImmutable original
StructurePages, documents, identity
VerifySource + intelligence + forensic lanes
ResolveEvidence request or human review
RecordResult + audit evidence
WORKFLOW

From input to defensible evidence.

Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.

01Receive
02Structure
03Run applicable lanes
04Escalate targeted gaps
05Human-confirm/preserve
DESIGNED FOR

One evidence model. Role-specific operations.

The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.

01

Reviewers

Understand case state and next action

02

Candidates

Know exactly what additional evidence is requested

03

Engineers

Implement bounded services around the same lifecycle

DECISION DISCIPLINE

Unknown fake.

Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.

Authority VerifiedAuthoritative source evidence is consistent.
Highly ConsistentStrong supporting evidence; independent source not complete.
Evidence RequiredA targeted item can likely resolve the case.
Unable to DetermineEvidence remains insufficient; no fraud conclusion.
DCS BONAFIDE · CREDENTIAL INTELLIGENCE PLATFORM

Establish what is bona fide.
Preserve the evidence.

Verify a credentialOpen portal