> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/4.-developer-and-payment-engine/waas/callback-setting.md).
# Callback Setting
The callback settings page allows the following configuration operations:
1. Batch edit callback addresses
2. Set the default BTC address format
3. Set the minimum callback amount for currencies
## 1. Batch edit callback addresses
After clicking "Edit," a window will pop up on the right side. Here, you can enter the callback URL and then click confirm.
## 2. Set the default BTC address format
Click on the dropdown menu in the default BTC address format row to select the BTC address format. For more information on the differences between formats, you can refer [here](/6.-resources-documentation-and-terms/faq/wallet-management/why-does-btc-have-different-address-formats.md).
## 3. Set the minimum callback amount for currencies
Find the currency you wish to set under the minimum callback amount. Only currencies that have been added to the wallet will be displayed here. After selecting, click edit to bring up a numeric input box. Users can set a value below which a callback will not be triggered to prevent deposit harassment or dust attacks.
---
# 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.cregis.com/4.-developer-and-payment-engine/waas/callback-setting.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.
