> For the complete documentation index, see [llms.txt](https://lofty-2.gitbook.io/faqs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lofty-2.gitbook.io/faqs/faq/why-is-my-id-verification-taking-so-long.md).

# Why is my ID verification taking so long?

We use a 3rd party provider to perform Identity verification. They are more specialized in US IDs. For international investors, if you have a passport, please use it for your KYC process instead of a Driver’s License or local ID. This is because not all IDs share the same format, some country’s Driver’s Licenses don’t have expiration dates, which will confuse the automated software. Whereas most Passport formats are standardized even if they're from different countries. In order to comply with US regulators at both the federal and state levels, we have to reject all IDs that are not clear or in good quality where information can easily be verified by a human. If your account creation was rejected multiple times please try to take higher quality photos or use your Passport instead.


---

# 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://lofty-2.gitbook.io/faqs/faq/why-is-my-id-verification-taking-so-long.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.