P
Verification layer · live in 47 jurisdictions

Proof, on paper, isn't enough.

Session SES·0000·0000 Issuer PW Registry / EU·UK·US·SG
Identity verified
License current
Sanctions clear
CPD on file
Peer-attested
Continuously monitored
Identity verified
License current
Sanctions clear
CPD on file
Peer-attested
Continuously monitored

Trust, measured at scale.

PW·001
0+
Professionals verified across the network
PW·002
0+
Issuing bodies and registers indexed
PW·003
0
Jurisdictions with live registry sync
PW·004
0%
Primary-source verification accuracy
01
Identity.
Government-grade ID match, biometric liveness, and continuous device attestation. The person you onboard is the person who renews — every time.
  • MethodKYC + Liveness
  • StandardeIDAS / NIST 800-63
  • CadenceOnboarding + Annual
02
Credentials.
Primary-source verification against universities, licensing boards and prior employers. Paper diplomas become cryptographically signed records.
  • MethodPSV + W3C VC
  • StandardOpen Badges 3.0
  • CadenceReal-time
03
Standing.
Live sync against statutory registers, sanctions lists and disciplinary panels. A lapsed licence or open complaint surfaces the moment it does.
  • MethodRegistry sync
  • Sources1,200+ bodies
  • CadenceContinuous
04
Practice.
CPD logs, peer attestations and verified work history — the signal that someone is not just qualified, but actively practising at standard.
  • MethodCPD + peer
  • StandardDomain-specific
  • CadenceRolling 24 mo
05
Continuous watch.
Webhooks fire the moment anything changes — a renewed licence, a new sanction, an expired insurance policy. Trust that doesn't go stale.
  • MethodEvent stream
  • Latency< 60 seconds
  • Cadence24 / 7 / 365
Identity Credentials Standing Practice Watch

Built like a registry. Used like an API.

F·01

Verifiable credentials

Issue, store and present W3C-compliant credentials with selective disclosure. One wallet, every standard.

F·02

Registry sync

Live API integration with statutory registers across medicine, law, engineering, finance and trades.

F·03

Sanctions watch

Continuous monitoring against OFAC, OIG, EU consolidated lists and 80+ professional disciplinary feeds.

F·04

Peer attestation

Cryptographically signed endorsements from verified colleagues — reputation that survives platform changes.

F·05

Disciplinary API

Programmatic access to a normalised, GDPR-aware feed of disciplinary actions across 47 jurisdictions.

F·06

White-label issuance

Issue your own branded credentials — bar associations, training providers, employers — on our rails.

Things people ask.

Detailed answers for compliance teams, platform operators and individual practitioners.

What exactly gets verified?
Identity (KYC + biometric liveness), academic and professional credentials (primary-source), current standing on statutory registers, sanctions and disciplinary history, insurance and CPD records, and verified work history. Each layer is independently revocable and time-stamped.
How is the underlying data sourced?
Directly from issuing authorities — universities via HEDD/NSC, regulators via official register APIs, employers via signed exchange. We do not scrape, and we never accept user-uploaded PDFs as the source of truth. If we can't verify primary-source, the credential is marked unverified, never approximated.
Is Proofwork GDPR-compliant?
Yes. The professional always controls their record. Selective disclosure means a verifier sees only the field they need (e.g. "is licensed in NY", not the licence number). Data is stored in-region (EU / UK / US / SG) and you can export or delete the full record at any time.
Who pays — professionals or platforms?
Either, both, or neither. Professionals can carry a free wallet; platforms pay per verification or for an enterprise seat. Issuers (registries, training bodies) can issue at cost. The record itself is portable across all three.
What happens when a credential lapses?
The credential's status flips to expired in real time and a webhook fires to every connected platform. The professional gets a renewal nudge 90, 30 and 7 days out. Anyone holding a presentation of that credential sees an automatic revalidation prompt.
How is fraud detected?
Three layers: cryptographic signatures make forged credentials mathematically detectable; behavioural anomaly detection on issuance, presentation and renewal patterns; and a human review board for disputed records. Confirmed fraud is published to our shared sanctions feed.

Start a verified conversation.

For platforms looking to integrate, issuing bodies looking to publish, or professionals looking to claim their record — we read everything.

Sales / Platformshello@proofwork.io
Issuers / Registriesissue@proofwork.io
Practitionerssupport@proofwork.io
Presspress@proofwork.io
0/500
By submitting you agree to a single follow-up from our team. No newsletters, no resale, no nonsense.
✓ Message received · We'll respond within 24 hours