We’re excited to announce the NeSL Certificate Validation on App1.

‍

NeSL Certificate Validation allows senders to verify a NeSL invitee's details before they eSign a document. The invitee's information, provided by the sender during the sending process (via form or Excel), is cross-checked against the invitee's data at NeSL.

Key Points:

• Validation Parameters:
  • Name: Must have at least a 75% match.
  • Year of Birth (YOB): Requires an exact match.
  • Gender: Requires an exact match.
• Mismatch Consequences:
  • If any of the fields do not meet the required threshold, the invitee's signature will not be applied to the document.
• Verification Process:
  • The invitee's details entered in the NeSL form are cross-verified against the certificate details fetched during the signing process.
• Availability:
  • This feature is available across API, Excel Upload, and Dashboard workflows.

‍

For more information, check out these resources:

‍Knowledge Base: https://support.leegality.com/portal/en/kb/articles/nesl-aadhaar-validation

Contract repository filters

The Filters functionality in the Contracts section has been enhanced! You can now refine your search results more effectively with the addition of variable-based filters. This allows you to filter contracts based on dynamic fields, such as deal value, making it easier to extract actionable contracts.

For example, you can now easily retrieve all contracts with a deal value greater than ₹1 crore.

‍

TAT for tasks and reminders for collaborators

TAT (Turnaround Time) helps you set deadlines for collaborators on specific tasks. If a collaborator misses the deadline, email notifications are automatically sent to the collaborator. This ensures that your deals are closed within the set timeframe and keeps everyone accountable for meeting their deadlines.

‍

For more information, check out these resources:

• Contracts Filters: https://knowledge.leegality.com/deal-collaboration/Contracts/find-contracts
• TAT for tasks: https://knowledge.leegality.com/deal-collaboration/Workflows/create-workflow#tat-turnaround-time-settings

‍

We’re excited to announce the Notifications Logs on App1.

Notification Logs help document senders easily track the status of notifications sent to their invitees. Whether you’re sending invitations, document completion alerts, or verification OTPs, Notification Logs provide you with detailed insights into the delivery and engagement status of your communications.

Key Benefits:

• Comprehensive Tracking: View a complete history of notifications (Email, SMS, WhatsApp) sent to each invitee, including status updates like Sent, Delivered, Read, or Error.
• Instant Verification: Quickly confirm whether an invitee has received and interacted with your message, helping you address potential issues like missed or delayed notifications.
• Detailed Status Logs: Get specific information for each notification, including the channel used, notification type, timestamp, and status remarks for better visibility.

‍

For more information please refer to the following resources:

1. Knowledge Base - https://knowledge.leegality.com/manage-documents/document-details/notification-logs
2. FE Page - https://www.leegality.com/features/notification-logs

‍

We've released the new Multiple Stamp Series feature on App1.

The Multiple Stamp Series feature allows users to affix multiple stamps of the same or different denominations from various stamp series to a single document. It is useful when you need to affix stamps with different purposes or article codes to the same document.

Key Benefits

• Flexibility to select Stamp Series: You can now add stamps from multiple series, even if they have the same or different denominations.
• Custom Quantities: Specify different quantities for each stamp series to match your document's requirements.
• Combined Use with Stamp Groups: You can use multiple stamp series alongside Stamp Groups, providing greater flexibility.

This flexibility ensures that the correct stamps are applied according to the specific requirements of each document.

Multiple Stamp Series is available in API, Excel Upload, and Dashboard.

You can now manage paper-based Bank Guarantees via NeSL as Hybrid Bank Guarantees.

Previously, only bank guarantees issued via NeSL (as eBG) could be managed digitally.

Key Benefit:

• No additional setup required: Manage paper-based bank guarantees digitally through NeSL, just like eBGs.

‍

This new feature is available via API, Excel Upload, and the Dashboard.

‍

Easily track your stamp orders with our new dashboard feature. Now, you can:

• Check the estimated delivery dates for their stamp orders.
• Monitor any delays in stamp procurement.

This update helps users track their stamp orders more efficiently and stay informed about any potential delays.

We've made some updates to improve the clarity and usability of the Audit Trail.

‍

The following enhancements have been made to the audit trail.

• About the Audit Trail Section: Added a brief explanation of ‘what the Audit Trail is’ and its purpose to help recipients understand its importance.
• Role Clarification: The left column now clearly indicates the role of each invitee, showing roles like Invitation Sender, Signer, and Reviewer. 
• UI Improvements: Enhanced readability by displaying email/phone information under each invitee's name.

