> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/releases/release-notes/v-3.0.0.3.md). # V 3.0.0.3 **emSigner Release Notes — Version 3.0.0.3 — July 2026** Version 3.0.0.3 focuses on data governance, resilience, and mobile modernization, adding configurable data retention, a resumable eStamping journey, more reliable external signing, expanded signature methods and global coverage, and a mobile API migration to .NET Core. **What's New at a Glance** | Feature | Region | Summary | | ------------------------------------------------------------- | ------ | --------------------------------------------------------------------------------------------------- | | Data Retention & Purging | Global | Configurable retention policies, recoverable grace period, secure recovery portal, full audit trail | | eStamping (NeSL) — Resumable Journey | India | Seamless resume, initiator failure alerts with correct-and-resubmit, refreshed UI/UX | | External Signing — Reliability, Failover & Identity Assurance | Global | Seamless eStamping payment, signature failover, demographic verification, resumable sessions | | Signature Methods & Global Coverage | Global | Aadhaar biometrics, multi-region/language/timezone, GST/VAT | | Mobile Application — API Migration to .NET Core | Global | Mobile app API migrated to .NET Core; added deep linking and push notifications | **1. Data Retention & Purging** **Region:** Global **Overview**\ Organizations can now configure data retention policies to automatically manage the lifecycle of documents and associated data. Purged data enters a recoverable grace period before permanent deletion, and a secure recovery portal allows authorized users to restore data within that window. All retention and purge actions are captured in a full audit trail. **Key Benefits** * Configurable retention policies tailored to organizational or regulatory needs * Recoverable grace period to prevent accidental permanent loss * Secure self-service recovery portal * Complete audit trail of retention and purge activity **Use Cases** * Organizations with regulatory data retention requirements * IT and compliance teams managing storage lifecycle * Administrators needing to recover accidentally purged data **2. eStamping (NeSL) — Resumable Journey** **Region:** India **Overview**\ The eStamping journey via NeSL has been enhanced to support seamless resumption if a session is interrupted, so users no longer need to restart the process from the beginning. Initiators now receive failure alerts when an issue occurs, with the ability to correct the problem and resubmit directly. The overall UI/UX for eStamping has also been refreshed. **Key Benefits** * Seamless resume of interrupted eStamping sessions * Proactive failure alerts to initiators * Correct-and-resubmit flow without starting over * Refreshed, clearer user experience **Use Cases** * Users completing eStamping transactions across multiple sessions or devices * Initiators managing failed or incomplete stamping requests * Organizations relying on NeSL eStamping for document authentication **3. External Signing — Reliability, Failover & Identity Assurance** **Region:** Global **Overview**\ External signing workflows have been made more resilient with seamless eStamping payment handling, automatic signature failover when a preferred signing method is unavailable, and demographic verification for stronger identity assurance. Sessions can now be resumed rather than restarted after an interruption. **Key Benefits** * Seamless payment handling during eStamping * Automatic failover to alternate signature methods for continuity * Demographic verification for stronger identity assurance * Resumable sessions that reduce drop-off and repeated effort **Use Cases** * External signers completing transactions requiring eStamping payment * Organizations requiring strong identity assurance for external signers * Workflows spanning unreliable networks or interrupted sessions **4. Signature Methods & Global Coverage** **Region:** Global **Overview**\ emSigner expands signing method support with Aadhaar biometric-based signing, alongside broader global coverage spanning multiple regions, languages, and timezones. Support for GST/VAT has also been extended to accommodate regional tax and compliance requirements. **Key Benefits** * Aadhaar biometric authentication for signing * Expanded multi-region, multi-language, and multi-timezone support * GST/VAT support for regional compliance * Broader accessibility for a global user base **Use Cases** * Organizations in India using Aadhaar biometric signing * Multinational organizations operating across regions * Businesses needing GST/VAT-compliant transaction handling **5. Mobile Application — API Migration to .NET Core** **Region:** Global **Overview**\ The emSigner mobile application's backend APIs have been migrated to .NET Core, aligning the mobile experience with the platform's broader modernization. This release also introduces deep linking and push notifications for the mobile app. **Key Benefits** * Modernized, .NET Core-based mobile API backend * Deep linking for direct navigation to specific documents or actions * Push notifications to keep users informed in real time * Improved consistency between mobile and web platform architecture **Use Cases** * Mobile users needing timely alerts on signing activity * Users navigating directly to a document via a shared link on mobile * Organizations relying on the mobile app for on-the-go signing --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.emsigner.com/releases/release-notes/v-3.0.0.3.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.