> For the complete documentation index, see [llms.txt](https://developer.flash-payments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.flash-payments.com/accounts/virtual-account-numbers/sub-client-statuses.md).

# Sub-client statuses

Sub-client VANs lifecycle

A sub-client lifecycle follows these stages.

A sub-client is created and has the **temporary** `INITIATED` status.\
At this stage, the request has been received and the system is currently processing it.

If processing is completed successfully, the sub-client automatically transitions to the `ACTIVE`.\
In this status, the sub-client is fully activated and approved.

If the sub-client requires manual compliance review, the sub-client moves from `INITIATED` to the **temporary** <mark style="color:orange;">`UNAPPROVED`</mark> status.\
From this status it would eventually transition to either `ACTIVE` or `FAILED_KYC`.\
Typically, we can't disclose the exact reason of the KYC failure, while it mostly happens because we do not have risk appetite for your client.

You can deactivate the client (via API of Flash Connect), - it'd move from `ACTIVE` to `DEACTIVATED`.\
A sub-client in the `DEACTIVATED` status can be activated by you at any time, returning to `ACTIVE`.

At any point, a sub-client may be moved to `DISABLED`.\
In this status, the sub-client is disabled and cannot be enabled by you, and contacting support is required for further information.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://developer.flash-payments.com/accounts/virtual-account-numbers/sub-client-statuses.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 `build a script that syncs our docs to a CMS` 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.