Employment Verification

The Problem

Employment verification is broken:

• 7-10 days to verify via phone calls to HR departments—candidates wait, job offers delayed
• 40% of resumes contain lies (HireRight, 2025)—fabricated job titles, extended dates, fake companies—undetected until (if) reference checks happen
• $4.8 billion lost annually in gig economy (2025)—workers with fabricated credentials, banned users creating new accounts
• Phone-based verification fails: Scammers spoof phone numbers, fake HR reps confirm fake employment

Even “official” verification services are slow:

• Centralized background check companies take 3-5 days, charge $30-$100 per check, and can’t verify gig work (Uber ratings, Upwork history)
• Pay stub verification requires uploading sensitive documents (full salary, SSN visible)—privacy nightmare
• LinkedIn profiles: Self-reported, no cryptographic proof—anyone can claim “VP at Company X”

Why It Matters Now

• Talent mobility increasing: Average worker changes jobs every 4.1 years (2026)—each change = 7-10 day verification delay
• Gig economy growing 40% annually: Workers need portable reputation across platforms (Uber → Lyft, Upwork → Fiverr)
• Remote hiring: Companies hiring globally—can’t call international HR departments (time zones, language barriers)
• Fraud detection gaps: Resume fraud undetected until background check completes—wasted interview cycles, delayed hiring

The infrastructure exists: W3C Verifiable Credentials for employment records, OpenID4VP for presentation flows, BBS+ selective disclosure for privacy. The platforms that adopt cryptographic employment verification first will hire faster, reduce fraud, and unlock cross-platform worker mobility.

---

How Affinidi Enables Employment Verification

The key shift: Instead of HR departments fielding phone calls or workers uploading pay stubs, employers issue verifiable credentials at hire and exit:

1. Credential issuance - Employer issues W3C Verifiable Credential to departing employee: “Employee X worked as Role Y from Date A to Date B”
2. Credential storage - Employee stores credential in Affinidi Vault on their device—portable work history, owned by worker
3. Verification flow - Employee applies to new job, new employer requests: “Prove prior employment.” Employee presents credential, employer verifies signature
4. No phone calls - New employer verifies cryptographically in seconds—no waiting for HR callbacks, no forged letters

All of this supports selective disclosure (prove “employed as engineer” without revealing salary) and real-time revocation (if credential was issued in error, employer revokes via Trust Registry).

Technical Foundation

• Elements Services issues W3C Verifiable Credentials for employment records:

  • Job title, department, start/end dates
  • Performance ratings (if employer chooses to include)
  • Reason for leaving (voluntary, layoff, termination—encoded securely)
  • Income range (with BBS+ selective disclosure: prove “income > $100k” without revealing exact salary)

• Affinidi Vault stores credentials on worker’s device—private keys never leave secure enclave, credentials portable across jobs

• OpenID4VP (Verifiable Presentations) provides verification flow:

  • Employer: “Prove prior employment at Company X”
  • Worker: Presents credential (signed by Company X)
  • Employer: Verifies signature + checks issuer via Trust Registry

• Trust Registry (TRQP) validates employer authority:

  • “Is Company X authorized to issue employment credentials?” (prevents fake companies)
  • “Is this credential still valid (not revoked)?”

• BBS+ Selective Disclosure lets workers reveal only needed attributes:

  • Prove “employed as engineer” without revealing salary
  • Prove “income > $100k” without revealing exact amount
  • Prove “left voluntarily” without revealing performance details

Example Flow: Corporate Hiring

[Candidate Alice interviews at Company B]
  ↓
Company B: "Prove prior employment at Company A"
  ↓
Alice's prior employer (Company A) issued credential at exit:
  - Issuer: Company A (did:webvh:company-a)
  - Subject: Alice (did:webvh:alice)
  - Job title: Senior Engineer
  - Department: Platform
  - Start date: 2020-01-15
  - End date: 2024-06-30
  - Reason: Voluntary departure
  ↓
Alice presents credential to Company B via OpenID4VP
  ↓
Company B receives presentation, verifies:
  ✓ Signature valid (Company A issued this)
  ✓ Issuer trusted (TRQP query: Company A authorized to issue employment credentials)
  ✓ Credential not revoked (TRQP query)
  ✓ Dates match claimed work history
  ↓
Employment verified—no phone call to Company A, no 7-day wait
  ↓
Company B extends offer same day

What this means:

• No phone calls: Company B verifies cryptographically—no waiting for HR department callback
• No forged letters: Can’t fake Company A’s cryptographic signature
• Worker privacy: Alice can choose selective disclosure—prove “employed” without revealing salary or performance rating
• Real-time revocation: If Company A issued credential in error, they revoke via Trust Registry—next verification blocked

---

Real-World Applications

Corporate Hiring: Instant Verification

Problem: Candidate claims “Senior Engineer at Company X, 2020-2024.” HR department calls Company X, waits 7 days for HR callback, offer delayed—candidate accepts competing offer while waiting.

Solution: Company X issued employment credential when candidate left. Candidate presents credential to new employer. New employer verifies: signature valid? Company X authorized (TRQP query)? Credential not revoked?

