BonaFideDocument, credential & identity verification
Every credential has a source. BonaFide is built to ask it, and keep the evidence.
In testing
- Universities & schools
- Employers & background checks
- Platforms
- Verification pillars: academic, employment, professional
- 3
- Steps from upload to an evidence-backed state
- 6
- Review required before any serious adverse finding
- Human
- Black-box fraud scores. Every state names its evidence
- 0
Verification decisions affect people. They need evidence, not a score.
A degree, an employment record or a professional licence decides whether someone gets a place, a job or a licence. Most checks still end in a screenshot, a phone call nobody recorded, or a fraud score nobody can explain.
BonaFide establishes whether credentials and claims are bona fide by combining issuer intelligence, official-source verification, document intelligence, regulatory history, progressive evidence and human review, and it keeps the evidence for every step.
Unknown is not fake. Uncertain cases go to manual verification, never to an automatic accusation.
From a messy packet to an evidence-backed state.
BonaFide follows the strongest available route and resumes only the affected lane when new evidence arrives.
- 01Preserve
The original is kept
Uploads are hashed while streaming, scanned and stored immutably. Processing copies stay separate.
- 02Structure
Pages become credentials
Pages are split, grouped, paired front-to-back and classified by credential type.
- 03Resolve
Know the issuer
Issuer, employer and regulator records with official domains, contacts and historical status.
- 04Verify
Run the right lanes
Source, regulatory, forensic and chronology checks, chosen per credential.
- 05Review
Ask only what resolves it
A targeted evidence request, or official-channel review through BonaFide Desk.
- 06Record
Preserve the evidence
Result, source snapshots, reviewer actions and an optional signed receipt.
Evidence-backed states, not a black-box score.
Customers see what is independently verified, what is strongly consistent, what needs more evidence and what cannot be determined.
- Authority
Authority VerifiedAn official source returned consistent evidence- Crypto
Cryptographically VerifiedIssuer signature, QR or credential proof validated- Strong
Highly ConsistentStrong support; independent source not complete- Gap
Evidence RequiredOne targeted item can resolve the gap- Manual
Manual VerificationOfficial-channel review is underway- Open
Unable to DetermineEvidence is insufficient; no fraud conclusion
Built for decisions that affect people.
Immutable originals
Raw uploads are preserved; processing derivatives remain separate objects.
Source outranks appearance
Authoritative source or cryptographic evidence outweighs how a document looks.
Unknown is not fake
New, legacy or source-unavailable credentials route to uncertainty and manual review.
Human review gate
AI can flag a potential discrepancy but cannot confirm a final material one on its own.
Candidate rights
Consent, correction, dispute, appeal and retention are part of the case lifecycle.
Auditable evidence
Source lookups, model and policy versions, reviewer actions and decisions stay traceable.
Different credentials need different proof.
The route changes by credential type; the decision language and evidence model stay the same.
- Pillar 01
Academic
- Degrees, marksheets and recognition
- Issuer, document version and regulatory period
- Checked against the official source
- Pillar 02
Employment
- Employer identity and trusted HR routes
- Chronology across records
- Company existence is not proof of employment
- Pillar 03
Professional
- Licence, regulator and validity period
- Registry-first status
- Jurisdiction and history kept explicit
One evidence model, role-specific workspaces.
Universities & boards
Answer verification requests from one case model, with official routes on record.
Employers & BGV teams
Source-heavy checks with chronology, and a dual-review workflow for adverse findings.
Platforms
Add verification to onboarding through the API, with evidence behind every result.
Reviewers
See the case state, its evidence and the next action in one workspace.
Candidates
Know exactly which item is requested, and correct, dispute or appeal a result.
Auditors
Reproduce any decision from preserved originals, sources and reviewer actions.
Where BonaFide stands today.
From the BonaFide pre-launch site, checked 27 Oct 2026.
- Built
The website, the institution portal preview and the verification pipeline: intake, document structure, quality and identity checks, forensic and passport lanes.
- In testing
Internally tested and being connected end to end on staging.
- Next
Self-serve access at launch. Until then, access is by request.
BonaFide does not announce issuer or institution partnerships until they are signed.
Inside BonaFide
Pick a feature to see its screen, what it does, and how it works once you connect your own accounts and data. All values are demo data.
Case BF-DEMO-014 · source checks
Degree · Example UniversityAuthority verified
Experience letter · Example SystemsSent to employer HR route
Professional licence · Example CouncilRegistry checked · valid period
No issuer portalRouted to BonaFide Desk
Statusin testing
Ask the source
Degrees, letters and licences routed to the issuer through official routes only, or through BonaFide Desk when there is no portal.
When it opens to customers, you upload a candidate's packet and BonaFide routes each credential to its issuer through official routes only, or through BonaFide Desk when there is no portal. Not yet running for customers; access is by request.
Inside BonaFide
Part of one ecosystem
Start with BonaFide.
Request early access, or talk to us about enterprise and sovereign deployment.