Branch scanning, account opening packets, trade finance files and decades of archived customer records — all of it full of identifiers that were collected before anyone asked whether they should be stored in the clear.
Talk to our technical team → — for integration questions, a security review or a volume estimate.
They need different sizing. A flow integration is provisioned to your steady-state peak; a backlog run is provisioned for a fixed window and then stepped down. Both use the same key and the same endpoints.
Large banks have document management platforms with their own roadmaps, and inserting anything into them takes quarters. Cooperative banks, regional banks, small finance banks and the vendors who build for them can put a single REST call into their pipeline this month.
The flow integration is the easy half. The archive is where the audit finding comes from, and it is a project rather than a change.
Document management platforms, loan origination systems, core banking integrators and BPOs all end up holding customer identity documents on behalf of a bank, and all get asked the same three questions in procurement.
The hosted API runs in ap-south-1 with no document retention, which answers most of what an on-premise requirement is usually trying to achieve. If your policy requires in-perimeter processing regardless, tell us and we will have that conversation directly rather than pretending the hosted service is something it is not.
Yes. The batch endpoints take many documents per call and return a ZIP with a manifest giving per-document status. Documents where no number was found come back unchanged and are listed as such — those are the ones still needing attention.
Not today, and we will not imply otherwise on a page your auditor is reading. If a certification is a hard procurement gate, tell us before you spend time evaluating.
Sample a few hundred representative documents first and read the manifest. The share coming back with nothing found tells you how much human effort the project actually needs, which is the number that makes or breaks the plan.
Yes. Keys are scoped per endpoint and the API refuses anything outside the plan with a 403. It is enforced server-side, so it holds even if the integration's code tries.
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.