Outcome:

• Employment verified in seconds—no phone calls, no waiting
• Cryptographic proof—impossible to forge, auditor-ready
• Faster hiring cycles—extend offer same-day, beat competitors

---

Gig Economy: Cross-Platform Reputation

Problem: Worker has 5-star rating on Uber, applies to Lyft. Lyft can’t verify—no cross-platform trust. Worker banned on Platform A creates new account on Platform B—fraud continues.

Solution:

1. Uber issues reputation credential when worker exits: “5-star rating, 2,000 rides, zero violations”
2. Worker presents credential to Lyft
3. Lyft verifies: signature valid? Uber authorized? Worker not globally banned (TRQP query)?

Outcome:

• Cross-platform reputation verified—fraud blocked, workers carry verified history
• Platforms trust each other’s verification—no need for centralized reputation database
• Workers benefit: High-reputation workers skip onboarding, get premium gigs immediately

---

Finance: Loan Underwriting

Problem: Loan applicant claims “$120k salary at Company X.” Bank calls HR, waits for pay stub verification, loan delayed 2 weeks—applicant goes to competitor.

Solution: Company X issues income credential with BBS+ selective disclosure: “Employee earns $120k annually.” Applicant proves “income > $100k” without revealing exact salary.

Outcome:

• Loan underwriting instant—bank verifies income cryptographically, no pay stubs, no HR calls
• Applicant privacy preserved—bank sees “income > $100k,” not exact salary or other details
• Fraud blocked: Can’t forge income credential (cryptographic signature required)

---

Professional Licensing: Healthcare Hiring

Problem: Nurse applies to hospital. Hospital must verify: state nursing license, prior employer, no disciplinary actions, malpractice history. Process takes 30 days—nurse waits, hospital short-staffed.

Solution:

1. State board issues license credential: “Licensed RN, expires 2027-12-31, no disciplinary actions”
2. Prior employer issues employment credential: “Employed 2020-2024, Cardiology ICU, no incidents”
3. Nurse presents both credentials
4. Hospital verifies: signatures valid? Issuers trusted? Credentials not revoked?

Outcome:

• Hiring process reduced from 30 days to same-day—cryptographic proof of license + work history
• Patient safety maintained: Hospital verifies license status in real-time via TRQP
• Staffing efficiency: Fill critical roles immediately, no 30-day lag

---

Why Affinidi

	Affinidi Employment Verification	Phone-Based Checks	Centralized Services	Blockchain Records
Verification speed	✓ Instant	✗ 7-10 days	⚠ 3-5 days	⚠ Hours (chain sync)
Fraud prevention	✓ Cryptographic signatures	✗ Spoofed calls/emails	⚠ Database alterable	⚠ No identity layer
Worker privacy	✓ Selective disclosure	✗ All details shared	✗ All details shared	✗ All data public
Portable credentials	✓ Worker owns, presents anywhere	✗ Employer owns records	✗ Service owns records	⚠ Chain-locked
Real-time revocation	✓ TRQP queries	✗ Manual updates	⚠ Batch updates (lag)	✗ Immutable, no revocation

What this means:

• Phone-based checks: Slow (7-10 days), fraud-prone (spoofed calls), privacy-invasive (HR shares all details)
• Centralized verification services: Faster (3-5 days) but still slow, can’t verify gig work, database admins can alter records
• Blockchain employment records: Immutable but public (privacy nightmare), no revocation (if credential issued in error, can’t fix), no identity layer (can’t verify issuer authority)

Affinidi provides instant verification + cryptographic fraud prevention + worker-owned credentials + selective disclosure—the only architecture that scales employment verification to modern talent mobility.

Proof It Works

• W3C Verifiable Credentials - Industry-standard employment record format
• OpenID4VP - Standard presentation protocol (adopted by EU Digital Identity Wallet)
• BBS+ Selective Disclosure - Production-ready zero-knowledge proofs (prove “income > $100k” without revealing exact salary)
• Affinidi Vault - Open-source wallet, credentials portable across employers

---

Get Started

For Developers

Issue your first employment credential

Create an employment credential, have worker store in Vault, verify presentation—end-to-end in under an hour.

Start building →

---

For HR Teams

See a live demo of instant employment verification

Watch candidate present employment credential, see verification complete in seconds, compare to phone-based checks.

Schedule demo →

---

For Enterprises

Custom deployment consultation

Integrate employment credential issuance into HRIS (Workday, ADP), configure Trust Registry, automate credential generation at exit.

Talk to an expert →

---

Related Resources

Technical Deep Dives

• Verifiable Credentials - How cryptographically signed credentials work
• Verifiable Presentations - How credentials are shared during verification (OpenID4VP)
• Zero-Knowledge Proofs - BBS+ selective disclosure explained

Related Solutions

• Reusable KYC - Similar credential exchange pattern for financial services
• Passwordless Authentication - Verifiable credentials for login flows
• Cross-Org Agent Trust - How agents prove identity across organizations

Case Studies

(Coming soon: HR tech platform employment verification implementation)