> 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.4.md).

# V 3.0.0.4

**emSigner Release Notes — Version 3.0.0.4 — August 2026**

Version 3.0.0.4 extends emSigner's .NET Core platform to the UAE region, adds AI-powered document summarization for faster document review, brings Darwinbox and Coupa integrations onto .NET Core, introduces Electronic Seal (organization and individual sealing certificates), and adds Gesture-Based Video Verification for stronger identity assurance.

#### What's New at a Glance

| Feature                               | Region | Summary                                                                                                       |
| ------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------- |
| UAE Region — .NET Core Migration      | UAE    | .NET Core capability extended to UAE instance                                                                 |
| AI-Generated Document Summary         | Global | AI-generated summary of documents                                                                             |
| Darwinbox Integration — .NET Core     | Global | Darwinbox integration now available on .NET Core                                                              |
| Coupa Integration — .NET Core         | Global | Coupa integration now available on .NET Core                                                                  |
| Electronic Seal (Sealing Certificate) | Europe | Organization and individual sealing certificates, with validation and access control                          |
| Gesture-Based Video Verification      | Global | New active verification option alongside Basic Video Verification, using a head-turn prompt within 20 seconds |

***

**1. UAE Region — .NET Core Migration**

**Region:** UAE

**Overview:** The .NET Core capability introduced in v3.0.0.0 has now been extended to the UAE region.&#x20;

**Key Benefits:**

* Brings UAE clients onto the same modern .NET Core architecture as other regions

**Use Cases:**

* UAE-based clients can now operate on the .NET Core platform with regional storage support

***

**2. AI-Generated Document Summary**

**Region:** Global

**Overview:** emSigner now generates an AI-powered summary of a document before it is sent for signature, giving signers a quick, plain-language overview of the document's content and key terms.

**Key Benefits:**

* Reduces time spent reading long documents before signing
* Supports faster turnaround on high-volume document workflows

**Use Cases:**

* A business user reviews multiple envelopes in a queue and uses summaries to prioritize which ones need closer reading
* Compliance or approval teams use the summary as a quick first-pass check before detailed review

***

**3. Darwinbox Integration — Now on .NET Core**

**Region:** Global

**Overview:** The Darwinbox integration is now available on the .NET Core platform. Both existing and new clients can use this integration going forward.

**Key Benefits:**

* Brings the Darwinbox integration onto emSigner's modernized architecture
* Ensures continued support for HR document workflows without disruption

**Use Cases:**

* HR teams continue sending offer letters, onboarding documents, and policy acknowledgements for e-signature directly from Darwinbox

***

**4. Coupa Integration — Now on .NET Core**

**Region:** Global

**Overview:** The existing Coupa integration, previously available on the .NET Framework, has now been extended to the .NET Core platform.

**Key Benefits:**

* Extends an established integration onto the modernized .NET Core platform
* Maintains continuity for clients already using Coupa with emSigner

**Use Cases:**

* Procurement teams continue routing purchase orders and vendor contracts through Coupa for e-signature without workflow changes
* Clients migrating to .NET Core retain uninterrupted access to their Coupa-based signing workflows

***

**5. Electronic Seal (Sealing Certificate)**

**Region:** Global

**Overview:** emSigner now supports Electronic Seal as a signing method, backed by sealing certificates (PFX/P12) that are uploaded and validated under Settings. Certificates can be configured as either Organization-type, available to eligible users across the organization, or Individual-type, allocated to a specific user. A certificate must pass validation (correct client secret, valid serial number, certificate holder, and validity period) before it can be saved, and Electronic Seal is only available to users who have a certificate allocated to them.

**Key Benefits:**

* Enables organization-level and individual-level electronic sealing alongside standard signatures
* Built-in certificate validation prevents incorrectly configured or invalid certificates from being saved
* Granular access control ensures only users with an allocated certificate can seal documents
* Admins can revoke a user's certificate allocation at any time, immediately removing their ability to seal

**Use Cases:**

* An organization uploads a shared sealing certificate so any authorized department user can apply the company seal to outgoing documents
* A specific officer is issued an individual sealing certificate so only they can apply their personal seal
* An admin revokes a departing employee's certificate allocation, immediately disabling their access to Electronic Seal

***

**6. Gesture-Based Video Verification**

**Region:** Global

**Overview:** emSigner now offers Gesture-Based Video Verification as an additional video verification option, alongside the existing Basic Video Verification. With Basic Video Verification, the signer records a brief video and liveness/face match checks run in the background. With the new Gesture-Based option, the signer must respond to an on-screen prompt — a head-turn gesture — within a 20-second window during recording, followed by the same liveness and face match checks. Both options remain available; the gesture-based check adds a stronger, user-visible verification step for clients who choose it.

**Key Benefits:**

* Adds a stronger, user-visible anti-spoofing option on top of existing background liveness checks
* Gives clients the choice between Basic (background) and Gesture-Based (active) video verification
* Time-bound gesture challenge (20 seconds) confirms real-time presence
* Applies uniformly across all global clients as an available verification option

**Use Cases:**

* A client handling high-value transactions enables Gesture-Based Video Verification to require signers to actively confirm presence via a head-turn prompt
* A client with lower-risk workflows continues using Basic Video Verification, where liveness and face match are verified in the background without an active prompt
* Compliance and risk teams gain the option to enforce active liveness checks for specific workflows or client segments


---

# 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.4.md?ask=<question>&goal=<endgoal>
```

`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.
