eStamp — Leegality

What does this API do?

The Leegality eStamp capability (BharatStamp) allows lenders integrated with the ULI Platform to digitally stamp loan documents as part of the eSign workflow. Stamping can be combined with an eSigning journey in a single API call or used independently for stamping-only flows via NeSL.

Key capabilities of BharatStamp:

• Available across 31 States and Union Territories.
• Supports both fixed and dynamic stamp duties.
• Dynamic stamping — automatically selects appropriate stamp denominations based on transaction value.
• Reclaims unused stamps if a signer drops off, eliminating stamp paper wastage.
• Integrates with NeSL (National E-Governance Services Ltd) for compliance tracking of stamped documents.

The same eSign eStamp API endpoint handles both eSign and eStamp operations. Stamping parameters are passed alongside signing parameters in the request body. After successful processing, the lender receives a Document ID, and signatories receive signing/stamping links via their preferred communication channel.

Who can use it?

Lenders and financial institutions onboarded on the ULI Platform who require legally compliant digital stamping — with or without accompanying eSigning — for loan agreements, security documents, or other instruments requiring stamp duty payment.

Prerequisites

Complete all common platform prerequisites as described in Getting Started with ULI Platform APIs.

In addition, the following Leegality-specific steps must be completed before using eStamp:

• Leegality Account Onboarding — Complete the necessary Leegality account setup to obtain system access.
• X-Auth-Token Setup — Retrieve your X-Auth-Token from the API Settings tab on your Leegality dashboard. This is required in every API request header.
• Stamp Procurement — BharatStamps must be procured in advance through Leegality before they can be used in requests.
• Workflow Configuration — Define and publish a Workflow Profile in the Leegality dashboard that includes stamping. The profileId of a published workflow is mandatory in the request body.
• NeSL Onboarding (if applicable) — If documents require NeSL-compliant stamping (lending or non-lending flows), complete NeSL-specific onboarding with Leegality and configure party, document, and security details accordingly.
• Template Configuration (if applicable) — If using a Template-type workflow, configure the template beforehand. A Base64-encoded PDF can also be passed directly.
• Callback URL Registration — Register a callback URL with the platform to receive post-stamping and post-signing webhook notifications.

API endpoints

HTTP Method: POST

URL path convention: /{service name}/{ver}/{lang}

Headers

Request body

All requests must be in JSON format. The top-level envelope parameters are:

Key stamp-specific fields within the data object:

Key NeSL-specific fields within the data.neslData object (required for NeSL-compliant stamping):

Sample request skeleton for eStamp with NeSL:

{
  "ts": "2025-05-01T10:00:00Z",
  "txncode": "TXN123456789",
  "ver": "1.0",
  "hmac": "<SHA-256 hash of data value>",
  "data": {
    "profileId": "<workflow-profile-id>",
    "file": {
      "name": "LoanAgreement.pdf",
      "file": "<base64-encoded-pdf>"
    },
    "neslData": {
      "documentDetail": {
        "loanNumber": "LN12345",
        "registrationType": "INDIVIDUAL_LOAN",
        "state": "Karnataka",
        "sanctionAmount": "500000",
        "typeOfDebt": "FINANCIAL",
        "accountClosedFlag": "NO",
        "fundType": "FUNDED",
        "sanctionCurrency": "INR"
      },
      "stampData": [
        {
          "firstParty": "Borrower Name",
          "secondParty": "Bank Name",
          "stampDutyAmount": "500",
          "considerationPrice": "500000",
          "descriptionOfDocument": "Loan Agreement",
          "stampDutyPaidBy": "Borrower Name",
          "articleCode": "<nesl-article-code>"
        }
      ]
    },
    "invitees": [
      {
        "name": "Borrower Name",
        "email": "borrower@example.com",
        "phone": "9876543210"
      }
    ],
    "irn": "LENDER-REF-001"
  }
}

Response fields

Retrieving the stamped document: Use the Get Details API (POST /leegality/detail/1.0/en) with the documentId returned in the eStamp response. Pass "refreshNeslDocument": true in the request body to fetch the latest stamped document from NeSL. The stamped file will be available at data.file in the response once stamping is complete.

Note: If a document is stamped but not yet signed, NeSL may not return the stamped file by default. Contact Leegality to enable stamped document retrieval for your account.

Callback (Webhook): After each event, Leegality sends a POST to the lender's registered callback URL. The lender's endpoint must return HTTP 200. If not received, Leegality retries 3 times.

Error codes

For a comprehensive list of platform-level error codes, refer to the Latest Platform Error Code document.

Who to contact?

If you encounter an issue with the eStamp API, email support@rbihub.in with the following details:

• Subject: Leegality eStamp API Error
• Service Name: esign-estamp
• Environment: Sandbox or Production
• Service Provider: Leegality
• Request Headers
• Request Payload
• Error Code and Error Message
• Screenshot or log of the error
• Prerequisites status: IP Whitelisting, URL Whitelisting, Service Subscription, Token Generation, Stamp Procurement