‍

These updates aim to make the Audit Trail more user-friendly and reduce any confusion for recipients.

‍

‍

We are excited to introduce the capability to add non-signing parties in Lending and Non-Lending NeSL flows. This new feature ensures that all relevant party information is communicated to NeSL, even if certain parties are not required to sign the document.

‍

This functionality is also available via API and Excel-based flows.

‍Important Note: NeSL allows banks to set up non-signing parties on a case-by-case basis after assessing their business use case. Clients must get their use cases approved by NeSL before using this feature.

We are pleased to announce a new eSign type: Visual Sign Impression, designed to cater to documents where timestamped digital signatures may not be suitable.

‍

Features of Visual Sign Impression

• It is a simple image-based signature without timestamps and document ID.
• Visual Sign Impression is available as a Signature Type across all sending channels: New Document Flows, Workflows, APIs, and Excel Upload.

For more details and usage guidelines, please visit our support documentation: https://support.leegality.com/portal/en/kb/articles/visual-sign-impression

We are pleased to announce a significant improvement in our stamp usage process.

‍

Key Changes:

‍

• FIFO Selection: When a request is made to create a stamped document, the system will select the stamp with the earliest order date (The date on which the stamps were added into the system). This means stamps that were added into the system earlier (First In) will be used first (First Out), ensuring that older stamps are used before newer ones. If there are multiple stamps with the same order date, the selection is based on the associated documentID to further refine the selection process.

‍

This upgrade ensures that older stamps are utilized first, preventing expiration and optimizing inventory management. Previously, stamps were selected randomly from a pool of 20 stamps with the earliest order date, which did not guarantee the use of the oldest stamps first.

‍

This upgrade applies to all modes of stamping using our inventory, including stamp series, stamp groups, and revenue stamps.

‍Note: No action is required from customers as the system upgrade has been implemented for all users immediately.

We are excited to introduce enhanced customization options for the signing journey on Leegality. You can now enhance the user experience by appending the following query parameters to the signURL obtained from the Create eSign Request API.

‍

• redirectUrl: Redirects invitees to a specified URL after completing the signing process.
• timer: Sets the duration (in seconds) the success page remains open before redirecting to redirectUrl.
• Okbutton: Controls the visibility of the OK button on the success page.

‍

Learn more: https://docs.leegality.com/webhooks_resources#section/Customise-Signing-Journey

‍

These enhancements enable users to customise the signing experience to their requirements directly from the API integration, providing greater flexibility and control over user interactions.

‍

We’re introducing the search and filter functionalities for the Users tab on the Leegality dashboard.

‍

• Search Capability: You can now search users by their name and email to quickly locate specific users within the dashboard.
• Filter by Roles: You can also filter users based on their roles i.e. Admin, Billing, and User.

We are excited to announce the beta launch of our new dashboard on production.

‍

Accessing the New Dashboard:

‍

• Option 1: Click on the 'Experience the New Leegality' button in the header to switch to the new dashboard view.
• Option 2: Directly log in from dashboard.leegality.com.

‍

Important Information

‍

• We encourage all users to familiarize themselves with the new dashboard, as it will become the default interface for Leegality moving forward once the full version is live.
• Note that support for the current dashboard will continue for the foreseeable future.

‍

We appreciate your support and feedback as we continue to enhance and refine the new dashboard experience.

As per NeSL's latest guidelines, the Consideration Price field now accepts only whole numbers. Previously, decimal values were also allowed.

‍

• Values such as 100.00 or 100.0 will be automatically converted to 100 without any errors.
• For values like 100.01, 100.50, or 100.55, a validation error will be displayed, requiring correction to a whole number.

‍

As per NeSL guidelines, a 16-character limit is now enforced on the Stamp First and Second Party OVD values.

Senders can now easily access NeSL eSign Details directly on the details page, ensuring that all necessary NeSL data is readily accessible.

‍

To view NeSL eSign details, click the "details" link next to the NeSL transaction ID.

The dialogue will show all NeSL information points added by the sender when the document was sent, including:

‍

• Registration Type
• Document Details
• Stamp Details
• Invitee Details
• Party Details

‍

Senders can now add reference attachments even after the document has been sent. This update allows senders to attach additional files to documents, which invitees can access during their signing journey.

