You are shipping features, not building an OCR stack. This is the document layer — extract, verify, mask, redact — as four REST endpoints you can integrate in an afternoon and hand to a compliance reviewer without a rewrite.
Talk to our technical team → — for integration questions, a security review or a volume estimate.
Aadhaar masking looks like a weekend project. A regex for twelve digits, a black rectangle, done. Here is what the weekend project misses, in the order teams discover it — usually in production.
Worked clients with retry and error handling for Python, Node.js and Java. Start on a trial key against the live service — there is no mock environment, deliberately, because a sandbox returning canned responses tells you nothing about how your documents actually OCR.
Usually a week before a funding diligence, and usually about code somebody wrote eighteen months ago and left.
A single multipart POST with an API key header. Most teams have masking in a staging pipeline the same day. There is no SDK to install and no dependency to add.
Yes. A trial key with a small quota calls the live service, so what you test is what you will run in production.
It keeps it out of ours: we return counts by type, never the values, precisely so an identifier does not end up in every access log between us. What your own application logs is yours to control — the usual mistake is logging the request body on error.
Yes. The 16-digit VID authenticates in place of an Aadhaar number and is covered by default. It is the identifier most in-house implementations miss.
Fail closed: do not store the original and continue. Hold the document out of the archive, retry, and surface it for review if it keeps failing. The failure mode worth designing against is an exception path that quietly falls back to storing the unmasked file.
You can, but think about what it implies: the unmasked document has to live somewhere until the worker picks it up, which recreates the stored object you were trying to avoid. Synchronous masking in the request path is the pattern that actually removes the risk.
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.