Every hire hands over an Aadhaar, a PAN, past payslips and educational certificates. HR platforms and background verification firms process these by the thousand, then keep them in an HRIS that was not designed to hold identity documents.
Talk to our technical team → — for integration questions, a security review or a volume estimate.
/extract-aadhaar and /extract-pan return name, date of birth and the identifier as JSON, so onboarding forms fill themselves and a typo never becomes a payroll record. The Aadhaar checksum is validated, so a mis-read is caught rather than stored./mask-aadhaar before the document reaches the HRIS. You needed the number to verify; you do not need to keep it readable for the length of someone's employment and seven years beyond.Onboarding is a one-week process that creates a twenty-year record. The documents collected in that week are still there long after everyone who collected them has left.
The instinct is to mask on upload and be done. That breaks onboarding, because the number you just covered is the one payroll needs to read.
Yes. The extraction endpoint returns name, date of birth, gender and the number as JSON with the checksum validated. Note that the unmasked-number entitlement is granted per organisation against a stated lawful basis rather than self-serve.
That is your counsel's call, not ours. What we can say is that most HR systems keep the document image long after they needed the number, and masking at intake removes that exposure without changing the verification step.
The generic redaction endpoint does, because it looks for identifiers rather than document types. The Aadhaar and PAN endpoints are for those specific cards.
Not if you extract first. Read the fields you need as JSON, complete the verification step, and mask the document afterwards. The stored image was never how payroll should have been reading the number anyway.
The clearest case of retained data with no remaining purpose. Masking at intake means there is nothing to purge later, which matters because the purge job is the one nobody gets around to building.
Tell us how many documents a month you process and what your peak looks like. We will size a plan, provision a key with a test quota, and answer a security questionnaire if you need one.