For more details and usage guidelines, please visit our support documentation:

https://support.leegality.com/portal/en/kb/articles/advanced-options#Upload_reference_attachments_for_invitees5mbs_PDFs

We are excited to announce parallel SMS and WhatsApp messaging to invitees. This will greatly improve the communication capabilities and ensure a higher delivery rate.

What’s New?

• Parallel Messaging for Mandatory Notifications

You can send SMS and WhatsApp messages simultaneously for mandatory notifications such as completion alerts and manual reminders.

This ensures that invitees receive important updates promptly, regardless of their preferred communication channel.

‍

• Flexibility for Non-Mandatory Notifications

You can send both SMS and WhatsApp messages in parallel for non-mandatory notifications such as invitation alerts.

Alternatively, you can opt to send only WhatsApp messages, with SMS serving as a fallback option only in the event of WhatsApp message delivery failure.

‍

We’re excited to announce Non-OTP Reviewer Flow on App1

‍

In Non-OTP Reviewer Flow, reviewers no longer need to authenticate via OTP when reviewing documents. This eliminates the unwanted friction in their reviewing journey.

Quick 3-Step Review Journey

Step 1: Preview Document

Step 2: Provide Approved Consent or Rejection Remarks

Step 3: Click Approve/Reject Document Button

‍

And you’re done!

You can opt for Non-OTP Reviewer Flow based on the document's criticality like internal documents.

Benefits of Non-OTP Reviewer Flow

• Faster Review Process: Reduced TAT for document review.
• Reduced Friction: Reviewing process becomes smoother.
• Better User Experience: Quick 3-step process enhances the reviewer's experience.

‍

Learn more about Reviewer Flow: https://www.leegality.com/features/reviewer-flow

The stamp limit has been increased in NeSL use cases. Earlier, the limit was set to 10, but now the client can add the number of stamps as needed.

Smart User Liveliness is now available on App1!

‍

Smart User Liveliness ensures that the document signatory is actively present during the eSigning process. This AI-based technology verifies the real-time presence of the individual in front of the device, guaranteeing that the person initiating the eSign is indeed live and genuine.

Smart User Liveliness is an upgrade over the current liveliness feature which required a cumbersome process of writing and displaying an OTP to the camera.

Key Benefits:

We're excited to announce three upgrades to our NeSL API, enhancing the overall experience and functionality:

‍

• Error Webhook Notification: Clients now automatically receive webhook notifications in the event of an error response from NeSL for their documents.
• Enhanced API 3.3 Response Data: API 3.3 now sends detailed response codes and messages from NeSL for each document. It also indicates if retrying the NeSL invitation for a particular document is feasible.some text
  • New data points sent in Details API 3.3- responseCode, responseMessage, isRetryAllowed‍
• NeSL Invitation Retry API: We've introduced a dedicated API to retry NeSL invitations.

We’ve added a new Payment Gateway to Payment Collect - Billdesk.

‍

Leegality Payment Collect now supports 2 Payment Gateways - Razorpay and Billdesk.

So, you have the flexibility to choose between the two or both payment gateways for seamless transactions.

Learn more about Leegality Payment Collect here: https://www.leegality.com/features/payment-collect

Custom branding for Aadhar eSign journeys is now available.

‍

Now, you can personalize the Aadhaar eSigning screens on Protean (NSDL) to match your brand, enhancing trust and customer experience.

Now, users have the flexibility to customize the following elements:

• Logo: Integrate your brand identity.
• Title: Adjust font size, text colour, and background colour for a tailored touch.
• Page: Personalize the background colour and text colour to align with your brand aesthetics.
• Primary and Secondary Buttons: Change the button’s background and text colors for a cohesive look.

‍

Learn more about Custom branding for Aadhar eSign here: https://www.leegality.com/features/custom-branding-aadhaar-esign

Punjabi is added as a local language in the eSigning journey.

‍

Signers can now navigate the entire signing journey in Punjabi, marking a significant milestone in our commitment to enhance local language support.

Learn more about Local Language eSigning Journey here: https://support.leegality.com/portal/en/kb/articles/local-language-support

The Stamp Group Amount Limit has increased from 1 Lakh to 15 Lakhs to incorporate use cases in Maharashtra and Rajasthan.

Hybrid Bank Guarantees: You can now update (amended, invoked, cancelled etc.) paper-based BGs using NeSL Flow.

