> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/resellers/deposit-calculation-update.md).
# Deposit Calculation Update
Understand the DataImpulse reseller deposit calculation update. Learn how deposits are computed for your sub-users and how billing works for resellers.
We've introduced a coefficient-based system for accurately managing deposits across different proxy pools.
Previously, deposit calculations were only applied to the residential pool. With the addition of Mobile and Datacenter pools, the following coefficients are now in place:
Residential: x1
Datacenter: x0.5
Mobile: x2
Premium Residential: x5
**Deposit Process**
The deposit process remains unchanged:
A $50 deposit provides 50 GB of traffic.
Custom pricing continues to function as previously defined.
**Sub-User Allocation**
When resellers allocate traffic to their sub-users, the balance is deducted based on the following logic:
***Residential Pool:***
Request: 10 GB
Deduction: $10 GB from reseller balance
***Datacenter Pool:***
Request: 10 GB
Deduction: $5 GB from reseller balance
***Mobile Pool:***
Request: 10 GB
Deduction: $20 GB from reseller balance
***Residential Premium Pool:***
Request: 10 GB
Deduction: $50 GB from reseller balance
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataimpulse.com/resellers/deposit-calculation-update.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.