# How Billing and Wallet works

### Billing and Wallet Management in emSigner

#### Overview

emSigner uses a **hybrid billing model** that combines **subscription-based counters** with a **prepaid wallet system**. This approach provides flexibility for predictable usage (such as users and envelopes) while enabling pay-as-you-go consumption for value-added and third-party services.

***

### Subscription Counters

#### User-Based Counters

User-based subscriptions are measured by the number of **active users** enabled on the platform.

* Only users who are enabled and can log in are counted.
* Deactivated users are excluded from billing.
* User counters reset or renew based on the subscription term.

***

#### Envelope-Based Counters

Envelope-based subscriptions are measured by the number of **envelopes** sent for signature.

* An envelope represents a document or set of documents sent to one or more recipients.
* Envelope counters are consumed when an envelope is created and sent.
* Envelope usage is tracked in real time and reflected in subscription usage reports.

***

### Wallet-Based Billing

#### emSigner Wallet

For services not covered under subscription counters, emSigner maintains an **internal wallet**.

* The wallet operates on a **prepaid balance** model.
* Wallet balance is consumed based on actual service usage.
* Administrators can monitor wallet balance and transaction history.

***

#### Services Charged via Wallet

The wallet is used for billing the following categories of services:

* **Third-party eSignature services**
* **Qualified Electronic Signature (QES) providers**
  * European Union Qualified Trust Service Providers
  * India-based Qualified Electronic Signature services
* **Messaging services**
  * SMS notifications
  * WhatsApp notifications
* **eStamping services**
  * Government or authorized eStamping providers

Each usage event deducts the applicable amount from the wallet in real time.

***

### Pricing Model

#### Default Pricing

emSigner maintains **default price points** for all wallet-based services, which apply unless otherwise agreed.

* Pricing is defined per transaction, message, or signature event.
* Charges are applied automatically upon service consumption.

***

#### Customer-Specific Pricing

For enterprise customers, **custom pricing** may be configured based on:

* Expected or committed volumes
* Geographic scope
* Service mix (for example, QES + SMS + eStamping)

Customer-specific pricing overrides the default rates and is applied transparently during wallet deduction.

***

### Wallet Recharge & Balance Management

* Wallets can be recharged through approved payment methods or invoicing arrangements.
* Low-balance alerts may be configured to avoid service interruptions.
* If the wallet balance is insufficient, wallet-based services may be temporarily unavailable until the balance is replenished.

***

### Usage Visibility & Reporting

Administrators can access detailed reports that include:

* Subscription counter usage (users and envelopes)
* Wallet transaction history
* Service-wise consumption breakdown
* Applicable pricing per transaction

These reports support cost tracking, reconciliation, and audit requirements.

***

### Important Notes

* Subscription counters and wallet balances operate **independently**.
* Consuming a wallet-based service does not affect user or envelope counters.
* Pricing changes or custom rate configurations require confirmation through emSigner support.

***

#### Need Help?

For wallet recharges, pricing clarification, or enabling additional services, please contact your emSigner administrator or raise a request through the emSigner Support Portal.


---

# Agent Instructions: 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:

```
GET https://support.emsigner.com/signing-up-for-a-subscription/how-billing-and-wallet-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.