New Fields: 4 new fields have been added to the NeSL Flow. These fields will be available in API, Excel Upload, and Dashboard flow.

• ContractRefNo
• VendorCode
• PortalID
• BusinessUnit

Quick Sign is now available on App1 environment!

‍

Experience a swift and seamless eSigning journey, no OTP verification, and minimal friction points. Ideal for quick and efficient document signing, especially in scenarios where a smoother experience prevails over high enforceability.

Learn more about Quick Sign here: https://www.leegality.com/features/quicksign

‍

‍With the Leegality Salesforce Plugin, you can send documents for eSigning directly from your Salesforce dashboard. You can set it up and start executing documents in 5 minutes or less.

Highlights:

• No need to do API Integration - plug & play solution
• No need to manage different dashboards - everything is available inside the Salesforce dashboard
• Gives control to business teams - no need for tech teams to set up
• Auto-fill template details from Salesforce CRM
• Infosec guaranteed by Salesforce after 3 months of stringent verification

Learn more about Leegality plugin for Salesforce here: https://www.leegality.com/features/leegality-on-salesforce

Telangana state is now available for eStamping via NeSL.

This enhancement aims to provide an streamlined experience for our users in Telangana.

Face Match is now available on App1 environment.

‍

Face Match compares the signer’s face, captured during the signing journey, against the signer’s approved ID proof uploaded by the sender. This makes sure only the intended recipient signs the document.

Learn more about Face Match here: https://www.leegality.com/features/facematch

‍

‍

Invitees (signers and reviewers) can now view the supporting documents uploaded by other invitees - if allowed by the sender. 

Benefits

• Reviewers will have the option to review supporting documents while accepting or rejecting the document. Ensuring no misses in the supporting documents.
• Faster reviews and approval cycles.

‍

We're excited to launch PDF Templates on App1. 

With PDF Templates you can easily create reusable templates by simply uploading your PDF documents and adding the required dynamic fields.

‍

Key Features

• Create dynamic templates using your PDF documents

No need to recreate your entire document in Leegality’s text editor and instead just simply upload your PDF and drop fields on top.

This significantly reduces the time and effort to convert your documents into Leegality templates.

Non-signers and only stamping journey

‍

We are thrilled to introduce a significant update to our NeSL eBG suite that will allow our clients to skip debtors and beneficiaries from the signing journey in eBG flow.

In addition, clients now have the flexibility to obtain only stamps from NeSL while utilizing other signing options available on Leegality, such as Aadhaar, Virtual, DSC, and more for signing.

‍

For more details on Bank Guarantee: https://www.investopedia.com/terms/b/bankguarantee.asp

‍

Signer when using Aadhaar eSigning goes to different ESPs, depending on the number of trial attempts. This happens because we use backup ESPs. For example, by default, the signer lands on the following ESP pages according to the attempts:

1. Attempt 1:  NSDL (Protean)

2. Attempt 2: Verasys

3. Attempt 3: CDSL

This is the default set priority order for ESPs

‍

Previous Working

In the past, determining whether ESP priority order adjustments were needed required manual monitoring by our Support team. This process was time-consuming and relied on Admin Panel actions. The decision to switch priorities was based on various ESP parameters, including success rate, error rate, and pending rate.

‍

We're unveiling an advanced AI-driven system that efficiently handles the above challenges, from jumbled names to phonetic similarities. The aim? To offer more accurate, reliable, and traceable similarity scores for name comparisons.

‍

‍

Introducing a new feature that will enhance your control over the signer experience in our platform: "Aadhaar First."

With "Aadhaar First," clients can now specify if Aadhaar eSign types should be prioritized over other eSigning options for signers. Additionally, senders have the ability to fine-tune the signing sequence and retry count for subtypes within Aadhaar, including OTP, BIO, and IRIS.

Setup and Sending Journey

To start using this feature, simply grant access from the Admin Panel. Once enabled, follow these steps to configure it in the sending journey:

1. When selecting the Aadhaar eSign type for an invitee, a new toggle for "Prioritize Aadhaar for the invitee" will appear in invitee-level options.

2. Turn on the toggle to specify the selected subtype (OTP/BIO/IRIS) to be shown.

3. You can further customize the experience by setting:

 3.1 Order: Define the sequence in which the subtypes should be presented to signers. Subtypes with the same order will be shown together.

3.2 Retry Attempts: Determine the number of additional attempts a signer needs to go through before the next option in the order is shown and made available to the signer.

