> For the complete documentation index, see [llms.txt](https://venzofinance.gitbook.io/venzofinance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://venzofinance.gitbook.io/venzofinance-docs/venzo-app/architecture/deposit-flow.md).

# Deposit Flow

The deposit and subscription process operates through five distinct stages to ensure capital security and precise accounting:

1. **Deposit Request:** A user submits a deposit of an accepted asset via the Venzo frontend or API. The vault checks that the asset is accepted, the vault is open, the user is eligible, and the deposit falls within product capacity and investor-level limits.
2. **Security Verification:** Before capital is made available for allocation, the security layer verifies access permissions, deposit limits, approved allocation rules, product status, risk controls, the emergency pause state, and network validity.
3. **Share Accounting:** Shares, receipt tokens, or subscription records are issued according to the product design. For synchronous liquid vaults, shares are minted immediately at the current share price. For asynchronous or less liquid vaults, a pending subscription record is created until the next pricing and allocation cycle.
4. **Allocation Approval:** Approved capital is made available exclusively inside the vault mandate. The Strategy Manager routes the capital to approved strategies and venues, strictly bound by configured limits.
5. **Monitoring and Reporting:** All deposits, share issuances, allocation changes, fees, NAV updates, and vault events are indexed for transparent reporting.


---

# 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://venzofinance.gitbook.io/venzofinance-docs/venzo-app/architecture/deposit-flow.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.