> For the complete documentation index, see [llms.txt](https://city-protocol.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://city-protocol.gitbook.io/docs/vault-as-a-service/deposit-and-subscription-flow.md).

# Deposit and subscription flow

The standard deposit flow includes five stages.

{% stepper %}
{% step %}

### Deposit request

The user deposits an accepted asset through City Neobank, a partner frontend, or an API integration.

The vault checks whether the asset is accepted, the vault is open, the user is eligible, and the deposit does not exceed product capacity or investor-level limits.
{% endstep %}

{% step %}

### Security verification

Before capital is made available for strategy allocation, the vault security layer verifies:

· access permissions;

· deposit limits;

· approved allocation rules;

· product status;

· risk controls;

· emergency pause state;

· accepted asset and network.
{% endstep %}

{% step %}

### Share accounting

The vault issues shares, receipt tokens, or a subscription record according to the product design.

For synchronous vaults, shares may be minted immediately at the current share price. For asynchronous or less liquid vaults, the user may receive a pending subscription record until the next pricing or allocation cycle.
{% endstep %}

{% step %}

### Allocation approval

Approved capital becomes available for strategy allocation only inside the vault mandate.

The Strategy Manager can route capital to approved strategies, borrowers, accounts, or execution venues, but cannot bypass the vault's configured limits.
{% endstep %}

{% step %}

### Monitoring and reporting

Deposits, share issuance, allocation changes, fees, NAV updates, and vault events are indexed for reporting. Integrators can display vault state without manually reading every contract call.
{% endstep %}
{% endstepper %}


---

# 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:

```
GET https://city-protocol.gitbook.io/docs/vault-as-a-service/deposit-and-subscription-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.