We’re excited to announce another upgrade to our suite of features specific to NeSL! We have launched the NeSL verification flow (v1).

‍

Background-

1. For NeSL eSign verification, even if verification fails, we have to Accept the eSign and respond that a mismatch has occurred (Accept but Respond with Result). 

    [For a normal Aadhaar eSign, we have 2 options upon verification mismatch → ‘Reject if failed’ OR 'Accept but Respond with Result']

2. If an NeSL eSign has verification ON and verification fails, the signer’s eSignature is placed on the document, and the next signer is made active (this was the intended flow). We cannot  reject the signing as the entire process happens in NeSL's environment so we're not in control of rejecting the eSign.

3. In the scenario where an NeSL signer signs and there is a verification mismatch, if the next active signer has an automated eSign configured, then despite verification mismatch, their eSign will be affixed to the document. Due to mismatch, the document may not be useful at all for the client. But the document gets completed and the client's automated eSign credits will be wasted nevertheless.

We are excited to announce a new feature called GPS Location and Accuracy based restriction, aka Geofencing. With this feature, our clients can now exercise precise control over document signing by ensuring:

1. The signing can be done from within a specific location only

2. Captured GPS location's accuracy to be within a certain threshold

‍

How does it work?

1. Location-based restriction: Senders can specify coordinates and a permissible radius for where an invitee can sign. If the invitee's captured location falls within the allowed area, they can proceed with the signing journey; otherwise, they will need to try again.

‍

2.  Accuracy-based restriction: Senders can set an accuracy threshold for the captured location during document sending. If the invitee's captured location's accuracy exceeds this threshold at the time of signing, they won't be able to complete the journey and will have to try again

‍

Setup:

1. The organization must be granted access from the Admin Panel.

2. In the Account Tab > Department > Invitee Config, clients can manage default permissible radius and default accuracy thresholds.

‍

We're excited to announce a game-changing feature that will elevate the way our clients communicate with their customers. Now, invitees can receive all communications such as invitation links, expiry reminders, completed document PDFs, Audit Trail PDFs, etc. directly on their WhatsApp! This feature represents a significant enhancement over our previous methods of SMS and email communication.

What's Changing:

‍Previously for NeSL flows, on the Details Page, error messages were displayed for all NeSL invitees, regardless of whether they had signed the document or not. This often led to confusion, especially when a signed invitee was mistakenly shown with an error message. Users were prompted to reach out to already-signed invitees for another signature, causing unnecessary hassle.

We've made a new update to enhance our Information Review process, specifically for NeSL's flows.

‍

Why This Change?

Previously, reviewers could only check the main document or template that was about to be signed. But with t NeSL gaining traction, it became clear that reviewers needed to see more. When using NeSL, senders have to fill in detailed information about the borrower and specifics about the loan and stamp. This includes essential details like loan details, stamp data, and information about the invitees.

‍

What's New?

Now, if a document has both a reviewer and NeSL signers, the reviewer can see the entire NeSL form completed by the sender. This means they can easily check the accuracy of the sender's entries in the NeSL form and decide whether to approve or decline the document.

‍

To improve the performance & load time of the "Expiring Soon" tab, we have introduced a filter on the "Expiring Soon" Tab.  You can now either see documents in this category "Sent" by you, or "Received" by you.  

Earlier, both these categories were listed in the same view, which caused performance issues, but now they are listed separately, depending on the filter chosen.

‍

Earlier, the system only notified users when their unused stamps, expired and reserved stamps  fall below a specified threshold.

However the inclusion of expired and reserved stamps gave a false idea regarding the available stamps for use. Due to which, timely low balance notifications weren't getting triggered to the clients, leading to halt in client operations at many instances as the stamps weren't available for usage.

Now, with this enhancement, we will exclude the expired and reserved stamps while counting triggering Low Balance Notification for stamps.

Announcing the enhancement to NeSL flows that will allow our clients to have multiple service types, such as Lending, Non-Lending and eBG (coming soon, stay tuned) under the same organisation.

In the past, our clients were limited to mapping only one type of service to each organisation.

However, with our latest update, NeSL credentials can be added for multiple services (or registration types) as separate profiles under a single organisation.

Leegality APIs now support end-to-end encryption through an additional payload encryption capability.  This enables customers to add an additional layer of security and ensure that the API payloads are encrypted using client specific key pairs.  To know more visit our API documentation: https://docs.leegality.com/v3#section/Payload-Encryption

