> 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/dataimpulse-documentation-zh-cn/jing-xiao-shang/cun-kuan-ji-suan-geng-xin.md).

# 存款计算更新

了解 DataImpulse 经销商存款计算更新。掌握如何为您的子用户计算存款，以及经销商的计费方式。

我们引入了基于系数的系统，以准确管理不同代理池的押金。&#x20;

此前，押金计算仅适用于住宅池。随着 Mobile 和 Datacenter 池的加入，现已实施以下系数：

Residential: x1

Datacenter: x0.5

Mobile: x2

Premium Residential: x5

**押金流程**

押金流程保持不变：

存入 $50 可获得 50 GB 流量。

自定义定价继续按先前定义的方式运行。

**子用户分配**

当转销商向其子用户分配流量时，余额按以下逻辑扣除：

***Residential Pool:***

请求：10 GB

扣除：从转销商余额中扣除 $10 GB

***Datacenter Pool:***

请求：10 GB

扣除：从转销商余额中扣除 $5 GB

***Mobile Pool:***

请求：10 GB

扣除：从转销商余额中扣除 $20 GB

***Residential Premium Pool:***

请求：10 GB

扣除：从转销商余额中扣除 $50 GB

<br>


---

# 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/dataimpulse-documentation-zh-cn/jing-xiao-shang/cun-kuan-ji-suan-geng-xin.md?ask=<question>&goal=<user_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.
