For employers & platforms

Verified workforce identity that travels between jobs.

Verify identity, qualifications, and clearance for staff and gig workers against portable credentials — right-to-work that a multi-jurisdiction employer can trust across every market it operates in.

Talk to us

Overview

The shift, in one anchor.

Hiring across markets means re-running identity, right-to-work, and qualification checks at every employer and on every gig platform — slow for the worker, costly for the employer, and impossible to trust across borders. Civic Anchor makes the worker’s verified identity, credentials, and clearances portable.

A worker carries identity, qualifications, and clearance as credentials they present with consent; an employer or platform verifies all of it in one check, and a multi-jurisdiction operator can trust the same anchor in every market it runs in. Household and informal employers get the same rails — formal trust for informal work.

Capabilities

What you get.

Identity, qualifications, and clearance in one verification
Portable between employers and platforms
Right-to-work for multi-jurisdiction operators
Household and informal-employer verification supported

Use cases

Where it runs.

Right-to-work verification

Confirm identity + clearance in one consent-bound check, portable across employers and platforms.

Qualifications & skills

Verify formal credentials and attested skills against portable skill credentials the worker holds.

Gig & platform onboarding

Onboard drivers, couriers, and sellers against a held anchor — re-verifiable without re-collection.

Household & informal employers

Domestic workers and informal staff get verifiable, signed attestations that survive disputes.

Fits your stack

Connects where you already work.

Civic Anchor verification drops into the systems this sector already runs — over REST or tRPC, mTLS-secured, with webhook events on every result.

HRIS & ATS
Payroll
Background-check providers
Gig & marketplace onboarding
Access control

Integration

One call, a signed answer.

Your system requests a check; the subject approves in their wallet; you receive an HSM-signed, jurisdiction-stamped result over webhook.

Request · POST /api/v1/challenges

POST /api/v1/challenges
Authorization: <mTLS client certificate>

{
  "subject": "did:civicanchor:018e4f2c-…",
  "checks": ["identity", "right_to_work", "qualification"],
  "purpose": "pre_hire"
}

Webhook · signed result

{
  "challenge_id": "chl_01J2Qe…",
  "status": "verified",
  "subject": "did:civicanchor:018e4f2c-…",
  "jurisdiction": "ZA",
  "checks": { "identity": "pass", "right_to_work": "pass", "qualification": "verified" },
  "signed_by": "hsm:af-south-1"
}

What changes

Before the anchor, and after.

Dimension	Document-based today	With Civic Anchor
Right-to-work	Re-run at every employer and gig platform	One consent-bound check, portable across employers
Qualifications	Phone-and-email reference chasing	Verified against credentials the worker already holds
Multi-market hiring	A different process in every jurisdiction	The same anchor trusted in every market you run in

Compliance

Built to the regulator, in jurisdiction.

Worker-consented by construction; the worker controls what each employer sees. Data is held in-jurisdiction under the local data-protection regulator.

Institution portal

Bring Employers & platforms onto Civic Anchor.

Tell us your market and we’ll map the fastest path to verifying against the anchor — including the regulatory steps in your jurisdiction.

Talk to us All solutions