> For the complete documentation index, see [llms.txt](https://docs.ccpayment.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccpayment.com/faq/webhook-notification/why-do-some-deposit-transactions-not-include-the-from-address-in-the-webhook-notification.md). # Why do some deposit transactions not include the “from address” in the webhook notification? In certain token transactions, such as BTC or LTC, that utilize the UTXO mechanism, both the “from address” and “to address” can have multiple addresses within a single transaction. Additionally, many of these addresses are not intended for transactional purposes. To prevent any potential misuse of these addresses for transactional purposes, CCPayment does not provide the “from address” in webhook notifications for these types of token transactions. We recommend familiarizing yourself with the UTXO transaction mechanism. If your product insists on including this type of address, please[ provide us ](https://t.me/CCPaymentSupportBot)with the specific use case, and we will review the request and consider implementing it to fulfill your requirements. --- # 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://docs.ccpayment.com/faq/webhook-notification/why-do-some-deposit-transactions-not-include-the-from-address-in-the-webhook-notification.md?ask=&goal= ``` `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.