You can now configure cloud DSC (Digital Signature Certificate) as a sign type option for group invitations.

This new addition is readily available across our New Document Flow, Workflows, and API 3.0 version. However, please note that this function is not compatible with API 2.1 due to its limitations in supporting Group Invitees.

‍

The attached image provides a glimpse into the Cloud DSC Options in the Workflow Creation process. As a Workflow Creator, you have the autonomy to set the signer ID for each participant individually, or delegate this responsibility to the Workflow Runner to arrange at the time of Workflow execution. In addition, we have also added a verification module. This will allow Workflow Creators to cross-verify the details of a signer with the information present in their Certificate Details, further enhancing the reliability and security of Cloud DSC as a sign type.

‍

We have rolled out a new API to eSign invitations created with DocSigner eSign. This is done to speed up the signing process for documents in queue to be automatically e-signed (via doc signer).  

With this new API, instead of configuring Automated Docsigner and keeping the customers waiting for upto a few minutes, our clients can immediately call the new DocSigner Signing API to eSign the docsigner invitation without any wait time.  

Note:  This API works only with Docsigner invitations (not automated docsigners).  The Docsigner must also be hosted on Leegality's server.  

‍

We have rolled out an update to notification emails that get triggered for group invitations.  Earlier, the emails sent for group invitations were identical to the emails sent for indivdual invitations.  This would confuse group invitees, because the emails would not give any contextual information such as the name of their group, other signers in the group, the threshold of the group, as well as the status of other signers in the group.  

The revamped notification emails will now cover all of this contextual information for the grouped signatories. See the KB here

‍

We have added support for the Morpho & Precision PB 510 devices through the backup ESP verasys, in the Aadhaar biometric flow.  To use the flow, customers will have to download the latest version of the Leegality Helper App that's available for download from the Google Playstore.

‍

We have made upgrades to Sign Upload on app1. Till now, users have been able to upload a signature drawn on plain white paper. However, we have taken this a step further and developed an automatic signature detection system.

2 new fields have been added to the stamp form in the product i.e. a.) Purchased By - In case an intermediary is purchasing the stamps on someone's behalf b.) Stamp Duty paid by - This can be either one of the first party or the second party mentioned.

This is relevant for eStamp purchases for certain customers who act as intermediaries for their own customers.

An enhancement has been made to revenue stamps whereby you can now attach more than 1 revenue stamps to a document (which was earlier restricted to 1)

We are excited to announce the launch of the highly anticipated NeSL non-lending flow. This new feature allows banks to use NeSL for non-financial use cases such as-

1. Opening escrow accounts
2. Signing NDAs
3. Opening bank accounts

In previous release of custom webhook headers, clients were enabled to add additional headers to the webhook calls for authentication purposes.

Now, whenever a customer wants to store their DocSigner Certificate on Leegality's server, they can do it by themselves without any support/ tech team involvement.

The activity logs for completed documents will now have a link to download the Audit Trail.  This link can be used to download the Audit Trail even after the document is deleted.

We are excited to announce the latest addition to NeSL: The NeSL MultiDoc feature! This new feature allows users to send multiple documents with corresponding eStamps affixed just before each document, providing a more organized and user-friendly experience.

Now concurrent logins from the same user ID (phone/email) will not be allowed for Dashboard logins.

Previously, a standard webhook structure was available for communication of invitation status and signed documents.

Now, the clients wanting to authenticate the webhook calls from Leegality can add custom headers to these webhook calls according to their needs.

‍

A few months back, we rolled out support for Revenue Stamps, which is a unique category of stamps used for Demand Promissory Notes (DPNs) and other documents. We are now rolling out an upgrade which allows you to affix more than one Revenue Stamp for a document.

We have launched a new module that affixes revenue stamps exclusively.

We have launched Regional Languages in the signing journey on the production environment! We now support the following 10 languages in the signing journey : India: - English, Hindi, Marathi, Gujarati, Kannada, Tamil, Telugu, Malayalam, Bengali, and Odia.

We’ve resolved the bug that was causing the API documentation to not open on some devices.

In all NeSL flows (F2F and nonF2F), we will now send a Leegality email/SMS with the signing URL.

We have made minor updates to SFTP- 

1. Included IRN in the email which is triggered upon failure of transfer via SFTP.
2. Added a subscript below the input parameter 'Destination'- 

