> 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/initiate-and-sign-envelopes/signing-a-document/as-an-external-recipient-ad-hoc-user/making-payment-for-estamping-optional.md).

# Making payment for eStamping (Optional)

In certain workflows, eStamping may be required as part of the document execution. In such cases, the initiator can configure the workflow to **collect the stamping fee from the external recipient during the signing process**.

When this option is enabled, the signing journey for the external user includes an additional **payment step before final signing**.

***

#### When Is Payment Required?

* During document initiation, the **initiator chooses to collect eStamping charges from the external signer**.
* If enabled, the external user must complete the payment **before proceeding to sign the document**.

***

#### Email Notification to External User

The external recipient receives an email notification containing:

* Document name
* Initiator (sender) details
* Date and time of request
* A **Review and Sign** action

Clicking **Review and Sign** opens the document signing flow.

***

#### Reviewing the Document Before Payment

Before making any payment, the external user can:

* **View the document** in full
* **Download the document**
* **View or download attachments** (if any)
* **Add or view comments**
* **Check the signing order** to understand participants and sequence

This ensures the user can fully review the document and context **before committing to payment**.

<figure><img src="/files/aLe0GwGoJyhtIGRKYEiY" alt=""><figcaption></figcaption></figure>

***

#### Proceeding With Payment

If the document requires eStamping payment:

* A **Proceed to Pay** option is displayed in the signing interface
* The user can continue only after confirming the document is acceptable

On clicking **Proceed to Pay**:

* The user is redirected to a **secure payment gateway**
* Multiple payment options may be available, such as:

  * UPI
  * Credit / Debit Cards
  * Net Banking
  * Wallets
  * EMI or Pay Later (based on gateway support)

  <figure><img src="/files/7IJ0qE1OHDfg2PoKeYl7" alt=""><figcaption></figcaption></figure>

***

#### Payment Completion and Redirection

* Once the payment is completed successfully:
  * The transaction is validated
  * The user is automatically redirected to the **eStamp provider page (NESL)**

<figure><img src="/files/hbSiWVFMJRAJNcqO6qTq" alt=""><figcaption></figcaption></figure>

***

#### Completing the Signing Process

After redirection:

* The document is displayed with the applied stamp
* The external user can proceed with the **remaining signing steps**
* The signing flow continues seamlessly until completion


---

# 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/initiate-and-sign-envelopes/signing-a-document/as-an-external-recipient-ad-hoc-user/making-payment-for-estamping-optional.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.