Integrations

Plug Aadhaar masking into your DMS, onboarding flow and existing systems.

Masking works best where documents arrive. Switch it on inside Eosten DMS, or call the masking engine from the systems you already run: one HTTP request per file, and the masked file comes straight back.

Get integration help See the API
01

Inside Eosten DMS

The shortest path: Aadhaar masking is built into the document management system.

Auto-mask foldersWorkflow stepBulk jobs
  1. Switch it onMasking is switched on when Eosten DMS is installed, then an administrator turns it on for the workspace.
  2. Choose folders, or the whole systemPick the folders to mask (each one includes its subfolders), or apply masking to the entire system so every upload is covered.
  3. Masked automatically after uploadA few seconds after a file is uploaded, the stored file is replaced by its masked copy. New versions, restored versions and files brought in by ZIP import are masked the same way.
  4. At upload, or as a workflow stepWhen the administrator allows it, people can tick “Mask Aadhaar” in the upload dialog. Workflow designers can add a “Redact Aadhaar” step to any workflow.
  5. Documents you already holdA bulk job masks a folder, with or without its subfolders, including every stored version of each file.
  6. Nothing changed that shouldn't beSigned documents and documents under legal hold are not changed; they are listed in a report for someone to decide. Locked files and files in a running workflow are masked once they are free.
Good to know
  • Systems that already send documents to Eosten DMS through its API are covered too: files uploaded into a masking folder are masked the same way.
  • You choose how the mask looks: a solid block, blur or pixelation, its colour, and rounded corners.
  • The masking engine runs next to the DMS with no public port, so only the DMS can reach it.
  • Learn more about Eosten DMS
02

Your own DMS, LOS, CRM or onboarding app

Call the self-hosted engine's HTTP API from your system. One request per file.

HTTP APIContainerYour network
  1. On uploadYour system receives a document: from a customer in your onboarding app, a branch scanning loan files, or an employee joining.
  2. Send it to the engineYour system sends the file to the masking engine on your own network, with a reference of your choice.
  3. Get the masked file backThe reply carries the masked file in the same format, and says whether the number and the QR code were masked.
  4. Store the masked copy, discard the originalSave the masked copy in your DMS, LOS or CRM. If the reply says a card was found but nothing could be masked, route the file to a person to check.
For your developers
  • We share the API reference and sample code when you start an integration, and help your team make the first connection.
  • Ask for the integration guide
Good to know
  • The reply comes when masking is done: in seconds for a card photo, longer for a multi-page PDF. Use a generous client timeout.
  • It takes JPG, PNG, TIFF and PDF. The maximum file size is a setting of your deployment.
  • The engine runs as a container on ordinary CPUs; plan on at least 8 GB of memory. One engine masks one file at a time, and we size the set-up to your volume with you.
03

Archives you already hold

Bulk Aadhaar masking for the KYC scans and files you already have.

Bulk jobsZIP importYour script
  1. In Eosten DMS: run a bulk jobChoose a folder, include its subfolders if you like, and start. Every stored version is masked, and skipped files are listed with the reason. An option re-checks files already found clean.
  2. Or bring the files in by ZIPImport a ZIP of scans into a masking folder, and each file is masked as it lands.
  3. Other repositories: loop over the filesYour script sends each file to the engine and writes the masked copy back. There's no separate batch tool: the script is yours, and the engine masks one file per request.
Good to know
  • Use your own record IDs as the reference, not file names or customers' names: the reference appears in the engine's logs.
  • Sending many files in one request is on the roadmap.
04

Security notes

Keep the engine private, next to the systems that use it.

Your networkBehind your system
  1. Runs inside your networkThe engine is built to sit on your private network, next to the systems that use it. Only your systems can reach it.
  2. Your system decides who may maskThe engine has no user accounts or keys of its own. Your DMS, LOS or gateway already knows its users, so it decides who may send documents, and it is the only thing that talks to the engine.
  3. Never on the public internetKeep the engine's port closed to the outside and put it behind your own system. Inside Eosten DMS, the engine has no public port at all.
  4. What the engine keepsThe engine doesn't keep the images it masks. Aadhaar numbers and card text are not stored or logged.
Good to know
Integration help

Tell us where
your documents go.

Your DMS, your loan origination system, your CRM or your onboarding app: we'll help you connect Aadhaar masking to the systems your documents pass through.

Get integration helpBook a demo