Aadhaar eSign API
Popular
Let a signer authenticate through Aadhaar, give consent, and apply a certificate-backed signature to a document inside your own journey.
Overview
Aadhaar eSign lets someone sign a document online after an Aadhaar-based authentication identifies them. The signature applied to the file is backed by a certificate created for that signing. There is no token to issue and nothing for the signer to renew. Lenders, insurers, marketplaces, logistics networks and staffing platforms deal with customers who are never in the room. They can finish execution in the same session that produced the document, instead of emailing a copy and waiting for a scan nobody can verify. The signer sees what is being signed, authenticates, and gives explicit consent before the signature is applied. The authentication methods you can offer and the files you get back depend on the data source behind them and on your service contract.
- Category
- Legal Services
- Coverage
- India, for signers identified by an Aadhaar-based authentication
- Input
- The prepared document and the signer's details, with the signer's consent to an Aadhaar-based authentication
- Output
- The signed document with its signature applied, and the reference your system needs to trace the signing
- Typical users
- Lending, insurance, fintech, marketplace, logistics and HR operations teams
- Coverage note
- India. The authentication methods, the files returned and the document types supported depend on the data source and your 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: loan agreements signed the moment the customer accepts
- Insurance: proposal and servicing forms signed remotely by the policyholder
- Fintech and PSP: merchant service agreements signed during onboarding
- Marketplaces: seller agreements signed before a listing goes live
- Logistics and fleet: driver-partner and vendor agreements signed at induction
- Staffing and gig platforms: offer letters and contractor terms signed off-site
What this service does
What comes back after an Aadhaar eSign
When signing completes, your application can receive the signed document, the signature applied to it, and the reference that lets you trace the transaction later. The fields and files you get can vary with the data source behind them and with your service contract.
eSign inside your own app
Connect the flow to a website, a mobile app, a loan origination system, a policy administration platform or an internal dashboard. Execution then happens in the session that produced the document, instead of in a separate email thread.
Nothing for the signer to buy or install
The signer needs no hardware and no certificate of their own. They authenticate, consent, and the signature is applied. That is what makes the flow workable for customers who sign once.
Consent stored with the signature
You show the signer what is being signed, and they give explicit consent before the signature is applied. The consent stays with the executed file.
How a check runs
Assemble the document
Your application assembles the final document and identifies the signer or signers it must reach.
Send the signer to Aadhaar authentication
You show the signer the document, and they complete an Aadhaar-based authentication of the kind your service contract supports.
Capture the consent to sign
The signer confirms the intent to sign and gives explicit consent for the signature to be applied to that document.
Collect the signed file and its reference
Your application receives the signed document and a structured response carrying the reference and the signing details available.
Carry on with the journey
Store the signed document with its audit information and let the process continue: disbursal, activation, onboarding or dispatch.
Questions
- What is Aadhaar eSign?
- It is a way to sign a document online where an Aadhaar-based authentication identifies the signer. The signature applied to the document is backed by a certificate created for that signing, rather than by a certificate the signer holds on a token.
- How does an Aadhaar eSign API work?
- Your application prepares the document and sends the signer to authenticate. The signer sees what is being signed, completes the authentication and consents. Your application then receives the signed file with the reference it needs to trace the transaction. The methods available and the files returned depend on your service contract.
- What does the signer need to complete an Aadhaar eSign?
- An Aadhaar-based authentication they can complete. Where a one-time password is used, it reaches the mobile number registered against the Aadhaar. A signer whose number is out of date has to update it before signing. Nobody has to buy a token or a certificate in advance.
- How is Aadhaar eSign different from a DSC or a plain electronic signature?
- Aadhaar eSign identifies the signer at the moment of signing, which suits people who sign occasionally. A Digital Signature Certificate belongs to a named authorized signatory who signs repeatedly in a defined role and holds it on a token. A general electronic signature suits lower-risk documents where an audit trail is the requirement. Each has its own page in this catalog.
- Can every document be signed with Aadhaar eSign?
- No. Indian law keeps some instruments outside electronic execution. Wills, trusts, powers of attorney and negotiable instruments other than cheques are the usual examples, and a document that requires registration still requires it. Confirm with your own legal advisors that a document may be executed this way before you automate it.
- Can I add Aadhaar eSign to an app I already run?
- Yes. The signing step can sit inside a website, a mobile app, an origination or servicing platform or an internal workflow tool. It is subject to the technical documentation you get at onboarding and to your service contract.
Catalog entry last updated .