When to Use DigiLocker and When to Use eSign
Choose between retrieving an issued document and obtaining a new signature. Map the consent, signer authority, evidence, and provider boundary for each step.
Use a document retrieval workflow when you need an existing record. Use an electronic signature workflow when someone needs to sign a new document. A product can require both steps for the same customer journey.
DigiLocker describes issued records and document sharing. The Controller of Certifying Authorities describes eSign as a service that applications can use to obtain an electronic signature through the applicable provider. DigiLocker FAQ CCA eSign overview
Compare the evidence
| Decision | Document retrieval | eSign workflow |
|---|---|---|
| What starts the request? | Application needs an existing record | A person needs to sign a specific document |
| What should the person review? | Document access and purpose | Document to sign and signing action |
| What comes back? | Applicable document or retrieval result | Signature result under the provider contract |
| What must the app preserve? | Source, permission, and check outcome | Signed document or reference and signer evidence |
| Who owns the next decision? | Application evidence reviewer | Application or agreement owner |
Use the applicable provider terms to confirm permitted data flows, support responsibilities, and the proof you receive.
Separate the two steps in a contract flow
A synthetic equipment rental company needs to review a licence and obtain acceptance of an agreement. The driver first shares the approved record. The application records the retrieval result and applies the evidence policy.
The intended signer then reviews the final agreement in the separate signing journey. Track the agreement version and the expected signer. Record the signature result with that version.
If someone changes the agreement after it was signed, treat it as a new revision. Follow the approval and signing process for that revision. A prior signature applies to the document identified in the earlier transaction.
Test independent failures
- Complete retrieval and cancel signing.
- Confirm that the agreement remains unsigned in your application.
- Change the agreement version before signing.
- Confirm that the result is attached to the correct version.
- Try to accept a result under an unrelated account.
- Verify that the account binding prevents the change.
Make the interface reflect each step. “Licence review complete” and “Agreement signed” describe different evidence and different user actions. Choose a DigiLocker integration route.
Review the application flow with NamoID
NamoID engineers can help map account control, consent, and result handling around your document and signing providers. Share a synthetic journey showing where evidence is retrieved and where agreement is given. Message the NamoID team in Slack