Secure intake
Raw evidence is preserved before OCR/deskew/other processing derivatives.
Verify a Credential
Start a credential verification case.
Upload securely · Preserve originals · Request only what is needed
This public prototype demonstrates the intake experience. Production verification will create a tenant/case scope, preserve original bytes, classify the packet and route only the verification lanes supported by policy and available evidence.
Case intakeStart with what you already have
Accepted case inputOne document or a mixed packet
Original bytes are preserved before processing.
QualityReadable · Limited · Rescan
Only affected evidence is escalated.
Next stepSource · Review · Complete
The workflow follows evidence, not a forced score.
LIVE PROTOTYPE INTAKE
Try the front-end verification intake.
This demo keeps the v4.3 file interaction: it does not upload your file to a server, but shows the workflow engineers should connect to the production upload, evidence-store, document, quality and orchestration services.
- Original digital PDF preferred when digitally issued
- 300 DPI normal minimum target for scans; 400 DPI colour preferred
- Full page, straight and uncropped
- Targeted additional evidence only when needed
Drop your credential herePDF, PNG or JPG · one document or complete packet
Prototype only. This static demo does not upload your file to a server.
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.
Automatic document splitting
Page objects and credential groups are created from mixed packets.
Quality-aware processing
Readable-but-limited files can still proceed through OCR/source/logical lanes.
Progressive evidence
Backside, original PDF or clearer scan is requested only when that item can resolve a specific uncertainty.
Source routing
Automatic or manual official-channel verification is chosen from trusted registry data.
Human safety gate
Serious adverse findings require the configured human confirmation workflow.
EVIDENCE MODEL
What you may be asked for depends on the credential.
A digitally issued PDF should remain unchanged. A physical scan is normally clearer at 300–400 DPI. Fine reference/security regions use higher-quality internal reference masters; candidates are not asked to recreate those reference standards.
- Original digital file preserved unchanged when available
- 400 DPI colour preferred for physical applicant scans; 300 DPI normal minimum target
- Lower quality may proceed with reduced forensic confidence
- Reverse side is optional by default and requested only when useful
- Source unavailable can route to Bonafide Desk rather than an accusation
Case intakeStart with what you already have
Accepted case inputOne document or a mixed packet
Original bytes are preserved before processing.
QualityReadable · Limited · Rescan
Only affected evidence is escalated.
Next stepSource · Review · Complete
The workflow follows evidence, not a forced score.
WORKFLOW
From input to defensible evidence.
Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.
01Upload→
02Quality/classification→
03Verification lanes→
04Targeted evidence if needed→
05Result/review
DESIGNED FOR
One evidence model. Role-specific operations.
The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.
Individuals
Future self-service after pilot maturity
Institution users
Create a new candidate case
Enterprise systems
Equivalent flow via API
DECISION DISCIPLINE
Unknown ≠ fake.
Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.
DCS BONAFIDE · CREDENTIAL INTELLIGENCE PLATFORMEstablish what is bona fide.