> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/security/aml-kyt.md). # AML/KYT Screening of Incoming Payments Automatic screening of the origin of funds for all incoming payments. Every incoming payment on Trybit automatically undergoes AML/KYT screening — an analysis of the funds' origin for signs of suspicious activity. This screening is built into the service and enabled by default for all payments — there's no need to activate it separately, and there's no dedicated toggle to fully disable it. ### Why this matters Screening reduces the risk of receiving funds with a suspicious origin — and, along with it, the risk of problems later when withdrawing or exchanging that cryptocurrency on exchanges: many exchanges run a similar check of their own and may block a deposit on their end if the received funds have a "bad" history. ### How it works The check runs automatically as a payment arrives, before it's credited to your balance. If a transaction shows signs of a suspicious origin, it isn't credited — the funds are returned to the sender. {% hint style="success" %} If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support). {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.trybit.com/security/aml-kyt.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.