# Why Advanced Integration?

***Advanced integration can be reasonable when:***

* you want to minimize code(skip inheriting `MicapassBasicClient`) and implement only needed interaction with Micapass smart contract
* there is need to implement more complex logic for the user checks (no need of modifiers, can be implemented through conditions in the method logic)
  * as an example - the case when depending on the fact whether user has specific proof or not - the different logic should be executed
  * as an another example - depending on amount of deposit we should check different proofs:
    * for example if > 1 eth - we should check KYC and Wallet sanctions screening, if less - only Wallet sanctions screening
* when the number of proofs to check is big enough (it means that the number of modifiers for method will depend on it) or if the proofs requirements are configurable dynamically (it means that you can not hardcode it through modifiers)


---

# Agent Instructions: 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:

```
GET https://micapass.gitbook.io/micapass/sc-integration/advanced-integration/why-advanced-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.