> For the complete documentation index, see [llms.txt](https://fija.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fija.gitbook.io/docs/overview/compliance/whitelisting-process-and-integration-with-platforms.md).

# Whitelisting Process and Integration with Platforms

In the fija ecosystem, **whitelisting** refers to the process that ensures only approved addresses can interact with certain features, such as depositing funds into vaults or receiving the fija Token. Here's how it works:

1. **Vault Whitelisting:**
   * Each fija Vault is associated with a specific partner or reseller, and only addresses that are **whitelisted** by the partner or reseller can interact with the vault.
   * This whitelisting controls which customers or partners can deposit assets into a vault and receive fija Tokens in return.
   * The whitelisted addresses are the only ones allowed to make deposits or withdrawals, ensuring secure and controlled access to the vault’s assets.
2. **Security and Compliance:**
   * Whitelisting helps ensure compliance by verifying the identity of parties interacting with the vaults, reducing the risk of unauthorized access.
   * It aligns with regulatory requirements, like AML (Anti-Money Laundering) measures, by ensuring that only vetted users can interact with the DeFi strategies.
3. **Token Issuance and Withdrawal:**
   * When an asset is deposited, a fija Token is issued to the whitelisted address, which acts as proof of the deposit.
   * Similarly, only those with whitelisted addresses can redeem their fija Tokens for the underlying assets stored in the vault.

Whitelisting serves as an important security and compliance mechanism in the fija system, ensuring that only authorized users can manage their crypto deposits and interact with the platform’s DeFi strategies.


---

# 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://fija.gitbook.io/docs/overview/compliance/whitelisting-process-and-integration-with-platforms.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.