Aadhaar Masking API
New
Redact the Aadhaar number on an uploaded document image. Your team can then store, review and share a copy that no longer holds the full number.
Overview
Aadhaar masking redacts the Aadhaar number on a document image so that only the last four digits stay readable. The photograph, the name, the address block and the layout of the page are left intact. Most businesses that accept an Aadhaar copy as proof of identity or address have no reason to keep the full number once the check is done. When an API applies the redaction inside the upload path, branch, agent, app and partner channels all store the same masked copy. Nobody has to remember to black out a number. What can be detected depends on the image, and the output available may vary by document type, data source and record. Build a review path for images the service cannot process confidently.
- Category
- KYC Services
- Coverage
- Aadhaar document images uploaded inside your own workflow
- Input
- A document image already uploaded in your workflow
- Output
- A masked image with the leading digits of the Aadhaar number obscured
- Typical users
- Lending, insurance, fintech, marketplaces, staffing
- Coverage note
- Supported document types and image formats depend on the selected service contract
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Reference in progress
The request and response reference for this endpoint is not published yet.
Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:
- Endpoint URL and method
- The host, path and HTTP verb for this service.
- Authentication
- How a request identifies itself, and where credentials come from.
- Request parameters
- Field names, types, which are required, and validation rules.
- Response schema
- The success body, field by field, with a real example.
- Error codes
- What each failure means and which are worth retrying.
- Rate limits
- Request ceilings, and what happens at the ceiling.
No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.
Use cases
- Lending and NBFC - redact identity proofs before they enter the loan file
- Insurance - mask proposal and claim documents handled by intermediaries
- Fintech and PSP - keep merchant onboarding attachments free of full numbers
- Marketplaces - seller and delivery-partner identity uploads at scale
- Staffing and gig platforms - candidate files passed to verification vendors
- Real estate - tenant and buyer documents held in shared folders
What this service does
Only the number region is covered
The photograph, name, address block and page layout stay readable. The masked copy still evidences what the customer submitted. An operations or audit team can review it.
Masked before the copy is stored
The redaction step can run inside the upload path. The masked version is then the one written to your document store, loan file or ticket attachment. Nobody has to clean up after an unredacted copy exists.
Built for phone photos and scans
Both arrive in onboarding. Skew, glare, low resolution and heavy compression affect what can be detected. Route unclear images to review, since the output available may vary by document type, data source and record.
One standard for new files and old archives
Apply the same step to branch uploads, agent applications, mobile journeys and partner handoffs. Run it as a batch pass over documents you already hold. Historical files then reach the same standard.
How a check runs
Agree document types and volumes
Start with Get API and tell us about the workflow you are building. Access, supported document types and volumes depend on the selected service contract.
Put masking in the upload path
Place the step between the point a document image arrives and the point you write it to permanent storage. That sits in your onboarding journey, agent application or document management system.
Send the document image
Your application sends the image your customer or agent uploaded, in a format the service contract supports.
Get the masked image back
The service returns the redacted version of the image, with a defined path for anything it cannot process confidently.
Store and share the masked copy only
Write the redacted image to your systems and attach it to outbound handoffs. Keep the unmasked original out of logs, caches and temporary storage.
Questions
- What do I send to mask an Aadhaar document?
- A document image your customer or agent has already provided, such as a scan or a phone photograph of an Aadhaar letter or card. Send it in a format the selected service contract supports. The redaction itself needs no other customer data.
- What does the Aadhaar masking API return?
- A masked version of the image you submitted, with the leading digits of the Aadhaar number obscured and the last four still readable. What comes back for a given image may vary by document type, image quality, data source and record.
- Does masking change the rest of the document?
- The intent is to redact the number region only. The photograph, name, address block and page layout stay readable. That keeps the copy useful as a record of what was submitted.
- Do I still need consent if the Aadhaar number is masked?
- Yes, masking reduces what you hold and does not replace consent. Collect the document only with the customer's informed consent and for a purpose you have told them about. Keep it only as long as that purpose or your record-keeping obligations require.
- Can I mask Aadhaar documents I have already stored?
- Yes. The same step can run as a batch pass over an existing archive and bring older files to the same standard as newly captured ones. Volumes and batch handling depend on the selected service contract.
- What happens if an image is too poor to mask?
- Plan a review path. Skew, glare, low resolution, partial crops and heavily compressed uploads all affect what can be detected. An image the service cannot process confidently should go to a manual queue and never into storage unredacted.
Catalog entry last updated .