> For the complete documentation index, see [llms.txt](https://yokifinance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yokifinance.gitbook.io/docs/subscription-payments/for-merchant/money-flows-and-settlement.md).

# Money flows and settlement

<figure><img src="/files/2w4srzqYIy9lx6mxGAYd" alt=""><figcaption><p>Money flows and settlement</p></figcaption></figure>

1. The merchant provides its wallet address for funds settlement.\
   This address is identical for all chains.
2. Yoki collects a 2% fee for all processed payments, the rest is transferred immediately to the settlement wallet provided by the merchant. E.g if the subscription is 100 USDT monthly, 98 USDT will be sent to the settlement wallet upon every monthly payment and 2 USDT to the Yoki Finance treasury wallet.
3. The first payment is deducted immediately from the customer, the next one is scheduled according to the details.
4. The smart contract is unchangeable but can be stopped. So to implement the changes (eg increase the pricing) merchant has to create the new smart contract by requesting the Yoki Finance team or using the API.
5. Yoki Finance does not hold customer funds which provides a better experience for the merchants and highly decreases any associated risks.


---

# 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://yokifinance.gitbook.io/docs/subscription-payments/for-merchant/money-flows-and-settlement.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.