> For the complete documentation index, see [llms.txt](https://guide.finceptor.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.finceptor.app/cashback-policy.md).

# Cashback Policy

Fount offers cashback rewards to users who participate in IDOs. 

Users are eligible for cashback regardless of whether they claim or refund their allocations. Simply participating in or depositing funds into the IDO pool and holding a tier status qualifies them for cashback.

Cashback starts at 0.25% and increases up to a maximum of 1% of the invested amount, depending on the user’s tier.

Tiers and corresponding cashback ratios are shown in the table below.

|              | **Trial** | **Standard** | **Standard**+ | **Premium** |
| ------------ | --------- | ------------ | ------------- | ----------- |
| **Cashback** | 0.25%     | 0.5%         | 0.75%         | 1%          |

{% hint style="info" %}
Cashback percentages do not increase linearly across tiers, unlike the Pool Weight in the Tier System. The next level is only obtained by reaching the threshold for that tier.
{% endhint %}

Cashbacks will be deposited after the refund period ends.

{% hint style="success" %}
**Example:** A user with Premium Tier invests $5,000 into an IDO Pool on Fount. The user will be eligible for a cashback of 1% of the invested amount, which equals $50.
{% endhint %}


---

# 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://guide.finceptor.app/cashback-policy.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.