> For the complete documentation index, see [llms.txt](https://docs.avici.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avici.money/getting-started/virtual-accounts/documents-required.md).

# Documents Required

## Virtual Bank Accounts

### KYC

**Basic Info**

* Full name
* Residential Address
* Date of Birth
* Nationality
* Email
* Phone
* ID Document
* Liveness check/Selfie (comparison of liveness vs image on passport or DL and verification of document)

**Specific**

* POA (less than 3months)
  * for Customer’s ID document country is different than residence country (except for EU citizens)
  * Residence Permit does not contain address information or it does not match customer’s provided address information
  * Customer residing in high risk jurisdiction Customer IP address is detected to be from high risk jurisdiction
* SSN (US citizen or resident only)

**KYC questionnaire**

* Use of product
* Employment status
* Source of Wealth
* Annual Income
* Monthly expected transaction count
* Monthly expected transaction value


---

# 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://docs.avici.money/getting-started/virtual-accounts/documents-required.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.