Know who you're hiring before day one.
Payslips, employment history and identity - verified from source records before the offer letter goes out, not discovered in month three.
Free trial credits included · Full API documentation
What a résumé can't prove
Résumés are claims. PF records, payslip forensics and identity linkages are evidence - and the gap between the two is where bad hires come from.
What we check for HR teams
Employment claims verified against the records employers actually file - not the documents candidates supply.
Screening that finishes before the offer letter
Collect
The candidate shares PAN and payslips in your existing onboarding or ATS flow.
Verify
UAN resolution, employment history, payslip forensics and identity linkage run as API calls - no OTPs for the candidate to forward.
Decide
A structured report reaches the recruiter: verified, flagged or mismatched, with reasons.
The APIs behind the hiring flow
Every call is encrypted in transit and at rest, DPDP-aligned, and logged with a full audit trail - and the data stays in India.
Before you add this to background checks
How do you verify employment history?
Through EPF records. A UAN lookup returns the establishments that actually filed PF for the candidate, with dates - employment history from the source, not the résumé.
Can we check a candidate's current employer?
Yes. Previous and current employer PF filing status shows where contributions are actually being made, which catches moonlighting and fabricated notice periods.
What does the payslip check look for?
Edited amounts, cloned templates, inconsistent fonts and figures that don't reconcile - the same document forensics we run on bank statements, tuned for salary slips.
Do candidates need to share OTPs?
No. UAN verification runs without an OTP, so background checks don't depend on the candidate forwarding codes.
Verify the résumé before it becomes a payroll entry.
Free trial credits and full documentation from day one.
Start free trial or book a 20-minute call