Manav.id
For HRIS, payroll & ATS platforms

The person you onboarded is the person on payroll.

Your platform is where the hire becomes an employee. Manav binds that human to a passkey at onboarding, then re-verifies — 30 seconds, on their own device — at the moments that matter. The operative behind the laptop farm can’t sign.

The receipt below was signed and checked in this tab, with zero network calls.

Never in your money pathNo biometric vaultVerify without us, forever
MANAV RECEIPT · v1 network: idle
…
Generating key & signing…
Ed25519 · WebCrypto · in this tab
actionpayroll.reverify employeemanav:human:7f3a9c…e21b · hired 2026-03-02 cyclepayroll · 2026-08 deviceenrolled at offer acceptance assurancepasskey + liveness challenge issued—
Cryptographic fields
nonce— kid— sig—
Signed and verified in this tab — zero network calls. View source welcome.
The loss your customers are carrying
1 in 4

candidate profiles will be fake by 2028; 6% already admit interview fraud.

29

laptop farms raided across 16 states placing DPRK operatives in US companies.

309

US companies staffed through one Arizona laptop farm — $17M to Pyongyang.

The gap between the interview and the keyboard

Background checks and KYC happen once, at hire. The fraud happens after: the person who aced four interviews is not the person who logs in Monday, or the identity is real but the worker behind it rotates nightly. Detection tools watch behavior — and lose. The only continuous fact is that the enrolled human either signs, or doesn’t.

Sells on compliance and sanctions risk, not just fraud loss — the DPRK scheme is under active Treasury and DOJ enforcement.
What fails without it: the interviewee who isn’t the worker, the deepfake on the video round, the rotating bench behind one identity — none can produce the enrolled human’s signature on schedule.
What your platform gains: “verified workforce” as a sellable tier, audit-ready evidence for your customers’ compliance teams, and the lifecycle story — interview → offer → first login → every payroll cycle — no point-in-time IDV vendor can tell.
Where it sits in your product

Three integration points. Your brand, our receipt.

Onboarding bind

At offer acceptance, the hire enrolls a passkey + liveness baseline on their own device — inside your flow, your brand.

Lifecycle re-verify

Your platform triggers a 30-second re-verify on a schedule or on events: first login, payroll change, privileged access.

Interview continuity

Same human across every round: the person who signed round one signs the offer — defeating bait-and-switch before day one.

// Before the consequential action, from your backend:
const receipt = await manav.sign({
  action: 'payroll.reverify',
  payload: { employeeId, cycle },
  approver: employee.principal,
  assurance: 'passkey+liveness',
});
if (receipt.ceremony === 'completed') proceed(receipt.id);
// Anyone verifies the receipt offline against our published JWKS — forever.
Structurally neutral. The receipt format and verifier are Apache-2.0 open source, filed at the OpenID Foundation and IETF. You embed a standard, not a competitor.
Nothing of yours flows through us. Payloads never leave your systems — only hashes. A Manav outage can’t block your product: issuance pauses, every existing receipt still verifies.
Verification is free for everyone, forever. Your customers’ auditors, banks and counterparties check receipts with one public key — that’s what makes the receipt worth issuing.
We’re early and say so. No fake logos — the mechanism runs in this page. Read the sleeper-on-the-payroll case →
Try it before you talk to us

Run the ceremony yourself. Then try to fake it.

A controlled sandbox of the exact flow above — your system asks, the enrolled human signs on their own device, a receipt is issued, and you attack it. Real Ed25519, in this tab, nothing sent anywhere.

Next step

A 30-minute integration conversation.

Bring the flow in your product where this belongs. We’ll run the ceremony on it and hand you a receipt you can verify yourself before the call ends — and a straight answer on what an embed looks like commercially.

Step 1 of 2

Talk to us about embedding

No biometrics, no tracking pixels. Your email goes to one inbox and nowhere else.
Step 2 of 2

Where would it sit?

Something went wrong. Email [email protected] and we’ll sort it.
✓

Request received.

You’ll get times from [email protected] within one business day — reply to lock one in.

We’re early, and we’d rather say so than fake logos: the receipt format and verifier are public, Apache-2.0 open source, and the mechanism above just ran in your browser. Judge it before you ever talk to us.