> For the complete documentation index, see [llms.txt](https://docs.terragon.io/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terragon.io/documents/terragon-manual/solutions/player-module/3.-kyc-requests.md).

# 3. KYC Requests

The **KYC Requests** section is the second submodule under the **Players** module. This section allows you to manage and track player verification requests after they submit their KYC information. This has 2 main areas involved:

* **Backoffice**: where operators can collect KYC submission from players to verify and approve (or decline) accordingly. Operators can request players to re-submit the documents in case the submitted one does not have a good quality or any other reasons.
* **Front end**: where players are requested to verify their KYC upon deposit, withdraw or game play. It's up to operators to decide which stage (deposit, withdraw or game play) to require players submit their KYC requests.

**Additionally, the platform supports multiple KYC levels.** Operators can configure these levels directly from the Backoffice Settings. Each level represents a different degree of verification, and actions on the player’s side—such as deposits, withdrawals — can be restricted until the required KYC level has been successfully passed.