Note: Please add a forward slash (/) after entering the destination

We’ve fixed the issue that made the document ID and stamps ID spillover on the document content when multiple stamps were attached to the document.

We've added an API for the manual activation of invitations! This new API is a part of API 3.1-

Reduced the ‘Resend OTP’ timer from 60 seconds to 30 seconds on the Dashboard login page. This is to help improve the user experience while using the Dashboard.

We have launched a new UI for the NeSL Forms and made improvements to make the form filling experience better for clients.

We have launched the Physical Signature Capture on production environment (app1).

A new parameter has been added called "replicateStampCoordinates". 

If this parameter is passed as "true", then the eSign coordinates passed for page 1 will be replicated for all the stamp papers in the document.

We have integrated another ESP (CDSL) for the Aadhaar eSign (OTP) flow.

It will work similar to all other ESPs currently live including NSDL & Verasys with the same auto-switch functionality.

We have launched Contact Book on production environment (app1).

This will appear under MY DRAWER once access is enabled via Admin Panel.You can Add, Edit, and Share contacts within the organisation.

To add contacts:

We have optimised NeSL Support flow by displaying Transaction ID to users. Transaction ID for NeSL Sign Invitations will be visible on the Details Page.

You can now eSign upto 5 documents in a single flow using Cloud DSC. This feature can be accessed when signing documents from the received folder (which have Cloud DSC type enabled).

The wallet tab has been revamped with an all-new purchase & transaction history experience allowing users to purchase credits and stamps easily and view transactions seamlessly.

We have added Multi-stamping functionality in NeSL flow. Instead of generating just one stamp for every use-case, we can now generate multiple stamp papers.

Invitees can now reject sign invitations in the signing journey itself, and provide a message at the time of rejecting invitations.

Kerala has been added to the list of states that support NeSL eStamping.

ePass tokens are now supported on MacOS for the DSC & Bulk DSC flows.

You can now check verification details on the dashboard. If verification is enabled for Aadhaar, DSC, Cloud DSC or NeSL, you will be able to view whether the verification was a success or a failure, and what was the parameter that caused the failure (if any).

The mac parameter has been added to the webhook. This allows users to verify that the webhook call is coming from Leegality's servers. 

See more: 

https://docs.leegality.com/webhooks_resources#tag/Coordinate-Picker-Webhook

The Notifications Tab of the dashboard has been revamped to make it more user-friendly and self-serviceable.

1. NeSL eSign is now supported on the 2.1 API as well.

We have rolled out a new version (v 3.1) of the Details API. 

The 3.1 Details API is a powerful & flexible API that can be used to fetch all data & files related to documents sent/signed using Leegality. 

Notable improvements:

We have also released a revamped version of the Settings Tab on Production. 

This will take care of several visual inconsistencies and improve usability and self-servicibility.

In workflows which have at-least 1 reviewer, there will be an option under "Advanced Options" called "Prevent Changes to Signing Order".

You can now create text-boxes using our template generator in a way that filling one text box automatically fills a number of other text boxes.

'Coordinate Picker' feature have been introduced in the Leegality application.

In the signing journey, an alert will be shown for message in the left corner when custom message is added by the sender same as that for the invitees.

Custom colour issue for the department: Earlier Sign button and the loading bar in the signing journey had the default colour (blue) irrespective of the colour set for the department. Now the button and the loading bar in the signing journey will have the custom colour set.

Custom date range issue on the Document Listing page: Earlier when the custom date range was set by the user, then the dates on the listing screen disappeared and the documents were shown for All Dates. Now the exact date range is shown and the documents are listed as per the range set by the user.

Earlier when the logged in user switched the user from shared accounts and navigates to Accounts>> Department, then Activity logs were shown. Now the fix has been done and the logged in user can see all tabs under Department tab.

Document listing fix: Earlier when a document(with signing order enabled) was received to a single invitee multiple times, then multiple rows of the same document was shown in the Received folder although one of the logged in user was inactive. Now the fix has been done, only a single row of the

Document will be shown in the received folder for which the logged in user is active

Much awaited feature 'Reviewer Rejection comments' is now live.

Earlier, DSC Name and SmartName verification validations were not handled in the Dashboard. Now, the checks have been added, and it is matched with the certificate details.

Group invitations - Post completion message has been updated.

1. API to fetch Stamp Consumption details - New field 'Expired' has been added which signifies the number of stamps expired in every stamp series.