Technology

eSign Failure Handling for Lenders: Error Codes and Fixes

|Posted by Hitul Mistry / 19 Nov 26

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.

CodeOfficial MessageLikely CauseFixAuto-Retry?
ESP-901Invalid Authentication ModeWrong mode value sentSend 1, 2, 3 or 4 as allowedNo; fix config
ESP-902 / 903Invalid ASP ID (empty, or may not exist or be inactive)Wrong environment or expired ASP onboardingCheck ASP ID with the ESPNo; fix config
ESP-905Document Hash not receivedHash missing in requestFix hash generation and resendYes, once
ESP-906UID Token does not matchDifferent person authenticatedConfirm the right signer, restartNo; review
ESP-907 / 908Request Time Stamp empty or not validServer clock drift beyond 30 minutesSync server time, new requestYes
ESP-909 / 910Transaction ID empty or duplicateRetry reused the old IDNew transaction ID per attemptYes
ESP-911 / 922Input XML signature verification failed or invalidASP signing certificate expired or not mappedRenew or remap the certificate with the ESPNo; fix config
ESP-944 / 945User terminated eKYC process (after OTP generation)Borrower abandonedReminder, then fresh linkAfter nudge
ESP-946User interface page expiredBorrower took too longFresh link with a new transactionAfter nudge
ESP-991 / 993 / 999ESP database, CA response or unknown errorProvider-side faultRetry with delay; switch ESP if repeatedYes

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.

  1. Technical error: retry automatically up to three times, 2–5 minutes apart, each with a new transaction ID.
  2. Borrower drop-off: send a reminder by short message service (SMS) and WhatsApp within 30 minutes, then a fresh link.
  3. OTP not received: offer fingerprint, iris or face authentication where your ESP supports it.
  4. Repeated ESP errors: route new requests to a secondary ESP if you have one.
  5. 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.

  1. Final agreement version locked and stored.
  2. E-stamp certificate generated and attached.
  3. KFS shown and acknowledged.
  4. eKYC name matches the loan record.
  5. Signer list and signing order set for co-borrowers and guarantors.
  6. Mobile number confirmed as active.
  7. Unique transaction ID generator in place.
  8. Server time synchronised.
  9. ASP signing certificate valid for at least 30 days.
  10. 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.

StepTypical Handling TodayBuilt Into a Custom Lending Platform by Digiqt
DetectBorrower calls to complainError code captured on every response
ClassifySupport guesses the causeCode mapped to configuration, request or borrower
RetrySame request resentNew transaction ID and timestamp per attempt
NudgeManual calls next dayReminder sent within minutes of drop-off
EscalateLost in emailAssisted-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.

MeasureManual Follow-UpCode-Based Retry and Fallback
First-attempt failures (15%)1,5001,500
Recovered within 48 hours6001,200
Lost to drop-off900300
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

Read our latest blogs and research

Featured Resources

Technology

Digital Loan Agreement e-Stamping and e-Sign for Lenders

Digital loan agreement e-stamping and e-sign for lenders: legal basis, state stamp duty, workflow controls and an illustrative e-stamp volume plan.

Read more
Technology

Loan Disbursement Delays: Fix Sanction-to-Payout Gaps

Loan disbursement delays explained for lenders: where time is lost between sanction and payout, how to measure each stage and how to fix the bottlenecks.

Read more
Technology

Loan Agreement Template Management After Every Rule Change

Loan agreement template management: the clauses RBI rules now dictate, a 7-step change workflow, a version register and 5 metrics for legal teams.

Read more

About Us

We are a technology services company focused on enabling businesses to scale through AI-driven transformation. At the intersection of innovation, automation, and design, we help our clients rethink how technology can create real business value.

From AI-powered product development to intelligent automation and custom GenAI solutions, we bring deep technical expertise and a problem-solving mindset to every project. Whether you're a startup or an enterprise, we act as your technology partner, building scalable, future-ready solutions tailored to your industry.

Driven by curiosity and built on trust, we believe in turning complexity into clarity and ideas into impact.

Our key clients

Companies we are associated with

Life99
Edelweiss
Aura
Kotak Securities
Coverfox
Phyllo
Quantify Capital
ArtistOnGo
Unimon Energy

Our Offices

Ahmedabad

B-714, K P Epitome, near Dav International School, Makarba, Ahmedabad, Gujarat 380051

+91 99747 29554

Mumbai

C-20, G Block, WeWork, Enam Sambhav, Bandra-Kurla Complex, Mumbai, Maharashtra 400051

+91 99747 29554

Stockholm

Bäverbäcksgränd 10 12462 Bandhagen, Stockholm, Sweden.

+46 72789 9039

Malaysia

Level 23-1, Premier Suite One Mont Kiara, No 1, Jalan Kiara, Mont Kiara, 50480 Kuala Lumpur

Lewes

16192 Coastal Highway, Lewes, Delaware 19958, USA

software developers ahmedabad
ISO 9001:2015 Certified

Call us

Career: +91 90165 81674

Sales: +91 99747 29554

Email us

Career: hr@digiqt.com

Sales: hitul@digiqt.com

© Digiqt 2026, All Rights Reserved