> For the complete documentation index, see [llms.txt](https://docs.inqud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inqud.com/crypto-static-addresses/integration/web-hooks.md).

# Web Hooks

{% hint style="info" %}
For foundational information on webhooks, including key concepts and verification methods, please refer to the [Webhook Basics](/developer/web-hooks.md) page.
{% endhint %}

Payment webhooks notify merchants of new payments to a static address and any status changes in real time.

### Prerequisites

* Your business account with Inqud is set up.
* The Crypto Widget has been established and configured within the Inqud platform.
* The Crypto Widget is active.

### Setting up Web Hook

1. Open the [app](https://app.inqud.com/) and sign in.
2. From the left menu bar, choose "Crypto widgets".
3. Select the desired widget with type **static**.
4. Open "Webhooks"
5. Locate the "Payment webhook" option and click on "Add".
6. Enter the required details:
   * Webhook link: Provide the URL of your webserver that will handle the callbacks.
   * Webhook secret: Enter a secret key for signature calculation (optional).
7. Click on "Save" to finalize your settings.

{% @howdygo/embed url="<https://app.howdygo.com/share/293ca2fc-be32-4736-8853-b42cf8a0ec6c>" %}

### Payment statuses

<figure><img src="/files/FFuSy3XvbKO73r25o6JB" alt=""><figcaption></figcaption></figure>

### Notification

The Payment Webhook triggers on every payment status change. Your server must respond with a **200 status code**; otherwise, retries will be attempted using an exponential backoff strategy.

For detailed request specifications, refer to the following page:

[Payment Web Hook Specification](https://apireference.inqud.com/#tag/crypto-acquiring-webhooks/operation/user_crypto-acquiring_set-crypto-acquiring-static-address-payments-webhook) (see **Callbacks** sections)


---

# 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.inqud.com/crypto-static-addresses/integration/web-hooks.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.