> For the complete documentation index, see [llms.txt](https://revuto.gitbook.io/revuto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revuto.gitbook.io/revuto/faq/kyc.md).

# KYC

#### Why KYC?

KYC is required because:

* We deal with finance and payments
* Our **card issuing provider needs KYC verification** to issue you a debit card
* It gives us the opportunity to build more features that will create more value for Revuto and REVU holders
* It relieves the regulatory burden, freeing us to focus on creating **the best product possible**

With KYC, we are also investing in you:

* We invest our money in **every KYC verification**
* Hours of engineering work is spent on eliminating throughput bottlenecks
* We’ve enacted **compliance and regulation** for countries within the Eurozone

{% hint style="info" %}
It would be easier for us to give you REVU tokens free of charge, and let the free riders in. **But at Revuto, we don’t do what’s easy — we do what’s right.**
{% endhint %}

**For any additional questions feel free to contact our Customer Support on <support@revuto.com>**


---

# 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://revuto.gitbook.io/revuto/faq/kyc.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.