> For the complete documentation index, see [llms.txt](https://varntix.gitbook.io/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://varntix.gitbook.io/resources/products/early-withdrawals-explained.md).

# Early Withdrawals Explained

### Overview

Early withdrawal rules depend on the type of savings product you choose.

Because Varntix offers both Flexible Savings and Fixed Savings, access to funds works differently for each.

#### Flexible Savings

Flexible Savings is designed to provide ongoing access to your funds.

This means you can withdraw your balance, in full or in part, at any time, subject to normal processing conditions.

Flexible Savings is intended for investors who want to earn interest while maintaining liquidity and day-to-day flexibility.

#### Fixed Savings

Early withdrawal is not available on Fixed Savings.

Allowing early withdrawal would change the structure of the product and reduce the predictability of both deployment and returns.

For that reason, Fixed Savings should only be used when you are confident you will not need access to those funds before the term ends.

#### What happens at maturity?

At the end of the term, your savings plan reaches maturity.

At that point:

* Your principal becomes available again
* Any interest due under the product terms is paid according to the schedule
* You may choose to withdraw, reallocate, or subscribe to another product

This gives you a clear end point and allows you to plan around future liquidity needs.

<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://varntix.gitbook.io/resources/products/early-withdrawals-explained.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.