eSign Failure Handling for Lenders: Error Codes and Fixes
Last reviewed: November 2026
eSign failure handling for lenders is the process of finding why a borrower's electronic signature on a loan agreement failed, fixing the cause and completing the signature through a retry or fallback route. Every failed eSign is a sanctioned loan that cannot disburse, and every hour of delay raises the chance the borrower takes another offer.
Heads of digital lending and product heads at non-banking financial companies (NBFCs), banks and fintech lenders ask the same questions when signing stalls. Each one is answered briefly below, from the official eSign service provider (ESP) error codes to retry rules, e-stamp order and the Digiqt Lending Platform build.
At a Glance
- Read the error code before retrying, since ESP codes separate your configuration faults from borrower drop-offs.
- Every retry needs a new transaction ID and a fresh timestamp, or the ESP rejects it.
- Check names before eSign, not after, because a mismatch between the Aadhaar name and the agreement is cheaper to fix upstream.
- Stamp first, sign second, send third, with signed documents going to the borrower only after all signers finish.
What Is eSign Failure Handling for Lenders?
eSign failure handling for lenders covers three kinds of failure: technical errors between your application and the ESP, borrower authentication failures, and borrower drop-offs. In eSign, your platform acts as the application service provider (ASP) that sends a document hash in an Extensible Markup Language (XML) request to an ESP, which authenticates the signer and returns the signature.
Is eSign the Same as a Digital Signature Certificate?
No, and the two are often mixed up. eSign issues a short-lived certificate for each signing after online authentication, while a digital signature certificate (DSC) is one the holder keeps and reuses, usually on a token.
Which Rules Govern Aadhaar eSign for Loan Agreements?
Four rules apply: the Information Technology Act, the Controller of Certifying Authorities (CCA) eSign application programming interface (API) specifications, and two Reserve Bank of India (RBI) disclosure rules.
- Legal basis: eSign operates "under the provisions of the Second Schedule of Information Technology Act, 2000" (CCA eSign API Specifications).
- Request format: timestamp within "maximum 30 minutes deviation"; authentication modes are one-time password (OTP) or time-based OTP (TOTP) = 1, fingerprint = 2, iris = 3, face = 4 (CCA eSign API Specifications 2.1).
- Key Facts Statement (KFS): given before executing the loan contract, with acknowledgement (NBFC Responsible Business Conduct Directions, 2025, para 29(1)).
- After execution: digitally signed KFS, sanction letter and terms "shall automatically flow to the borrower on the registered and verified email / SMS" (NBFC Credit Facilities Directions, 2025, para 9(3)).
The CCA's eSign API page lists every version. Version 2.1 covers online Aadhaar eSign, and the 3.x series covers certifying authority (CA) electronic know your customer (eKYC) accounts.
Which eSign Failure Codes Do Lenders See and How Are They Fixed?
They fall into configuration errors you fix once, request errors you fix per transaction and borrower errors you fix with a nudge or a new route. This runbook table comes from Annexure 1 of the CCA eSign API Specifications 2.1.
| Code | Official Message | Likely Cause | Fix | Auto-Retry? |
|---|---|---|---|---|
| ESP-901 | Invalid Authentication Mode | Wrong mode value sent | Send 1, 2, 3 or 4 as allowed | No; fix config |
| ESP-902 / 903 | Invalid ASP ID (empty, or may not exist or be inactive) | Wrong environment or expired ASP onboarding | Check ASP ID with the ESP | No; fix config |
| ESP-905 | Document Hash not received | Hash missing in request | Fix hash generation and resend | Yes, once |
| ESP-906 | UID Token does not match | Different person authenticated | Confirm the right signer, restart | No; review |
| ESP-907 / 908 | Request Time Stamp empty or not valid | Server clock drift beyond 30 minutes | Sync server time, new request | Yes |
| ESP-909 / 910 | Transaction ID empty or duplicate | Retry reused the old ID | New transaction ID per attempt | Yes |
| ESP-911 / 922 | Input XML signature verification failed or invalid | ASP signing certificate expired or not mapped | Renew or remap the certificate with the ESP | No; fix config |
| ESP-944 / 945 | User terminated eKYC process (after OTP generation) | Borrower abandoned | Reminder, then fresh link | After nudge |
| ESP-946 | User interface page expired | Borrower took too long | Fresh link with a new transaction | After nudge |
| ESP-991 / 993 / 999 | ESP database, CA response or unknown error | Provider-side fault | Retry with delay; switch ESP if repeated | Yes |
Because the specification says Aadhaar authentication errors "may be forwarded to ASP", log the Unique Identification Authority of India (UIDAI) code alongside the ESP code. Track error rates through API monitoring for lending integrations.
What If the Borrower's Name Does Not Match the Agreement?
Stop and fix the record before the next eSign attempt. The certificate carries the name from the borrower's eKYC, so "Ramesh K Patil" signing an agreement for "Ramesh Kumar Patil" creates a mismatch your auditors will question.
Compare the eKYC name with the loan record at onboarding, using the same tolerance rules as your video KYC for lenders process, and record any alias with evidence.
How Should Lenders Retry or Fall Back After an eSign Failure?
Escalate in five steps, from automatic retry to a human-assisted route, as in this illustrative flow.
- Technical error: retry automatically up to three times, 2–5 minutes apart, each with a new transaction ID.
- Borrower drop-off: send a reminder by short message service (SMS) and WhatsApp within 30 minutes, then a fresh link.
- OTP not received: offer fingerprint, iris or face authentication where your ESP supports it.
- Repeated ESP errors: route new requests to a secondary ESP if you have one.
- Still unsigned after 48 hours: assign to a call-centre or branch queue for assisted signing before the offer expires.
The CCA's 3.3 specification caps failed authentication attempts per transaction at five for the eKYC provider, so do not loop OTPs. For co-borrowers and guarantors, set the signing order in advance, as covered in guarantor and co-applicant verification.
Where Does E-Stamping Fit in the eSign Sequence?
E-stamping comes before eSign, because the stamped agreement is the document the borrower signs. The order is: generate the final agreement, attach the e-stamp certificate, show and acknowledge the KFS, collect borrower signatures, apply the lender's signature, then send the signed set.
A retry of the same agreement version reuses the stamped document; a changed agreement goes to legal for a stamp decision. State stamp rules are in our guide to digital loan agreement e-stamping, and KFS timing is in the key fact statement for loans guide.
What Should a Checklist to Prevent eSign Failure Include?
Ten checks remove most failures before the borrower sees the signing page. Build them into your journey design.
- Final agreement version locked and stored.
- E-stamp certificate generated and attached.
- KFS shown and acknowledged.
- eKYC name matches the loan record.
- Signer list and signing order set for co-borrowers and guarantors.
- Mobile number confirmed as active.
- Unique transaction ID generator in place.
- Server time synchronised.
- ASP signing certificate valid for at least 30 days.
- Fallback route ready: other authentication modes, secondary ESP and assisted signing.
Audit the journey against RBI digital lending guidelines compliance, and measure signing completion next to pre-approved loan offer conversion.
How many sanctioned loans are stuck at the eSign step today?
See How Digiqt Builds eSign Recovery Into Lending Journeys
Share last month's eSign error log with our team, or talk to us about your signing journey.
How Can the Digiqt Lending Platform Handle eSign Failures?
The Digiqt Lending Platform can handle eSign failures by reading each error code and choosing a retry, reminder or fallback automatically. The Digiqt Lending Platform lets lenders launch custom lending products in weeks, covering onboarding, disbursement and repayments through user-friendly APIs, and Digiqt builds eSign handling like this into it.
| Step | Typical Handling Today | Built Into a Custom Lending Platform by Digiqt |
|---|---|---|
| Detect | Borrower calls to complain | Error code captured on every response |
| Classify | Support guesses the cause | Code mapped to configuration, request or borrower |
| Retry | Same request resent | New transaction ID and timestamp per attempt |
| Nudge | Manual calls next day | Reminder sent within minutes of drop-off |
| Escalate | Lost in email | Assisted-signing queue after the time limit |
Keep agreement versions in loan agreement template management, so every retry signs the right version.
How Much Disbursement Does a 15% eSign Failure Rate Put at Risk?
Weak handling can lose about one in ten sanctioned digital loans at the signing step. In this illustrative worked example, a lender sends 10,000 agreements for eSign in a month with an average loan of ₹60,000.
| Measure | Manual Follow-Up | Code-Based Retry and Fallback |
|---|---|---|
| First-attempt failures (15%) | 1,500 | 1,500 |
| Recovered within 48 hours | 600 | 1,200 |
| Lost to drop-off | 900 | 300 |
| Disbursement lost | ₹5.4 crore | ₹1.8 crore |
Code-based handling keeps ₹3.6 crore of that month's disbursement. Signing stalls also show up as loan disbursement delays, so track the two together.
Want eSign failures fixed in minutes, not days?
Plan eSign Retry and Fallback Rules With Digiqt
Start with your top five error codes, or visit Digiqt to book a digital lending journey review.
Sources
- CCA: eSign API Specifications (all versions)
- CCA: eSign API Specifications 2.1, Annexure 1 Error Codes
- CCA: eSign API Specifications 3.3 (9 December 2020)
- RBI: Non-Banking Financial Companies – Credit Facilities Directions, 2025 (RBI/DOR/2025-26/347)
- RBI: Non-Banking Financial Companies – Responsible Business Conduct Directions, 2025 (RBI/DOR/2025-26/362)



