Hrkyc™ – Simplifying Right-to-Work and Id Checks for UK Employers

I built HRKYC™ to solve a compliance headache I’ve seen over and over: verifying employees’ Right-to-Work (RTW) and ID in the UK is slow, inconsistent, and often still done through email threads, photocopies, and spreadsheets.

Employers face up to £20,000 in fines per illegal worker, yet the tools to stay compliant are fragmented and expensive. You either integrate multiple APIs yourself (ID, RTW, phone, document checks) or pay enterprise vendors £80–£200 per candidate.

HRKYC™ automates all of it behind a simple workflow.

What it does

• Employers embed a 2-line widget in their onboarding flow or careers page. • Candidates enter name + email, and HRKYC™ takes over: → verifies identity, phone, and RTW status through approved APIs → stores results securely with full audit trail → issues a CandidateID™ badge candidates can add to Apple/Google Wallet.

Employers get results and compliance evidence automatically.

Candidates get a reusable verified status for future jobs.

How it’s built

The system is API-first and modular, designed so verification providers can be swapped or added without rewriting core logic.

All data is validated and normalized to a structured schema before storage.

We focused on isolation and compliance — each employer’s workspace is sandboxed, and verification records are encrypted and auditable.

The dashboard and widget share the same API, which keeps the architecture simple and consistent.

Why this matters

Every UK employer must perform RTW checks, but most still rely on manual workflows that are slow and error-prone.

HRKYC™ makes compliance automatic — reducing risk, saving time, and keeping small employers out of trouble.

My goal: make employment verification as easy as “Sign in with Google,” but for compliance.

Pricing

PAYG: £39 / candidate Subscriptions from £299 / month (includes audit storage)

We’re also contemplating with running a small non-equity crowdfund (~£50k) to complete the MVP in ~6 weeks.

I would love your thaughts, inouts and your experience regarding crowdfunding.

Feedback

I’d also love feedback from:

• HR/recruiting SaaS founders • compliance or gov-tech engineers • anyone building onboarding or identity tools

Especially interested in thoughts on the API surface design — how you’d model employer vs candidate flows — and whether a reusable verified ID (CandidateID™) could extend beyond RTW into other regions.

https://hrkyc.com

Thanks, Masoud — founder support@hrkyc.com