DCS Bonafide
DCS BonafideCredential Intelligence Platform
Sign inVerify a credential
AcademicEmploymentProfessionalHow it worksUniversitiesSchoolsEmployers & BGVPlatformsIntelligenceDevelopersTrust & SecurityCandidate RightsPlansSign in
Webhooks & Events

Follow verification events without constant polling.

Case · Source · Evidence · Review · Decision

Bonafide’s event model separates lifecycle events so external systems can react when evidence arrives, a source check completes, a review escalates or a final decision is recorded.

View developer platform →How Bonafide works
Event streamAsynchronous lifecycle
1
upload.committedOriginal evidence stored
accepted
2
source.check.completedOfficial route returned
verified
3
evidence.requestedTargeted candidate action
pending
4
decision.finalizedEvidence state locked
final
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.

◇

case.created

Case orchestration and analytics can begin.

✓

upload.committed

Document/quality/security processing can start from immutable evidence.

◎

document.classified

OCR/reference/source lanes can be routed.

↗

source.check.completed

Decision/review services receive the source result.

▦

evidence.requested → evidence.received

Communications and resume orchestration stay connected.

⌁

appeal.created → decision.finalized

Independent review and final receipt/report generation are traceable.

EVIDENCE MODEL

Events carry correlation; they do not erase state.

Consumers use the event stream to react, while authoritative case/document/decision resources remain queryable. Duplicate delivery is handled with idempotent processing.

  • Manual verification replies feed channel-trust/review
  • Reference version candidates feed internal reference review
  • External clients should verify webhook authenticity and handle retries
  • Production delivery contracts are versioned during engineering implementation
Event streamAsynchronous lifecycle
1
upload.committedOriginal evidence stored
accepted
2
source.check.completedOfficial route returned
verified
3
evidence.requestedTargeted candidate action
pending
4
decision.finalizedEvidence state locked
final
WORKFLOW

From input to defensible evidence.

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

01Event produced→
02Signed/delivered→
03Consumer verifies→
04Consumer handles idempotently→
05Authoritative resource remains queryable
DESIGNED FOR

One evidence model. Role-specific operations.

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

01

Enterprise platforms

Update applicant workflows asynchronously

02

BGV systems

Resume cases after source/evidence events

03

Data/ops teams

Connect analytics and downstream processes

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